Review round: refresh daemon/agent charters + prompts + spawn/reset packets against current tools/workflows/features

Operator-requested (Mike, 2026-07-04). A review round on EVERYTHING we pass to agents/daemons — charters, prompts, spawn/reset/compaction packets, worker-kickoff conventions — to bring them up to date with the tools/workflows/features/feedback that have landed recently. Chose a brief over extending feedback #127 because this is a substantive audit+update task, not a single convention line. ## Surfaces to review - `App\Support\DaemonCharterDefaults` — role charter bodies (orchestrator/ops/refine/lead; just bumped to v5 by #170). - `App\Support\AgentConventions` — shared daemon block, daemonLines, brief-trailer + worker finish conventions. - `SpawnPacketService` / `CompactionPacketService` / the reset-successor packet + dispatch packets. - `prompt_templates` (DB, seeded by `PromptTemplateSeeder`) + any /roster spawn prompts. - The worker-kickoff text the orchestrator sends when dispatching (currently ad-hoc per dispatch — consider a canonical template). ## Recent changes the text should reflect - Decisions feature (#95) + `decision_*` tools now exist — daemons should escalate/ask via `decision_ask`/`brief_ask` (async); #170 wove `decision_*` into charters (verify coverage + consistency across roles). - **feedback #127**: daemons must NEVER use the Claude Code interactive AskUserQuestion tool — route to `decision_ask`/`brief_ask`. Bake this convention into the shared charter block. - Epic-lead pattern (#226, COMPLETE): charters/spawn should reference the lead role, `epic_delegate`/`epic_return` signals, `flower:spawn-epic-lead` / `flower:retire-epic-lead`, `EpicLeadPolicy`, the epic-branch merge-lock vs the MAIN baton. The orchestrator charter should cover spawning + monitoring + auto-spawn-on-force (#241) of leads. - `brief_ask` ↔ `decision_ask` parity (#228). - Auto-dispatch + reconcile flow + cap semantics; the post-merge gates (`flower:horizon-reload` on job change, `flower:daemon-schema-reload` on rename, `PromptTemplateSeeder --force` on charter-body change). - The `#→name` Refs-index convention (companion brief) once refined. ## Deliverable An audit pass per surface (what's stale / missing / inconsistent) → a set of concrete ADDITIVE charter/prompt update briefs (or direct edits). Additive + backward-compatible; charter-body changes require a `PromptTemplateSeeder` re-seed to reach new daemons (per #170), and standing daemons only pick up charter changes on their next reset. Good candidate to run as an EPIC (audit → child update briefs) or a design pass. Keep the suite green (charter/convention tests). ## Refs #127 (no-interactive-questions feedback), #170 (v5 charters), #95 (decisions feature), #226 (epic-lead), #228 (ask parity), #241 (force-epic-lead control), #78 (entity-ref recommendation / inbox note 2), companion ref-index brief (below).