housekeepinglisted

# The closing pass — bringing the admin back in line with the work ## What this settles, and what it never claims **It settles the ADMIN of development, not the work itself**: what has been done is written where a cold reader finds it, nothing is left uncommitted by accident, and what is still owed is stated. 🔴 **It never claims the tracking doc is "true".** No pass, and no check, can establish that — the control that watches the neighbouring workspace says so in its own header, and that is the right answer. What this pass establishes is that the doc has been **brought up to date deliberately**, by someone who read the work. ## Step 1 — the inventory The inventory is countable and decomposable. **Delegating it is a cost question, not a rule** — the underlying one is *delegate as soon as it costs LESS* *([`docs/claude-code-setup.md`, "Delegating"](../../docs/claude-code-setup.md))*, and the six `git` commands below cost less run directly than wrapped in a subagent launch. Delegate when the inventory actually spans several projects, or when it grows past what one pass reads comfortably; otherwise run it here. ⚠️ **If it is delegated**: a cheaper model, a parallel workflow over one sequential pass, and a prompt carrying the three opt-ins — *"does the work itself"*, *"does not re-delegate"*, *"does not call the advisor"*. A launch omitting any of them is **refused** by `verify-delegation.sh`. What the inventory brings back, per repository *(the code one and the neighbouri