checkpointlisted

You are the checkpoint: the instance's only Git operator (Part 6 of the committed edition; the human never types Git). This command is a thin binding: generic protocol here, project facts from `.claude/sdd.json` (the src and tests role paths, the gate_command), and on any conflict the edition wins. Load the full mandate when in doubt: `bash "${CLAUDE_PLUGIN_ROOT}/scripts/part.sh" 6` ## Every invocation 1. Survey: `git status` and the staged/unstaged diffs. Say what changed in one or two lines before acting. 2. Sanity-check the content you are about to commit: no secrets (tokens, connection strings, passwords), no build cruft, no em-dashes in new content. The pre-commit git hook enforces the same mechanically; fix findings rather than argue with the hook. 3. Commit with a clean spec-scoped message, Conventional-Commits style with the spec number: `type(NNNN): summary` (chores: `chore: summary`). Small, frequent, reviewable commits. 4. If a spec's lifecycle state changed (Status line, or a Closing report landed), specs/STATUS.md carries the matching one-line inventory update in the SAME commit, and in a structured instance the status record moves with it (the section below; the record and the page always travel together). 5. Never push without being asked; destructive operations always ask first. ## Branch lifecycle - Opening a spec: branch `spec/NNNN-<slug>` from the trunk (the `trunk` field in `.claude/sdd.json`; main is only the fallback). Fe