stack: TOC-Scope auf types/ und docs/, Sprachregeln nach AGENTS.md zentralisiert, alle Templates auf Control-Plane-Sprache, --breaking akkumuliert (schliesst #99)

Files changed:
- AGENTS.md
- CHANGES.md
- ENVIRONMENT.md.template
- SOUL.md
- SOUL.md.template
- USER.md.template
- VERSION
- docs/ownership-and-templates.md
- docs/version-model.md
- instructions/CONTRACT.md
- instructions/dev/doc-pull-through.md
- instructions/dev/stack-close/SKILL.md
- instructions/dev/stack-dev/SKILL.md
- instructions/dev/version-parts.md
- instructions/setup-instance.md
- kb/CONVENTIONS.md
- kb/CONVENTIONS.md.template
- kb/concepts/COLLECTION.md
- kb/sources/COLLECTION.md
- tools/CONTRACT.md
- tools/chemenu/commands/types_cmd.py
- tools/chemenu/commands/version_cmd.py
- tools/chemenu/tests/test_toc.py
- tools/chemenu/tests/test_version_cmd.py
- tools/chemenu/toc.py
- tools/chemenu/version.py
- types/comparison.md
- types/concept.md
- types/entity.md
- types/lint-report.md
- types/source.md

instructions/dev/stack-dev/SKILL.md

@@ -76,12 +76,13 @@ stack development happens in the origin repo instead (see AGENTS.md's routing li
 
    So when the design is settled - the issue body says what will be built, the open questions are
    answered - stop and say so, in one sentence that names what the mechanical stretch does **not**
-   cover:
+   cover. The message below is a model of what to say, not a script to quote: say it in the
+   instance's KB language, per `AGENTS.md` § File naming.
 
-   > Der Plan steht, ab hier ist die Arbeit größtenteils mechanisch und durch Tests/CI abgedeckt -
-   > mit Ausnahme der Changelog-Prosa (Schritt 4), einer berührten `docs/`-Seite, neuer
-   > Menschendoku oder des Prosa-Anteils einer Instruction. Wenn du auf Opus bist, ist jetzt der
-   > Moment für `/model sonnet` bei Effort `high`.
+   > The plan is settled. From here the work is mostly mechanical and covered by tests/CI -
+   > except the changelog prose (step 4), any `docs/` page you touch, new human-facing
+   > documentation, and the prose half of an instruction. If you are on Opus, now is the moment
+   > for `/model sonnet` at effort `high`.
 
    **You cannot make this switch yourself** - the session's model is the user's `/model`, not a
    setting an agent applies. Offer it once and keep working either way; a session that argues
@@ -146,7 +147,13 @@ stack development happens in the origin repo instead (see AGENTS.md's routing li
 
 5. **Pull through every document that makes a claim about the surface you touched - `docs verify`
    checks a cell's presence, never its prose.** `instructions/dev/doc-pull-through.md` has
-   the table of which document that is, per surface.
+   the table of which document that is, per surface, and its step 3 for the one part of the
+   pull-through that is *not* prose: a reference file whose headings moved needs
+   `tools/wikitool docs toc --apply`, never a hand-written list.
+
+   Prose you write here is English, whatever language the session is being held in -
+   `AGENTS.md` § File naming has both language rules and the line between prose and quoted
+   vocabulary.
 
 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