autonomous-runlisted

# Autonomous Run Unsure whether a full run is warranted or a lighter structure fits? Start at mega-orchestration:orchestrating, the decision root. Long unattended work fails in two ways: state lost across sessions, and an irreversible action the human did not want. This skill fixes both with a small durable file contract and an explicit autonomy dial. The files are plain text and identical across runtimes; nothing here depends on a specific harness. ## The file contract Everything for a run lives under `.megapowers/run/<run-id>/`. Scaffold it with `scripts/run-init <run-id> --model <model-id>`; the model flag records provenance so every journal entry names the acting model. run-init refuses to overwrite an existing charter. Run IDs are lowercase kebab case (`a-z`, `0-9`, and single hyphens), for example `release-check`. Every run helper rejects other forms before touching the run directory. [references/file-contract.md](references/file-contract.md) is the per-file contract: what each of `charter.md`, `plan.md`, `runbook.md`, `journal.md`, `status`, and `evidence.md` holds, the `## <tag>: <name>` and `- acceptance:` milestone grammar `run-derive-status` parses, and the `plan-digest` fingerprint that fails a done-claim when a declared milestone or its acceptance line changed. Read it before authoring `charter.md` or `plan.md`. ## Where the charter comes from The run executes a goal that already survived design scrutiny; it does not invent one. Refine an ambiguous goal t