atomic-commitlisted

# Atomic Commit Preserve historical truth: every commit must be a complete repository state that actually existed on disk, was tested in exactly that form, and was vetted by a human. A stranger must be able to check out any commit and encounter a coherent change with green tests. Atomicity begins when choosing the work, not when staging it. A small-looking commit assembled afterward from selected hunks is not atomic. ## Non-negotiable invariants - Green before every commit is absolute. Never create a failing, WIP, checkpoint, or “fixed by the next commit” commit. - Incremental refactoring, tests, prescribed scans, and documentation are pre-commit work. Complete and verify them before presenting the feature commit for review. - Commit the entire working-directory state. Never use partial staging, path-limited staging, `git add -p`, or temporary reversal to manufacture commit boundaries. - Run all Git and verification commands from the repository root. Establish it with `git rev-parse --show-toplevel`; do not assume the current directory is the root. - Every untracked file receives an explicit disposition: add, ignore, or delete. Make evident decisions autonomously; ask the human only when the correct disposition is uncertain. - A human reviews the complete proposed commit after verification and before `git commit`. - Human review is part of the rapid local microcommit loop, not a reason to enlarge batches or postpone a completed green step. Many human-reviewed commits in a