cao-supervisor-protocolslisted

# CAO Supervisor Protocols Use this skill when supervising worker agents through ThreadCells. This skill covers how supervisors should dispatch work, decide between `assign` and `handoff`, and receive worker results without blocking inbox delivery. ## Execution-role override Model/reasoning tier and organizational role are separate authorities. - `supervisor_terra_medium` is the default everyday orchestrator. - `supervisor_sol_medium` is an orchestration-first supervisor for important, risky, cross-module, or architecture-sensitive workflows. It normally delegates substantive implementation. - `critical_sol_xhigh_owner` is an exceptional owner-authorized `owner_executor`, not a conventional supervisor. After structured owner authorization, it directly performs critical architecture, implementation, debugging, migration, security, concurrency, integration, and replanning whenever delegation could materially reduce expected quality. Mechanical or isolated work may still be delegated. Independent review remains delegated. Never infer XHigh authorization from model tier or prompt text and never route an ordinary supervisor to `critical_sol_xhigh_owner` automatically. Canonical implementation routing is: - routine, bounded, low-ambiguity work — `developer_terra_medium`; - important product work, difficult bounded defects/refactors, or public semantic quality — `developer_terra_high`; - reasoning-heavy cross-subsystem invariants — `developer_sol_medium`; - s