happier-commit-worktree

# Happier Commit Worktree Turn an existing moving worktree into a sequence of reviewable commits without treating file count, directory boundaries, or the current index as truth. Preserve all bytes on disk, prove what each commit contains, and leave uncertain material uncommitted with a specific reason. A large-worktree request is a campaign, not a request for one commit or one analysis wave. Continue recon, packet preparation, committing, and residual classification until every current path is committed or has an evidence-backed exclusion or blocker. Producing a few commits while commit-ready paths remain is incomplete execution unless the user explicitly pauses the campaign. ## 1. Establish authority and safety Require an explicit user request to commit. Analysis alone does not authorize staging or commits. Apply these invariants throughout: - Never run `git reset`, `git restore`, `git clean`, `git checkout`, `git switch`, or an equivalent destructive operation. - Never overwrite, delete, or normalize unrelated work merely to make status clean. - Never trust or wholesale-commit the shared index. Stage every commit from explicit paths or hunks in a fresh private index. - Treat the checkout as live. A path can change before, during, or after a commit. - Serialize HEAD mutations even when reconnaissance and validation run in parallel. - Use Conventional Commit subjects and explanatory bodies. - Commit only changes whose intent, ownership, and suitability are understood. ...