Prompts

You are being dispatched from flower Brief #280: Cross-harness MCP tool validation 914de47aee43

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

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: choose an appropriate branch
- worktree: not specified
- kind: fresh

Current brief spec:
## Trigger
The scheduled `flower:mcp-tool-drift` command detected a **discovery-material** Flower MCP tool-set change.

- Previous hash: `4b1d6e3fa232bef9f103e6ffdfa437b7aca1e2fd6c5abe73e0b9f2d7bc006a24`
- Current hash: `914de47aee43e533e1e1b6e91e8863cbbd4b3e46f6f19b978892409b65fc2bbd`
- Current tool count: `71`
- Added tools: `brief_design_loop_signal`
- Removed tools: `none`
- Definitions changed: `none`
- First-page mutating tools added: `brief_design_loop_signal`
- 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_design_loop_signal`, `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`

Recent/key trace events:
[1] participant_joined system:mcp-tool-drift: (no body)
[2] note_added system:mcp-tool-drift: Scheduled MCP tool-set drift detector found a discovery-material Flower MCP tool change.
[3] plan_proposed system:mcp-tool-drift: ## Trigger
The scheduled `flower:mcp-tool-drift` command detected a **discovery-material** Flower MCP tool-set change.

- Previous hash: `4b1d6e3fa232bef9f103e6ffdfa437b7aca1e2fd6c5abe73e0b9f2d7bc006a24`
- Current hash: `914de47aee43e533e1e1b6e91e8863cbbd4b3e46f6f19b978892409b65fc2bbd`
- Current tool count: `71`
- Added tools: `brief_design_loop_signal`
- Removed tools: `none`
- Definitions changed: `none`
- First-page mutating tools added: `brief_design_loop_signal`
- 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_design_loop_signal`, `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`
[4] status_change system:mcp-tool-drift: (no body)

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; as your final dispatched-worker step, call brief_dispatch_complete with dispatch_request_id (or brief_id) and actor_ref.
- Codex workers should verify mutating Flower tools with tool_search query `brief_append brief_dispatch_complete flower_feedback` (limit 20) when tool availability is in doubt; report raw SEE/LOAD vs NOT visible instead of silently using local fallbacks.
- Add a git commit trailer `Brief: #280` to every commit for this brief so flower can exact-link commits back to the brief.
- Need an operator call while working this brief? A question ABOUT THIS BRIEF -> brief_ask(280, ...); a standalone decision not tied to the brief -> decision_ask(...). Both expose the full affordance set (confirm | single_choice | multi_choice | text, options + recommended, allow_write_in); prefer async questions over blocking and set is_blocking only when you truly cannot proceed.
- Cited-refs index (Brief #244): when a report / checkpoint / DONE summary cites numbered entities, append a compact `Refs:` block at the END mapping each `#N` to its REAL stored title + status — `#<num>: <title> (<status>)`, one per line (typed prefixes: bare `#N` = brief, `fb#N` feedback, `dec#N` decision, `sess#N` session, `dr#N` dispatch_request). Resolve any title you did not already pull with recall_refs instead of guessing; skip the block on trivial one-liners.