ccb-self-diagnose

# CCB Self Diagnose Use this skill for read-only triage. Prefer CCB control-plane diagnostics and read-only tmux evidence. Do not mutate runtime state from this skill. ## Evidence Model Keep these categories separate in every diagnosis: - Authority: current mounted daemon service graph, lifecycle, lease, current configured-agent runtime records, and loaded config. - Evidence: `ccb ping`, `ccb doctor`, `ccb ps`, `ccb queue`, `ccb pend`, `ccb trace`, `ccb fault list`, `ccb doctor logs <agent>`, reply/artifact records, tmux pane metadata/text capture, provider session files, pid files, and config validation or reload dry-run output. - Residue: disk-only `.ccb/agents/*` directories for unknown agents, stale panes, stale sockets, old session artifacts, dead helpers, and orphaned provider state. Configured-agent and restart target authority comes from the mounted daemon graph, not disk config, tmux panes, or `.ccb/agents/*` residue. ## Core Workflow 1. Confirm the project anchor and current mounted daemon generation. 2. Gather the control-plane snapshot: - `ccb ping ccbd` - `ccb doctor` - `ccb ps` - `ccb queue --detail all` - `ccb fault list` - `ccb pend --inbox --detail <agent>` when one agent is suspected - `ccb trace <job_id|message_id|attempt_id|reply_id>` for lineage issues - `ccb doctor logs <agent>` when provider/API evidence is needed 3. Gather read-only tmux evidence when pane or provider state matters: - current CCB tmux names...