Launch OpenShell Gator

Launch and supervise the repository's headless gator sandbox agent through OpenShell. This skill covers the operator workflow around scripts/agents/run.sh; the in-sandbox review and state-machine policy remains the gator-gate skill baked into the gator payload.

For gator's PR/issue validation policy, load gator-gate inside the launched sandbox. For generic sandbox CLI usage, use openshell-cli. For unhealthy gateways or sandbox startup failures, use debug-openshell-cluster after the launch preflight identifies a gateway/runtime problem.

Non-Negotiable Rules

• Keep normal gator launches supervised: use --watch --background and let the in-sandbox supervisor own sleeping and relaunching bounded cycles.
• Do not add passive sleep loops in the operator session to watch gator. Check logs or status once, then report the current state or launch a proper watcher outside the model session only when explicitly asked.
• Do not change the default gator model in scripts/agents/gator/agent.yaml for experiments. Use CODEX_MODEL=... and, if needed, a temporary --from Docker context or --codex-bin override.
• Do not push to contributor branches, approve, merge, post /ok to test, or broaden gator scope unless the operator explicitly authorized that action.
• Scope each launch prompt to the requested issue/PR set. Avoid repo-wide gator scans unless the operator asked for repo-wide processing.
• Leave unrelated local files alone, including .opencode/ artifacts and old gator logs unless the user asks for cleanup.

Key Paths