mcp-restart-ceremonylisted

# mcp-restart-ceremony Canonical (v4) procedure for reconnecting threadwork agents to the `task-board` MCP server. Follow it in order; do not improvise. The ceremony touches other agents' input buffers via `tmux send-keys`, which is a privileged operation — a wrong keystroke can silently submit garbage as if the agent typed it (F1, ceremony #963), or interrupt real work. Every step exists because a prior shortcut around it had a real failure mode. For the full step-by-step procedure (with pane-state decision table, keystroke commands, and reporting format) see [`references/playbook.md`](references/playbook.md). For the field- findings history that motivates each step see [`references/field-findings.md`](references/field-findings.md). Read both before running the ceremony for the first time in a session. ## When to fire - User asks to reconnect agents to MCP. - A `/clear` was just injected into one or more agent panes (the recycle pipeline drops the MCP connection on the way through). - Team-wide MCP disconnect signals: heartbeat anomalies, gaps in `query_audit_log`, agents reporting tool-call failures. - Snoopy or boss explicitly requests the ceremony after a restart. ## Inputs - `agents` — subset of `{boss, steve, sadie, kiera}`. Default: all four. - **Snoopy is the operator running the ceremony; do NOT run it on the snoopy pane itself.** (F4) ## Procedure summary (full detail in `references/playbook.md`) For each agent in scope, in series: ### 1. READ FIRST —