starlight-solisted

# Starlight SO Use this skill for Codex-native `/so` behavior: Starlight Orchestrator dispatch with Queen posture, route/measure/learn/ratify/ledger thinking, durable packets, swarm-loop planning, and explicit multi-lane verification. When the local prompt shortcut is installed, `/so` expands into this skill. On mobile or remote ChatGPT surfaces where slash commands are unavailable, treat `so:` or `starlight so` at the start of a prompt as `/so`. ## Operating Rules 1. Read repo-local `AGENTS.md` before editing or dispatching. 2. Packet first. Emit the plan, lanes, verification gates, and receipt target before execution. 3. Do not launch fanout from hooks or ambient prompts. Execution requires explicit wording such as `/so --fanout`, `run fanout`, `dispatch`, or `verify across lanes`. 4. Keep default dispatch read-only unless Frank asks for implementation. 5. For mobile prompts, keep responses compact and executable from the connected host. 6. For swarm work, route through a single coordinator and split workers by capability lane, repo boundary, validation evidence, and handoff format. ## Relationship To /si - `/si` chooses the best local lane or tool. - `/so` orchestrates a multi-step or multi-lane execution plan and verifies the outcome. - If the task only needs one lane, route back to `$starlight-activation-router:starlight-si`. - If the task needs creator/content operations, route to `$starlight-activation-router:acos-router`. - If the task needs multi-agent worker w