stack: TOC-Pflicht fuer Referenzdateien ueber 100 Zeilen (docs toc); session-setup.md/gates.md nennen die tatsaechliche Budget-Ausnahmeliste (schliesst #73, #76)

Files changed:
- AGENTS.md
- CHANGES.md
- VERSION
- instructions/CONTRACT.md
- instructions/capture-session.md
- instructions/claude-code-model-selection.md
- instructions/dev/issue-tracking.md
- instructions/dev/testing-conventions.md
- instructions/dev/version-parts.md
- instructions/evolve-subtypes.md
- instructions/gates.md
- instructions/german-terminology.md
- instructions/ingest-large-tree.md
- instructions/kb-profiles.md
- instructions/link-taxonomy.md
- instructions/mcp-read-server.md
- instructions/migrate-corpus.md
- instructions/migrations/3.0.0-authoring-conventions.md
- instructions/migrations/4.0.0-link-taxonomy.md
- instructions/private-instance.md
- instructions/session-setup.md
- instructions/setup-instance.md
- kb/CONTRACT.md
- kb/CONVENTIONS.md
- kb/concepts/COLLECTION.md
- raw/CONTRACT.md
- tools/CONTRACT.md
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/commands/instructions_cmd.py
- tools/chemenu/tests/test_docs_verify.py
- tools/chemenu/tests/test_instructions_cmd.py
- tools/chemenu/tests/test_toc.py
- tools/chemenu/toc.py
- types/type-spec.md

instructions/dev/issue-tracking.md

@@ -20,6 +20,18 @@ This instruction exists only in the dev repo. A distributed instance has no
 issues at that URL, which is exactly why `dist export` excludes
 `instructions/dev/` wholesale (see [tools/CONTRACT.md](../../tools/CONTRACT.md)).
 
+<!-- wikitool:toc -->
+## Contents
+
+- [When to run](#when-to-run)
+- [Steps](#steps)
+- [Incoming stubs](#incoming-stubs)
+- [Renames and other decay in the tracker](#renames-and-other-decay-in-the-tracker)
+- [Citing an issue in the repo](#citing-an-issue-in-the-repo)
+- [What no tool checks](#what-no-tool-checks)
+- [Decision points](#decision-points)
+<!-- /wikitool:toc -->
+
 ## When to run
 
 - Something is worth doing but not now. Open an issue; do not write it down in

instructions/dev/testing-conventions.md

@@ -19,6 +19,17 @@ the first CI run that ever reached pytest, in a container that had no such confi
 (Gitea #8). Two more tests of the same kind were written afterwards, by someone who had read
 that issue first - which is the argument for a fixture rather than a rule.
 
+<!-- wikitool:toc -->
+## Contents
+
+- [What the fixture already neutralizes](#what-the-fixture-already-neutralizes)
+- [Which tree a test writes into](#which-tree-a-test-writes-into)
+- [When to run](#when-to-run)
+- [Steps](#steps)
+- [Decision points](#decision-points)
+- [Scope](#scope)
+<!-- /wikitool:toc -->
+
 ## What the fixture already neutralizes
 
 Do not re-do any of this per test; it is done for you, per test, via `monkeypatch`.

instructions/dev/version-parts.md

@@ -20,6 +20,17 @@ Two questions decide a version bump, and they are **not the same question**:
 Getting these backwards is how a genuinely breaking change ships as a MINOR. It happened once
 already (see the case study at the end), which is why this file exists.
 
+<!-- wikitool:toc -->
+## Contents
+
+- [The candidate model](#the-candidate-model)
+- [When to run](#when-to-run)
+- [Steps](#steps)
+- [Decision points](#decision-points)
+- [Scope](#scope)
+- [Case study: 2.0.0](#case-study-200)
+<!-- /wikitool:toc -->
+
 ## The candidate model
 
 Between two releases the stack carries **one running candidate**, not a fresh version per