fix(model-routing): commit-changer resolves step→hash refs on apply; edge-case resume notes (release NEED-DECISION, commit-change skip)

skills/commit-change/SKILL.md

@@ -80,6 +80,9 @@ AskUserQuestion:
   message judgment stays on the sonnet subagent (never redrawn inline on
   the session model); show the redrawn plan and re-ask.
 - `skip` → exit cleanly, no commits created, no `MODE: apply` dispatch.
+  Note: if the propose run created a `chore/*` branch (gitflow aiguillage
+  off a protected base), that branch stays checked out with the work
+  uncommitted — mention it so the user isn't surprised by the branch switch.
 
 ## STEP 3 — Gate 2: capitalize approval
 

skills/release-candidate/SKILL.md

@@ -63,7 +63,11 @@ prompt: "SPAN: prep <X.Y.Z>
 Parse the `RELEASE-EXEC REPORT`:
 - `STATUS: DONE` → continue to STEP 4, carrying the `TESTS` line forward.
 - `STATUS: NEED-DECISION` → surface the exact question to the user, STOP
-  (don't guess the CHANGELOG wording on its behalf).
+  (don't guess the CHANGELOG wording on its behalf). Resume note: prep may
+  have already run `gitflow start release` (the release branch exists) — do
+  NOT re-dispatch `SPAN: prep` (it would BLOCK on the existing branch);
+  resolve the CHANGELOG on the current release branch, commit the prep, then
+  resume at STEP 4.
 - `STATUS: BLOCKED` → surface the blocker verbatim, STOP.
 
 ### STEP 4 — HUMAN GATE: when to release