session-autonomous

# session-autonomous - work approved GO items unattended A credo session runs in exactly one mode - `active`, `passive`, or `autonomous` - set by the `/credo:session-*` commands and surfaced on every prompt by the session-mode inject line. This skill is the umbrella for **autonomous** mode: the user is away, you work approved GO items on your own, keep the session alive, respect the budget caps, notify via ntfy, and hibernate cleanly at the end. It is the dach / umbrella over the credo building blocks - it wires them together and adds the unattended-run machinery, and it duplicates none of their content. Autonomous mode is only in force while the autonomy flag `credo-autonomy-active` is set - which is what the `/credo:session-autonomous` command sets (and it lifts the `credo-autonomy-paused` opt-out). If that flag is not set, do not run the keep-alive or hibernate behavior below. ## Bootstrap - enter the mode only on an unambiguous grant This skill may LOAD on a full-autonomy / AFK-handoff intent, but entering autonomous mode requires an unambiguous, explicit user grant. If this skill loaded because the user just handed off full-autonomy / unattended / AFK work and the mode is NOT yet set (no `credo-autonomy-active` flag), FIRST enter autonomous mode by running `/credo:session-autonomous`. That command runs `session-mode-set.sh autonomous`, sets the flag, and activates the rules below - which resolves the chicken-and-egg problem of needing the mode set before this skill's...