maintainlisted

# maintain — a maintainer's circuit for this repo This is a **workflow**, not a rulebook. The rules live in `AGENTS.md` and `docs/RELEASING.md` and are cited here by section, never restated: two copies drift, and drift between rule files is the failure mode this repo exists to kill. Read `AGENTS.md` before the first tool call of a cycle; when it and this file disagree, `AGENTS.md` wins and this file is the thing to fix. The circuit below was run twelve times over two days. The numbers in it are measured on those runs, not estimated. ## 0. Coexistence — before anything Other sessions may be working this same repo. - `ListAgents` first. If another session is live, exchange **file sets** by message before either of you starts: two cycles that touch disjoint files can run at once, two that touch `src/core/facilitator/executors/build.ts` cannot. - **Never merge while another session's release is running** — and note there is NO detector for that. `scripts/release.sh` writes no marker (only a merge wave does, §2), so this is a question you ASK: `SendMessage` each live peer "is a release in flight?". One signal you can read yourself, and it is a hint rather than a check: a `release: X.Y.Z` commit on `origin/main` with no `vX.Y.Z` tag yet means one is mid-flight. A release moves `main`, tags it and pushes; a merge wave in the middle of that is how a half-released state happens. - When a release lands mid-cycle, the released CHANGELOG section becomes immutable (`A