dev-commit

# Dev Commit Make one intentional, verified commit without sweeping in unrelated work. ## Commit Contract 1. Check repository state with `git status --short --branch`, `git diff --stat`, and `git diff`. 2. Identify the files that belong to the requested change. Treat pre-existing user edits, local config, generated artifacts, dependency caches, build outputs, and unrelated formatting churn as out of scope unless the user explicitly includes them. 3. Run appropriate validation before committing. Prefer the repo's targeted tests, lint, typecheck, build, or documented verification commands. Record skipped validation with the reason. 4. Stage only intended paths. Prefer explicit pathspecs such as `git add path/to/file` over `git add .`. 5. Re-check with `git diff --cached --stat`, `git diff --cached`, and `git status --short`. 6. Write a concise conventional commit message: `<type>(optional-scope): <summary>`. 7. Commit, then report the commit SHA, final status, validation commands, and any unstaged/untracked files left behind. ## Guardrails - Do not commit secrets, credentials, `.env` files, local machine config, caches, coverage, logs, screenshots, or generated files unless the change explicitly requires them. - Do not stage another person's unrelated edits. If intended and unrelated changes are mixed in one file, use an interactive or patch-based staging flow and review the staged diff carefully. - Do not amend, rebase, force-push, reset, or delete branches unless the use...