conventional-commitslisted

# Conventional Commits Turn uncommitted changes into a series of atomic, conventional commits ordered for review, using Hedgehog's commit vocabulary (`hedgehog-loop`). ## When this runs Normally the Loop commits one step at a time as it goes — schema, then contract, then repository, and so on — so there's nothing to clean up. This skill is for when that didn't happen cleanly: - A **Correction Protocol** fix touched an upstream step and several fast-forwarded dependents in one working-tree pass, needing to land as separate commits (one per step, per the Correction Protocol's own rule). - Work happened outside the Loop's discipline (exploratory changes, a session that didn't commit as it went) and needs reconstructing into the step-shaped history Hedgehog expects. ## What "atomic" means here One commit = one build step, where that applies (one schema, one contract, one repository, etc.) — not one file. A single step may span several files (a Drizzle schema + its migration, a service + its test). If work doesn't map onto a build step (tooling, config, docs), fall back to normal atomic-commit judgment: one logical change per commit. If a hunk can be removed without breaking the others in its commit, it belongs in its own commit. ## Steps ### 1. Survey the working tree Run in parallel: - `git status` (no `-uall`) - `git diff` (unstaged) - `git diff --staged` (anything pre-staged) - `git log -10 --oneline` to confirm the project's existing commit style - Run `he