Editable agent prompts: dispatch packet + charters as config-as-data in a prompt-library UI (conventions DRY-d)

Checked current state per the refinement task: this is ALREADY SHIPPED. Backend templatization + AgentConventions (commit 6086f8a) and the /prompts prompt-library UI with edit + live preview + versioning + revert (commit ef57322) are both merged; I used the working /prompts page during the #38 design review. Set to COMPLETE — no build spec needed. Reopen if any residual gap.

## Spec: editable agent prompts + DRY participation conventions **Ask (Mike, 2026-07-01):** the **dispatch packet** — the instruction block `DispatchService::renderPacket` sends to a dispatched agent (brief spec + trace events + linked context + resume hints + the "Execution notes" incl. the `Brief: #N` commit trailer and the `brief_append` progress line) — is hard-coded in PHP. **Expose it as an editable template in the flower UI** so we can iterate on what agents are told without a code change. Same for the daemon **charter** templates (config-as-data via `prompt_templates` since B3, but not yet UI-editable). ### Backend 1. **Templatize the dispatch packet** — a config-as-data template (a `dispatch_packet` kind in `prompt_templates`), placeholders for the dynamic parts (brief id/slug/spec, trace events, linked todos/scratchpads, resume hints) + an editable static Execution-notes/conventions section. `DispatchService` renders from the template; **seed it from the current hard-coded text so behaviour is unchanged**. 2. **`AgentConventions` single source of truth** — working-agent subset (`Brief: #N` trailer + `brief_append` progress) + daemon subset (`daemon_checkin` heartbeat + trailer + compaction/handoff). The dispatch-packet template, the `brief_claim` / `brief_dispatch` MCP responses, and `DaemonCharterDefaults` all render the relevant subset. One edit adds a future convention everywhere. 3. **Close the gaps:** `brief_claim` returns the packet/instructions (not a bare ack); daemon charters include the commit-trailer convention (they only carry the heartbeat today). ### Frontend (prompt-library UI) 4. A **prompt-library screen** (pairs with the B3 charter/spawn work + the roster UI) to view + EDIT the **dispatch-packet template** AND the per-role **charter templates** in one place: placeholder reference, a **live preview** rendering the effective packet with sample substitution (so Mike sees exactly what an agent receives), versioning, `is_active`, revert-to-seed. Reuse the config-as-data + bloom patterns. ### Notes - **Subsumes the earlier participation-conventions codification** — making the prompts data + editable inherently DRYs and centralizes the conventions (answers the open "DRY from the start?" question: yes, the data model is required for UI-editability anyway). - Owner: a backend/foundation lane for 1–3; design for 4. Commit trailer `Brief: #16`.

Mike (2026-07-01): the dispatch packet — the full instruction block DispatchService::renderPacket emits to a dispatched agent — is hard-coded in PHP. Expose it as an EDITABLE template in the flower UI so we can iterate on what agents are told without a code change. Same for the daemon charter templates. And DRY the participation conventions so they propagate to every channel automatically.