stack: stack-close Schritt 3 verlangt einen eigenen Bump fuer den Doku-Nachzug

Files changed:
- CHANGES.md
- VERSION
- instructions/dev/stack-close/SKILL.md

instructions/dev/stack-close/SKILL.md

@@ -86,6 +86,17 @@ and a fresh subagent starts without the session's context).
    behaviour one of these documents describes, update it now; if none did, say so rather than
    leaving the question unasked.
 
+   **A pull-through of its own needs its own bump.** This phase runs *after* `stack-dev` step 4
+   has already bumped the version, and the documents it touches are frequently the ones CI's
+   version gate watches - `types/`, `instructions/`, `tools/`, `AGENTS.md`, any
+   `<stage>/CONTRACT.md`. A commit into one of those without a `VERSION` line fails the gate
+   (`.gitea/workflows/ci.yml`, "Version gate"), whatever the session meant it as. Reading the
+   edit as "only documentation" is the trap: `types/source.md` is a document *and* a shipped
+   behaviour description, and the gate is scoped by path, not by intent. So run
+   `tools/wikitool version bump --patch` in the same breath as the pull-through commit - it
+   only advances the running candidate's counter - rather than discovering it from a red run
+   after the issue is already closed.
+
 4. **Name which model ran which phase - not only this one.** This is the handover in full, not
    a note about the tail alone: state the model for the design/version-part/boundary-judgment
    phase (`stack-dev` step 3), for the mechanical middle (code, tests, the version bump), and for