implementing-batchlisted

# Implement Run a decided change to completion in one pass. The enemy is checkpoint implementation: repeated confirmation of decisions already made. The overcorrection is unchecked autonomy: one wrong assumption propagates through every file. ## Activation gate For a decided change, count these facts after initial inspection: more than two source/test/config files must change; a dependency is added; a public signature changes; a persisted format or security boundary is crossed; a required file was not covered by the inspection. Zero facts means read the ranges, make the direct edits, run their check, report, and stop, applying the test-design row first when the change is risky or adds or changes an automated test. One or more runs the loop. A change the user wants test-first (test-first, TDD, red-green, write the test first, a bug with a reproduction) runs the loop with `## Test first` at any file count, because the two-file shortcut has no red run. ## Context discipline - Address files by repository-root-relative or absolute paths. Never chain `cd &&` and never pipe a test or build runner, because both hide which command failed and its exit code. - Read ranges with an offset and a limit and scope every grep to a path; read here only the ranges you will edit. ## The loop 1. **Orient.** When a file named implement-next.md exists under the directory `git rev-parse --git-dir` prints, read it first: it holds a previous context's task list and remaining edits; delete it on