clean-up — make the change belong

The code works. This pass makes it look like it was always meant to be there: matching the conventions of the code around it, with no scaffolding, dead ends, or "clearly bolted on" smell left behind.

This is not a generic code-quality pass or strict structural review (use thermo-nuclear-code-quality-review for that) and not a product/UX rework of pre-existing screens or flows (that is product-design). It is scoped to the change you just made and how that change sits next to its neighbors.

When to use

The user has just finished a fix or feature and wants it integrated cleanly. The signal is "make this fit / tie this off", not "make the codebase better" and not "add more behavior".

The one rule

Behavior must not change. Every phase checks against this. It is what keeps this pass from sprawling into a rewrite. If a finding can't be addressed without changing what the code does, it is out of scope — report it, don't do it.

Phase 1 — Pin the blast radius

Run git diff against the base branch and git status for untracked files. Enumerate exactly what changed and the set of files touched.