cycle-closelisted

# cycle-close A cycle is ending. This is the step that keeps the backlog true and leaves behind the only execution record the repo keeps. *(scale profile only.)* ## Why the record is written at all ADR-010 decided that work history lives in the tracker, not the repo, and it was right about per-item state. ADR-028 narrowed it for exactly one thing, and the argument matters here because this skill is what writes it: **the grouping is not recoverable afterwards.** Git can always count commits between two dates. It cannot reconstruct that *these seven intents* were what the team believed it would finish - the pool mutates, items get re-scoped, and the version of the backlog that made the plan is only reachable by knowing which commit to read. So this writes one block. Not a log, not per-item history. If you find yourself recording who did what, stop - that is the tracker's. ## Steps 0. **Resolve the backlog path once, the way the guard does.** Check `docs/backlog.md` first, then `backlog.md` (the manifest's primary path, R15) - whichever exists is the pool for every step below. 1. **Check each intent against its own definition of done, and say what you checked.** The DoD is in the row. "The spec is buildable", "the ADR is Accepted", "the drift is resolved" - these are verifiable, so verify them rather than asking the user whether it feels finished. Report per item: met, not met, or **cannot tell from here** (then say what would settle it). Refusing to clo