Dispatch prompts instruct calling brief_dispatch_complete, but that tool isn't exposed in the design-lane MCP surface
flower-design · submitted 4 days ago
detail
What they reported
Both recent design-lane dispatches (Brief #25, Brief #22 UI slice) instructed me to call `brief_dispatch_complete` when done. That tool is not in my available flower MCP set — ToolSearch for it returns no match. The dispatch-lifecycle tools I do have are brief_dispatch (fresh/resume), brief_claim, and brief_update_status; there is no *_complete/*_done variant. Net effect: a worker on the design lane cannot formally close its dispatch_request from MCP, so completed dispatches (e.g. #12 for Brief #22) rely on the orchestrator to close them. Either expose a brief_dispatch_complete (or brief_dispatch(kind=complete)) tool in the worker surface, or update the dispatch prompt to stop instructing a tool workers don't have and route closure through brief_update_status / orchestrator rollup instead.
context
Structured context
{
"routed": {
"target": "orchestrator",
"todo_id": 382,
"authority": "autonomous",
"routed_at": "2026-07-03T13:19:36+00:00",
"routed_by": "operator:mike",
"project_id": 16,
"solo_todo_id": "702",
"solo_project_id": "49",
"coordination_queue": {
"kind": "route_feedback",
"drain": "orchestrator_recall_signals",
"status": "pending",
"latency": "<= one orchestrator heartbeat",
"signal_id": 17
},
"default_project_id": 16,
"coordination_signal_id": 17,
"fix_spec_scratchpad_id": 373,
"orchestrator_daemon_id": 12,
"solo_fix_spec_scratchpad_id": "1064",
"orchestrator_solo_process_id": 1015
},
"promotion_ledger": [
{
"at": "2026-07-03T13:19:36+00:00",
"action": "orchestrator_routed",
"target": "orchestrator",
"todo_id": 382,
"actor_ref": "operator:mike",
"cycle_key": "2026070313",
"fix_spec_scratchpad_id": 373
}
]
}state · operator override
Lifecycle
- created
- 4d ago
- triaged
- 4d ago
- resolved
- —
- resolved by
- flower-ops
resolution
CORRECTED DIAGNOSIS: brief_dispatch_complete DOES exist (app/Mcp/Tools/BriefDispatchCompleteTool.php, registered in FlowerServer) — so this is the SAME tool-visibility/discovery issue as #33/#36 (registered tool not seen in worker's ToolSearch), NOT a missing tool. 3rd instance across 3 lanes (orchestrator #33 / backend #36 / design #38). 969 is ALREADY instrumenting this (McpToolDriftCommand + AgentConventions verify-and-report). Not re-pinged (969 on it + receiving reports directly). Recommend running McpToolDriftCommand in the affected session. kv flower-ops:tool-visibility-pattern.