polish-new

# Pre-Release Polish A review is finished when a review of its own fixes warrants no further edits - not when the fixes are written, not when checks pass. Evidence beats judgment: a finding that cannot be reproduced from its own citations does not survive. The fix pass is where the next round's defects come from, so it gets reviewed like any other code. Findings live in files, not in this conversation - context can be compacted away mid-run; if you are resuming after a compaction or interruption, re-read `ledger.md` and the saved agent reports before continuing. They are the source of truth, not the summary. A base ref may be passed as an argument; Phase 2 uses it for scope. ## Phase 0: Orient Work in the repository under review - it may be a worktree, not the current directory. Establish state there: ``` git rev-parse --abbrev-ref HEAD git status --short git diff --stat ``` Create the run directory `.agents/polish/<YYMM-DD-HHMM>-<slug>/` with an `agents/` subdirectory, and start `ledger.md` recording the reviewed sha (`git rev-parse HEAD`) and, as they launch, one row per agent (lens, shard, output file, launch time, plus any run identifier the harness exposes). Base ref and diff stat are backfilled at the end of Phase 2. Findings get ledger rows as reports arrive, not later. If `.agents/` is not already ignored, add `.agents/polish/` to the project's ignore file - run artifacts are working state, never committed. The reviewed sha makes this review a certificate abou...