autopilotlisted

# Booster Autopilot Read the sibling skill `../booster-command/SKILL.md`, then run command `autopilot` through that runner. Preserve the same hard boundary in Codex even though Claude hooks are not active: UI action/visual acceptance always goes to Dmitry, as do secrets, real/user/production data or persistent project files at risk, irreversible actions, external messages, publication, payments/orders, and expansion beyond existing authority. Classify security topics by blast radius and reversibility: validated task-specific temporary fixtures and sandbox-only reversible changes may be delegated. Treat remaining user text as `on <North Star>`, `status`, or `off`. Fable calls must use `~/.claude/scripts/fable_consult.sh`; never fabricate a user answer. For `on <North Star>`, state activation and persistent work activation are one operation. After validating project-local autopilot state, call `get_goal` first. Retain a matching unfinished goal. If there is no unfinished goal, call `create_goal` with an objective derived from the North Star and do not pass a `token_budget`. If a different unfinished goal exists, report that concrete conflict and do not replace or falsely complete it. `status` and `off` never create a goal. After creating or retaining the matching goal, immediately begin the first autonomous North-Star/roadmap step in the same turn; never end the activation turn with only setup confirmation or status. After the first concrete artifact contract and allowed pa