flower
/
All briefs
planned mcp flower

Cross-harness MCP tool validation a3fb9175f4aa

Dispatch

canonical · plan

Spec

markdown

hand-off · dispatch

Dispatch

Auto-dispatch

when it reaches planned

Design-loop

design pass before build

kind

No dispatch requests yet — dispatch above to generate a copy-paste packet.

provenance · append-only

Trace

live
or paste a screenshot uploading…
  1. status change 13h ago
    agent · system:mcp-tool-drift
  2. plan proposed 13h ago

    ## Trigger The scheduled `flower:mcp-tool-drift` command detected a **discovery-material** Flower MCP tool-set change. - Previous hash: `389419d364180edd91e5eaf31c3403849e4b35ef12cbf6fa95f1335471c1e49e` - Current hash: `a3fb9175f4aacb9ca1839e614c5b70ec6cb161f4ffd29ebb9494bc05fcc1ca66` - Current tool count: `70` - Added tools: `decision_discuss` - Removed tools: `none` - Definitions changed: `recall_decisions` - First-page mutating tools added: `decision_discuss` - First-page mutating tools removed: `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_auto_dispatch_signal`, `brief_claim`, `brief_create`, `brief_depend`, `brief_dispatch`, `brief_dispatch_cancel`, `brief_dispatch_complete`, `brief_merge`, `brief_open_questions`, `brief_request_review`, `brief_review`, `brief_set_epic_lead_mode`, `brief_set_parent`, `brief_undepend`, `brief_update_spec`, `brief_update_status`, `daemon_checkin`, `daemon_compaction_done`, `daemon_park`, `daemon_poke`, `daemon_register_expected`, `daemon_request_compaction`, `daemon_request_reset`, `daemon_request_winddown`, `daemon_reset_handoff`, `daemon_retire_predecessor`, `daemon_start_reset`, `daemon_subordinates_ready`, `daemon_successor_ready`, `daemon_unpark`, `daemon_winddown_ready`, `decision_ack`, `decision_answer`, `decision_ask`, `decision_ask_set`, `decision_discuss`, `decision_withdraw`, `epic_delegate`, `epic_return`, `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_decisions`, `recall_dispatch_queue`, `recall_file_story`, `recall_health`, `recall_inbox`, `recall_open_loops`, `recall_projects`, `recall_refs`, `recall_resume`, `recall_roster`, `recall_search`, `recall_signals`, `recall_touching`, `signal_claim`, `signal_complete`, `signal_fail`

    agent · system:mcp-tool-drift
  3. note added 13h ago

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

    agent · system:mcp-tool-drift
  4. participant joined 13h 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

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.