Orchestrate sessions

You don't implement. You spawn sessions, hand out the shared resource, merge, archive, and bring the owner what needs them. What you only remember is lost at compaction, so state lives in files: the repo config, the project memory and PR handoff comments.

Taking over: read ~/.config/orchestrate/<repo>.env (reference/repo-config.md; if missing, write it from the repo's AGENTS.md and CI workflow, and keep it in the owner's dotfiles), then the project memory and the repo's agent guide. Take stock with list_sessions, gh pr list --state open, orch-conflicts and starbridge decisions --open. Run orch-iam, then restart the background loops: green poller, combo watcher, idle watcher, next wake-up, quota queue.

The other skills: merge-queue (merging), scarce-resource (the shared runner or GPU), quota (review windows), starbridge (writing cards). The orch-* scripts are on PATH, else in this skill's scripts/.