docs: ausgelieferte Doku zitiert keine Issue-Nummern mehr, docs verify prueft es (schliesst #77)

Files changed:
- .gitignore
- CHANGES.md
- EVALS.md
- INSTALL.md
- README.md
- VERSION
- docs/pipeline-rationale.md
- instructions/CONTRACT.md
- instructions/bootstrap.md
- instructions/dev/issue-tracking.md
- instructions/evolve-subtypes.md
- instructions/kb-profiles.md
- instructions/mcp-read-server.md
- instructions/wiki-ingest/SKILL.md
- kb/CONTRACT.md
- kb/concepts/COLLECTION.md
- kb/sources/COLLECTION.md
- raw/CONTRACT.md
- tools/.coveragerc
- tools/CONTRACT.md
- tools/README.md
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/tests/test_docs_verify.py
- types/source.schema.yaml
- types/type-spec.md

README.md

@@ -79,7 +79,7 @@ chemenu/
 ├── raw/                # INPUT: immutable, untrusted source material
 │   ├── CONTRACT.md     # Date shard, capture fields, immutability, untrusted content
 │   ├── 2026/09/        # Where `raw accept` puts a file: the month it was accepted
-│   ├── articles/       # Pre-#67 type directories: still valid paths, never moved,
+│   ├── articles/       # The old type directories: still valid paths, never moved,
 │   ├── documents/      #   but nothing new is ever routed into them again
 │   ├── notes/
 │   └── assets/
@@ -152,11 +152,12 @@ when the split would not actually help. `kb/comparisons/` is the worked example
 that stays flat - it has no subtype field for a `layout:` to key on at all. A *lopsided* subtype
 field is a different case and is fixed rather than left flat: `kb/sources/` looked lopsided only
 because `source_type` had a schema `default:` that the compiler applied whenever nobody chose a
-value, and once that was removed and the pages reclassified it split into six real areas
-(Gitea #66). `COLLECTION.md` never
-appears outside `kb/` - the other layers carry a `CONTRACT.md` or a root type-spec instead. A stage may carry
-both a `README.md` and a `CONTRACT.md`: they have different readers. The README is for humans
-working *on* that layer, the contract is what binds an agent working *with* it.
+value, and once that was removed and the pages reclassified it split into six real areas.
+
+`COLLECTION.md` never appears outside `kb/` - the other layers carry a `CONTRACT.md` or a root
+type-spec instead. A stage may carry both a `README.md` and a `CONTRACT.md`: they have different
+readers. The README is for humans working *on* that layer, the contract is what binds an agent
+working *with* it.
 
 ## How to Use