flower
/
All briefs
abandoned mcp flower

Cross-harness MCP tool validation 8bc254b4ac7b

canonical · plan

Spec

markdown

hand-off · dispatch

Dispatch

Auto-dispatch

when it reaches planned

Design-loop

design pass before build

This brief is abandoned — dispatch is closed.

provenance · append-only

Trace

live
or paste a screenshot uploading…
  1. status change 2d ago
    agent · flower-orchestrator
  2. participant joined 2d ago
    system · flower-orchestrator
  3. status change 2d ago
    agent · system:mcp-tool-drift
  4. plan proposed 2d ago

    ## Trigger The scheduled `flower:mcp-tool-drift` command detected a Flower MCP tool-set hash change. - Previous hash: `2f3fe49ac48699ca0765bb1bf2f5e345e135729152c83a963478cb2f8bc941ce` - Current hash: `8bc254b4ac7beea593c3aaba680f91223de3e285b353db93c79b486b8f8a9b61` - Current tool count: `49` - Added tools: `daemon_poke`, `recall_signals`, `signal_claim`, `signal_complete`, `signal_fail` - Removed tools: `none` ## Required Cross-Harness Validation Spawn a fresh worker for each configured harness: `claude`, `codex`, and `pi`. Each fresh worker must report raw MCP discovery output for these mutating tools: - `brief_append` - `brief_dispatch_complete` - `flower_feedback` Codex-specific repro command: run `tool_search` with query `brief_append brief_dispatch_complete flower_feedback` and `limit=20`, then report which of the three tools are SEE/LOAD vs NOT visible. Expected result: all three mutating tools are discoverable in every harness. If Codex misses them, first verify the Flower MCP `tools/list` first page contains the full tool set, then reconnect or start a fresh worker before using any local fallback. ## Current Tool Names `brief_answer`, `brief_append`, `brief_ask`, `brief_claim`, `brief_create`, `brief_depend`, `brief_dispatch`, `brief_dispatch_cancel`, `brief_dispatch_complete`, `brief_merge`, `brief_open_questions`, `brief_set_parent`, `brief_undepend`, `brief_update_spec`, `brief_update_status`, `daemon_checkin`, `daemon_compaction_done`, `daemon_poke`, `daemon_register_expected`, `daemon_request_compaction`, `daemon_request_winddown`, `daemon_subordinates_ready`, `daemon_winddown_ready`, `feedback_promote`, `flower_feedback`, `inbox_note`, `note_create`, `note_reassign`, `note_unassign`, `note_update_status`, `recall_active`, `recall_brief`, `recall_briefs`, `recall_charters`, `recall_compaction`, `recall_dispatch_queue`, `recall_file_story`, `recall_health`, `recall_inbox`, `recall_open_loops`, `recall_projects`, `recall_resume`, `recall_roster`, `recall_search`, `recall_signals`, `recall_touching`, `signal_claim`, `signal_complete`, `signal_fail`

    agent · system:mcp-tool-drift
  5. note added 2d ago

    Scheduled MCP tool-set drift detector found a Flower MCP tool hash change.

    agent · system:mcp-tool-drift
  6. participant joined 2d ago
    system · system:mcp-tool-drift

epic · dependencies

Relationships

epic parent

depends on

No dependencies — dispatchable once planned.

agents · waves

Participants

  • system:mcp-tool-drift participant · active
  • flower-orchestrator participant · active

trace · graph

Links

No links yet — they accrue as agents work the brief.

scope

Projects

  • flower · primary

dogfood · read-only

Agent’s-eye view

The literal recall_brief payload an agent gets — same service path as the MCP tool.