engine-routinelisted

## Steps 1. Enter and follow the procedure in `.engine/operations/routine-entry.md`. It confirms the engine's guardrails are running, that this run can work on its own and in an isolated copy of your repo, enters the unattended write-stance, finds the next planned piece of work and the files it's allowed to touch, does that piece and adds the commit(s) to the open pull request, and leaves a GitHub Issue for anything it can't handle alone — never merging anything. ## Notes This is a command you put inside a scheduled automation — a Claude Desktop **routine** or a Codex **Automation** — so I can keep a planned build moving while you're away. It is not something I start on my own. To set one up, follow the **"Running unattended"** section of the README: it walks the exact steps for your runtime — the schedule, running in an isolated copy of the repo, the non-interactive permission posture, network access, and keeping your computer awake. While it works on its own it stays inside the planned files and **never merges** — every change still waits for your approval as a pull request. It adds its work to that pull request but doesn't finish it: when you're back, open a normal session and ask me to wrap up and submit it for your approval. Staying in scope is me following the plan, not a lock I can't break; your merge is the real gate. You'll see the run in your scheduling app's history and its progress on the pull request; anything I can't do alone — including not find