ccb-self-recover

# CCB Self Recover Use this skill for runtime recovery after diagnosis. Mutations must go through CCB control-plane commands. Raw tmux mutation and direct runtime-file writes are forbidden. ## Recovery Gates Before any mutation: 1. Confirm maintenance intent from the user, such as "fix", "recover", "restart if safe", "apply this config", or "make CCB healthy". 2. Read the current mounted daemon graph. The target must be a current daemon-graph agent for clear or restart-like actions. 3. Check busy/pending state: - `ccb ps` - `ccb queue --detail <agent|all>` - `ccb pend --inbox --detail <agent>` - `ccb trace <id>` when the issue involves active or pending lineage 4. Check `ccb fault list`. If active fault-injection rules affect the target, treat them as diagnostic evidence. Clear them with `ccb fault clear <rule_id|all>` only when the user intended maintenance and the rules are known test residue. If a rule is recent, or its task/reason fields could represent an active drill, ask before clearing unless the user explicitly asked to clear fault-injection rules. 5. Choose the least disruptive supported action. 6. Report exact commands, gates, affected agents, blockers, and what remains unchanged. If the target is unknown, busy, has queued work, has pending reply delivery, or has a pending callback continuation, stop and report blockers. ## Provider/API Or Startup-Input Recovery For provider/API failures or changes that affect provider pro...