Epic-lead Slice B — Lead charter & spawn path (#226)

You are being dispatched from flower Brief #232: Epic-lead Slice B — Lead charter & spawn path (#226)

Recall pointer:
- Use recall_brief with id 232 for the full folder if you need provenance.

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/232-epic-lead-slice-b
- worktree: not specified
- kind: fresh

Current brief spec:
# Slice B — Lead charter & spawn path

Parent epic: #226. Design: `docs/design/226-epic-lead-orchestration.md` (§Spawn, §Identity pt.1). **Depends on Slice A (#231).** Target ≤~300 lines (charter prose excepted).

## Deliverable
1. **Relax the 3 spawn/charter role guards** to permit `lead` (still reject `other`):
   - `SpawnDaemonBridge::role()` (:170), `SpawnPacketService::role()` (:384), `CompactionPacketService::role()` (:83).
   - **Deliberately LEAVE** the operator-UI guard `Roster/Index.php` `SPAWNABLE_ROLES` (:588) rejecting `lead` — leads are spawned programmatically by MAIN, not hand-spawned from `/roster`.
2. **Lead charter** — `DaemonCharterDefaults::leadBody()` + seeded `daemon_charter` role=lead PromptTemplate row. Charter covers: own the epic (parent brief + children); delegate/review children like the orchestrator (scoped to the epic branch); merge children → epic branch under the `flower-epic-<id>-merge` Solo lock (NOT the baton); the epic-scoped `epic_delegate` mailbox drain carve-out (permitted despite not holding the baton); report up via `epic_return`; the bounded post-merge window + ops handoff + cooperative retire.
3. **Lead spawn-packet variables** — epic brief id, epic branch (`flower/epic-<id>`), epic worktree path.
4. **MAIN-facing spawn affordance** — `flower:spawn-epic-lead` command (or a DirectDispatch-style live spawn) that: ensures the epic branch + worktree exist (worktree-manager external; Brief #184 `WorktreePreparer` gate), `registerExpected('lead', project, actor_ref, epic_brief_id)`, then `SpawnDaemonBridge::spawn()` with the lead charter → `SoloClient::spawnAgent`.

## Tests
- Lead spawn renders the lead charter (not orchestrator/ops/refine).
- The 3 spawn/charter guards permit `lead`, still reject `other`.
- `flower:spawn-epic-lead` registers an expected lead row with the right `epic_brief_id` + actor_ref.

## Notes
- Reuse the existing spawn path; only the charter body + packet vars + the MAIN affordance are new.

Recent/key trace events:
[1] participant_joined flower-226-worker: (no body)
[2] note_added flower-226-worker: # Slice B — Lead charter & spawn path

Design: `docs/design/226-epic-lead-orchestration.md` (§Spawn, §Identity pt.1). Depends on Slice A. Target ≤~300 lines (charter prose excepted).

## Deliverable
1. **Relax the 3 spawn/charter role guards** to permit `lead` (still reject `other`):
   - `SpawnDaemonBridge::role()` (:170), `SpawnPacketService::role()` (:384), `CompactionPacketService::role()` (:83).
   - **Deliberately LEAVE** the operator-UI guard `Roster/Index.php` `SPAWNABLE_ROLES` (:588) rejecting `lead` — leads are spawned programmatically by MAIN, not hand-spawned from `/roster`.
2. **Lead charter** — `DaemonCharterDefaults::leadBody()` + seeded `daemon_charter` role=lead PromptTemplate row. Charter covers: own the epic (parent brief + children); delegate/review children like the orchestrator (scoped to the epic branch); merge children → epic branch under the `flower-epic-<id>-merge` Solo lock (NOT the baton); the epic-scoped `epic_delegate` mailbox drain carve-out (permitted despite not holding the baton); report up via `epic_return`; the bounded post-merge window + ops handoff + cooperative retire.
3. **Lead spawn-packet variables** — epic brief id, epic branch (`flower/epic-<id>`), epic worktree path.
4. **MAIN-facing spawn affordance** — `flower:spawn-epic-lead` command (or a DirectDispatch-style live spawn) that: ensures the epic branch + worktree exist (worktree-manager external; Brief #184 `WorktreePreparer` gate), `registerExpected('lead', project, actor_ref, epic_brief_id)`, then `SpawnDaemonBridge::spawn()` with the lead charter → `SoloClient::spawnAgent`.

## Tests
- Lead spawn renders the lead charter (not orchestrator/ops/refine).
- The 3 spawn/charter guards permit `lead`, still reject `other`.
- `flower:spawn-epic-lead` registers an expected lead row with the right `epic_brief_id` + actor_ref.

## Notes
- Reuse the existing spawn path; only the charter body + packet vars + the MAIN affordance are new.
[3] parent_set flower-226-worker: Grouped under epic #226.
[4] dependency_added flower-226-worker: Now depends on #231 (Epic-lead Slice A — Lead identity & roster scaffolding (#226)).
[5] plan_proposed flower-226-worker: # Slice B — Lead charter & spawn path

Parent epic: #226. Design: `docs/design/226-epic-lead-orchestration.md` (§Spawn, §Identity pt.1). **Depends on Slice A (#231).** Target ≤~300 lines (charter prose excepted).

## Deliverable
1. **Relax the 3 spawn/charter role guards** to permit `lead` (still reject `other`):
   - `SpawnDaemonBridge::role()` (:170), `SpawnPacketService::role()` (:384), `CompactionPacketService::role()` (:83).
   - **Deliberately LEAVE** the operator-UI guard `Roster/Index.php` `SPAWNABLE_ROLES` (:588) rejecting `lead` — leads are spawned programmatically by MAIN, not hand-spawned from `/roster`.
2. **Lead charter** — `DaemonCharterDefaults::leadBody()` + seeded `daemon_charter` role=lead PromptTemplate row. Charter covers: own the epic (parent brief + children); delegate/review children like the orchestrator (scoped to the epic branch); merge children → epic branch under the `flower-epic-<id>-merge` Solo lock (NOT the baton); the epic-scoped `epic_delegate` mailbox drain carve-out (permitted despite not holding the baton); report up via `epic_return`; the bounded post-merge window + ops handoff + cooperative retire.
3. **Lead spawn-packet variables** — epic brief id, epic branch (`flower/epic-<id>`), epic worktree path.
4. **MAIN-facing spawn affordance** — `flower:spawn-epic-lead` command (or a DirectDispatch-style live spawn) that: ensures the epic branch + worktree exist (worktree-manager external; Brief #184 `WorktreePreparer` gate), `registerExpected('lead', project, actor_ref, epic_brief_id)`, then `SpawnDaemonBridge::spawn()` with the lead charter → `SoloClient::spawnAgent`.

## Tests
- Lead spawn renders the lead charter (not orchestrator/ops/refine).
- The 3 spawn/charter guards permit `lead`, still reject `other`.
- `flower:spawn-epic-lead` registers an expected lead row with the right `epic_brief_id` + actor_ref.

## Notes
- Reuse the existing spawn path; only the charter body + packet vars + the MAIN affordance are new.
[6] participant_joined flower-231-worker: (no body)
[7] unblocked flower-231-worker: Unblocked — #231 reached complete.
[8] participant_joined flower-orchestrator: (no body)
[9] status_change flower-orchestrator: (no body)

Recommended linked context:
{
    "todos": [],
    "scratchpads": []
}

Execution notes:
- Treat the brief as the source of truth.
- Keep work scoped to this dispatch request.
- Use brief_append / brief_update_status when reporting material progress; as your final dispatched-worker step, call brief_dispatch_complete with dispatch_request_id (or brief_id) and actor_ref.
- Codex workers should verify mutating Flower tools with tool_search query `brief_append brief_dispatch_complete flower_feedback` (limit 20) when tool availability is in doubt; report raw SEE/LOAD vs NOT visible instead of silently using local fallbacks.
- Add a git commit trailer `Brief: #232` to every commit for this brief so flower can exact-link commits back to the brief.