Codex Orchestration Skills

I recently overhauled my Codex orchestration skills and cut the whole system back to just two: `teamwork` for bounded multi-agent work and `governed-delivery` for tracked repository changes that really need custody, exact-head review, or an external delivery gate. This is a deliberate move away from the larger cast of named roles, runtime hooks, and state machinery I had built. Ordinary work should stay ordinary. Teamwork should load when parallel agents will materially help, and Governed Delivery should load when the risk of a merge, deploy, migration, or other external action earns the extra structure. I am trying this setup now to see whether the smaller instruction surface makes Codex more predictable and easier to maintain without losing the boundaries I care about. The attached field note reflects the current in-progress v2 working tree; the released `main` branch is still v1.0.0, so this is an experiment rather than a claim that v2 has shipped.