integration-branchlisted

# Integration branch Merges a set of PRs into one branch so they can be tested together, in dependency-correct order, recording the run as it happens. Two documents come out of it: - a **log** written continuously — [`docs/integration/log-format.md`](../../../docs/integration/log-format.md) - a **summary** written at the end from the log — [`docs/integration/summary-format.md`](../../../docs/integration/summary-format.md) Read both formats before starting. The log is not a write-up at the end; it is appended after every action, because the obstacles are the part worth keeping and they are the first thing memory loses. **This skill never pushes to `main` and never merges a PR into `main`.** It produces an integration branch and two documents. Landing the PRs is a separate, explicitly-requested operation. ## The branch has an expiry — this repo retired the other kind This repo deleted its long-lived integration branch on 2026-08-12 and landed all 20 open PRs onto `main` individually instead. The decision and the stale-ref audit behind it are in `docs/integration-branch-retirement-2026-08-12.md` — open in PR #666, so link it once that lands — and the rule it states is the one this skill operates under: > An integration branch is a staging area with an expiry, not a parallel trunk. So: - A branch this skill creates exists to **test a set of PRs together**, and is deleted once `main` holds its content. Deleting it costs nothing when a backup ref points at the same commi