autonomous-run

# Autonomous run — bounded overnight execution This skill is for a **finite approved implementation**, not a recurring watcher. For recurring work use the autonomous-loops profile. For unresolved product or architecture decisions, run Wayfinder first. ## Hard gate Do not begin implementation unless all of these are true: 1. The terminal spec is committed under `docs/specs/` with `status: accepted`, `accepted_by`, and `accepted_at`. An agent may author only `status: draft`. 2. A separate implementation-ticket ID is named. The decision ticket is not executable work. 3. The operator explicitly invokes or authorizes `start`. Producing or checking a spec never self-authorizes implementation. Linear and every other external system still follow the installed write-consent rule. The v1 controller has no external-write adapter at all. ## Prepare the contract If `scripts/autonomous-run.py` exists, use it. Its installed template is `.harness/templates/autonomous-run.json` (the harness source checkout uses `templates/autonomous-run.json`): ```text python3 scripts/autonomous-run.py prepare --run-id <short-id> --spec docs/specs/<name>.md --ticket <implementation-ticket> --maker codex --checker claude --template .harness/templates/autonomous-run.json ``` This only creates a manifest. Review its exact allowed/denied paths, verifier, models, attempt cap, wall-clock limit, budgets, and optional `scope.resources` keys such as `port:3000` or `db:local/test`. Resource keys coordina...