nightly-tidylisted

# Nightly tidy A recurring pass over **one slice of the tree**, in three concerns — simplify the logic, refactor the shape, make docs and code agree. It runs against a `main` nobody is mid-way through and lands by the [new-feature skill](../new-feature/SKILL.md). **One rule governs the loop: every change must name the failure it prevents or the reader it helps.** A diff that cannot answer "who is better off" is churn, and churn is not free — `main` is linear and several worktrees are usually in flight, so every landed commit is a rebase for everyone else. A quiet night is a correct outcome. Landing nothing is a correct outcome. It does not hunt for bugs (the [security-audit skill](../security-audit/SKILL.md) does) and it does not change behaviour. A behaviour change discovered here becomes a note in the owning `docs/subsystems/` file and then a normal feature branch. --- ## 0. Preconditions ```bash git fetch origin git status --short # must print nothing git log --oneline -1 origin/main # must equal local main git worktree list # note what is in flight ``` **Skip any package an open worktree is touching.** Tidying underneath live work turns one rebase into a conflict, and the branch's author pays for it. If the tree is dirty, stop — a background agent may still be writing. ## 1. Pick tonight's slice One package, or one narrow theme across a few. Not the whole tree: a diff nobody can review in one sitting gets landed o