Cross-harness MCP tool validation 3fea07f5f2d4

## Trigger The scheduled `flower:mcp-tool-drift` command detected a Flower MCP tool-set hash change. - Previous hash: `20a663fa5c4b517c720dac4dc5c75c64723182f0bcced525f9ca8b4859eb4480` - Current hash: `3fea07f5f2d4ee92981752799ef0f941cf9fea933e32da045cccb3444f97a218` - Current tool count: `41` - Added tools: `none` - 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_register_expected`, `daemon_request_compaction`, `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_touching`