Spawn setup polish: naming, concrete cadence/heartbeat config, MIA detection, agent-tool config (pre-refine-daemon gate)

You are being dispatched from flower Brief #34: Spawn setup polish: naming, concrete cadence/heartbeat config, MIA detection, agent-tool config (pre-refine-daemon gate)

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

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/spawn-polish
- worktree: not specified
- kind: fresh

Current brief spec:
## Goal
Make the /roster daemon-spawn setup (#22) **fully working + trustworthy** before any autonomous
daemon (esp. the refine daemon #27) is turned loose. All items from the operator's review of the
spawn UI (brief #22 event 266). **This + #22 live-spawn enablement = the gate before #27.**

## Items

### 1. Charter agent-name: double-prefix bug + collision check
- **Bug:** previewing role=refine for project=flower yields `You are flower-flower-refine …` —
  `SpawnPacketService::variables()` builds `AGENT_NAME = 'flower-'.$project->slug.'-'.$role->value`,
  doubling "flower" when the slug is "flower". Fix so it never double-prefixes (don't prepend
  `flower-` when the slug already leads with it, or switch to `{slug}-{role}` / `{role}@{slug}`).
- **Collision check:** before spawning, check Solo for an existing agent/process with that name;
  if one exists, fail with a clear message or auto-suffix — never silently create a duplicate-named
  daemon.

### 2. Heartbeat cadence as config + MIA detection
- Add a flower config key for the daemon **heartbeat interval** (default ≤ 30 min; "checkin on each
  loop/wake AND at least every N min"). The charter must state the CONCRETE cadence, not "when due".
- Use it for **MIA detection**: a daemon with no checkin within its expected window (heartbeat
  interval + grace) reads missing/stale on the roster.
- **GUARD:** a daemon legitimately on a slow/dormant poll must NOT be falsely marked missing — the
  expected window must derive from the daemon's CURRENT cadence, not a fixed short value.

### 3. Polling cadence as concrete config values
- Replace the charter's vague "quickly / slower / slowest" with concrete configured values
  (e.g. fast=Xs, slow=Ymin, dormant=Zmin), so there's no interpretation — and so we can tell whether
  a daemon SHOULD have acted by now (expected-action window per cadence). Reflect in the charter text.

### 4. Agent-tool config for live spawn
- Pre-flight flagged **"SOLO_AGENT_TOOL_ID is not configured"** — the bridge needs a Solo agent tool
  id to spawn. Decide + configure which runtime daemons spawn as (recommend **Claude**, the harness
  that gets the full flower tool surface after the #29 pagination fix), via config/flower.php
  (`SOLO_DAEMON_AGENT_TOOL_ID` / `SOLO_AGENT_TOOL_ID`). Surface a clear config error when unset.
- (Pre-flight also correctly flagged active operator sessions `flower-ops` / `flower-orchestrator` —
  working as intended; the guard blocks spawning into a project with active operator sessions.)

## Acceptance
- Charter agent name correct (no double-prefix) + collision-checked against Solo before spawn.
- Heartbeat + polling cadences are concrete config values reflected in the charter
  (`SpawnPacketService`), with MIA / expected-action detection that respects the daemon's current
  cadence (no false-missing on a long poll).
- `SOLO_(DAEMON_)AGENT_TOOL_ID` configurable + validated; pre-flight clears when set.
- Tests; suite green. `Brief: #34` trailer.

## Gates / relations
Builds on #22 (spawn bridge + UI); belongs to the daemon-roster epic (#11). This + #22 live-spawn
enablement = "spawn setup fully working" — the operator's gate before starting the refine daemon (#27).

## Provenance
Operator #22 UI review (2026-07-01, brief #22 event 266): naming double-prefix + collision, undefined
heartbeat cadence, vague polling cadence, and unconfigured agent-tool id.

Recent/key trace events:
[1] participant_joined flower-orchestrator: (no body)
[2] note_added flower-orchestrator: From operator review of the /roster spawn UI (brief #22 event 266). Makes daemon-spawn fully working + trustworthy. Together with #22 live-spawn enablement, this is the gate the operator set before starting the refine daemon (#27).
[3] plan_proposed flower-orchestrator: ## Goal
Make the /roster daemon-spawn setup (#22) **fully working + trustworthy** before any autonomous
daemon (esp. the refine daemon #27) is turned loose. All items from the operator's review of the
spawn UI (brief #22 event 266). **This + #22 live-spawn enablement = the gate before #27.**

## Items

### 1. Charter agent-name: double-prefix bug + collision check
- **Bug:** previewing role=refine for project=flower yields `You are flower-flower-refine …` —
  `SpawnPacketService::variables()` builds `AGENT_NAME = 'flower-'.$project->slug.'-'.$role->value`,
  doubling "flower" when the slug is "flower". Fix so it never double-prefixes (don't prepend
  `flower-` when the slug already leads with it, or switch to `{slug}-{role}` / `{role}@{slug}`).
- **Collision check:** before spawning, check Solo for an existing agent/process with that name;
  if one exists, fail with a clear message or auto-suffix — never silently create a duplicate-named
  daemon.

### 2. Heartbeat cadence as config + MIA detection
- Add a flower config key for the daemon **heartbeat interval** (default ≤ 30 min; "checkin on each
  loop/wake AND at least every N min"). The charter must state the CONCRETE cadence, not "when due".
- Use it for **MIA detection**: a daemon with no checkin within its expected window (heartbeat
  interval + grace) reads missing/stale on the roster.
- **GUARD:** a daemon legitimately on a slow/dormant poll must NOT be falsely marked missing — the
  expected window must derive from the daemon's CURRENT cadence, not a fixed short value.

### 3. Polling cadence as concrete config values
- Replace the charter's vague "quickly / slower / slowest" with concrete configured values
  (e.g. fast=Xs, slow=Ymin, dormant=Zmin), so there's no interpretation — and so we can tell whether
  a daemon SHOULD have acted by now (expected-action window per cadence). Reflect in the charter text.

### 4. Agent-tool config for live spawn
- Pre-flight flagged **"SOLO_AGENT_TOOL_ID is not configured"** — the bridge needs a Solo agent tool
  id to spawn. Decide + configure which runtime daemons spawn as (recommend **Claude**, the harness
  that gets the full flower tool surface after the #29 pagination fix), via config/flower.php
  (`SOLO_DAEMON_AGENT_TOOL_ID` / `SOLO_AGENT_TOOL_ID`). Surface a clear config error when unset.
- (Pre-flight also correctly flagged active operator sessions `flower-ops` / `flower-orchestrator` —
  working as intended; the guard blocks spawning into a project with active operator sessions.)

## Acceptance
- Charter agent name correct (no double-prefix) + collision-checked against Solo before spawn.
- Heartbeat + polling cadences are concrete config values reflected in the charter
  (`SpawnPacketService`), with MIA / expected-action detection that respects the daemon's current
  cadence (no false-missing on a long poll).
- `SOLO_(DAEMON_)AGENT_TOOL_ID` configurable + validated; pre-flight clears when set.
- Tests; suite green. `Brief: #34` trailer.

## Gates / relations
Builds on #22 (spawn bridge + UI); belongs to the daemon-roster epic (#11). This + #22 live-spawn
enablement = "spawn setup fully working" — the operator's gate before starting the refine daemon (#27).

## Provenance
Operator #22 UI review (2026-07-01, brief #22 event 266): naming double-prefix + collision, undefined
heartbeat cadence, vague polling cadence, and unconfigured agent-tool id.

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.
- Add a git commit trailer `Brief: #34` to every commit for this brief so flower can exact-link commits back to the brief.