Long-lived orchestrator session lacks the mutating flower MCP tools (brief_*/daemon_checkin/recall_charters) it's meant to drive

During the 2026-07-01 thedarkroom_automation daemon-spawn dogfood, this orchestrator session (Solo proc 969) could only call the recall_* read tools over the flower MCP. The mutating/daemon surface — brief_create, brief_update_spec, brief_dispatch, brief_claim, daemon_checkin, recall_charters, recall_roster — was NOT available (ToolSearch 'select:mcp__flower__recall_charters,recall_roster,daemon_checkin' returned no matches). Yet freshly-spawned Claude agents in proj 9 negotiated the FULL surface and used daemon_checkin/recall_charters/brief_* fine. So the cause is almost certainly connect-time MCP negotiation: this session connected before those tools were registered (or to an older server instance), and tools don't retroactively appear. Impact: the orchestrator — the primary persona meant to create+dispatch briefs and register/heartbeat daemons — had to bypass MCP and call BriefService/DispatchService directly via artisan tinker to file Brief #21/#22 and dispatch #21. Ideas: (a) document that orchestrators should reconnect/refresh MCP after a flower deploy, or be spawned fresh; (b) a lightweight 'refresh tool discovery' path; (c) surface a warning in recall_health when the caller's negotiated toolset is stale/partial. Not blocking (service layer worked), but it's friction on exactly the surface the orchestrator is supposed to own.

{
    "tool": "(missing) brief_create/brief_dispatch/daemon_checkin/recall_charters",
    "session": "flower-orchestrator proc 969",
    "observed": "only recall_* reads available to long-lived session; fresh agents get full surface",
    "workaround": "BriefService/DispatchService via tinker"
}

created

4d ago

triaged

4d ago

resolved

—

resolved by

flower-ops

resolution
DIAGNOSED (reported to 969): the mutating tools ARE registered in FlowerServer::$tools (BriefCreate L110, BriefDispatch L116, DaemonCheckin L105, RecallCharters L81, RecallRoster L85, etc.) — NOT a registration bug. Likely STALE MCP CONNECTION: Brief-11 spine tools added after 969's long-lived session negotiated its tool list (MCP fixes tools at connect). Fix: reconnect/restart 969's flower MCP session. If still missing after clean reconnect → real serving bug, reopen for route.