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. ## Step 0 — Pick the flow Three flows, differing only in **what they are allowed to write**. Ask the user which one, unless they already said. | Flow | Writes to | Produces | Danger | |---|---|---|---| | **A — Rehearsal** | nothing outside the local worktree; `origin` is read-only | log + summary | none | | **B — Real, no rehearsal** | `origin`: integration branch, force-pushed PR heads, merged/closed PRs | log + summary, written live | **high — requires explicit approval** | | **C — Real, from a rehearsal** | same as B | a *new* log + summary that reference the rehearsal's | moderate — every resolution was rehearsed first | **Default: A, then C.** Run the rehearsal, r