fix(docs): AGENTS.md-Contract-Prosa als Sitzungsarbeit klargestellt, doc-pull-through-Instruction (schliesst #90)

Files changed:
- AGENTS.md
- CHANGES.md
- VERSION
- instructions/dev/doc-pull-through.md
- instructions/dev/stack-close/SKILL.md
- instructions/dev/stack-dev/SKILL.md
- instructions/dev/testing-conventions.md
- instructions/dev/version-parts.md
- tools/chemenu/commands/docs_verify.py

instructions/dev/stack-dev/SKILL.md

@@ -48,7 +48,7 @@ stack development happens in the origin repo instead (see AGENTS.md's routing li
    moves, so an interrupted session leaves a body the next one can resume from, *and* rewrite it
    to its final state before closing. Both halves bind; the second is what
    [`stack-close`](../stack-close/SKILL.md) carries out once this skill's own work is published -
-   see step 5 below. An issue labelled `status/incoming` is the exception to all of that: it is a
+   see step 6 below. An issue labelled `status/incoming` is the exception to all of that: it is a
    human's stub, not a spec, and it is **never implemented as it stands** - it gets worked out and
    triaged first. Read this file before filing something for later, before editing or closing an
    issue, before picking up an incoming stub, or before deciding what to pick up next.
@@ -62,6 +62,10 @@ stack development happens in the origin repo instead (see AGENTS.md's routing li
    demo/testbed `kb/`, the measurable floors that define it, and what a reactive fix may and may
    not do to corpus content. Read it before judging whether the corpus can exercise a change, or
    before any fix that would touch `kb/` content.
+   [doc-pull-through.md](../doc-pull-through.md) - which document makes a claim about a touched
+   surface (a `wikitool` command, a stage's rules, an `AGENTS.md` rule/gate/invariant, a
+   README-shaped human doc, a `docs/` page's reasoning) and therefore needs updating alongside
+   the code, since `docs verify` never reads a cell's prose. Read it before step 6.
    More instructions are added here incrementally as stack-development needs come up - this
    list grows without needing this skill file to change shape.
 3. **Settle the design before building - and break there for the model switch.** These are two
@@ -135,7 +139,11 @@ stack development happens in the origin repo instead (see AGENTS.md's routing li
    Prose-only changes (`README.md`, `INSTALL.md`, `EVALS.md`) and the workflows under `.gitea/`
    do not need a bump - CI's version gate is scoped to what changes behaviour.
 
-5. **Verify, then publish.** `tools/wikitool docs verify`, `tools/wikitool instructions verify`,
+5. **Pull through every document that makes a claim about the surface you touched - `docs verify`
+   checks a cell's presence, never its prose.** [doc-pull-through.md](../doc-pull-through.md) has
+   the table of which document that is, per surface.
+
+6. **Verify, then publish.** `tools/wikitool docs verify`, `tools/wikitool instructions verify`,
    and the relevant `pytest` run in `tools/` - the same checks any stack change must pass, run
    explicitly rather than assumed. CI (`.gitea/workflows/ci.yml`) runs these plus a full
    `setup-instance.md` replay against a fresh `dist export`; a push to `main` that moves `VERSION`