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

docs/pipeline-rationale.md

@@ -14,7 +14,7 @@ thing later claims get checked against is no longer the thing that was actually
 immutable `raw/` means a citation always resolves to the original, not to somebody's tidied
 memory of it. It also draws a trust boundary in one place instead of scattering it - everything
 past `raw/` can be treated as reviewed, because nothing upstream of it silently already was.
-`incoming/` (Gitea #58) sits entirely on the near side of that boundary: a file waiting there is
+`incoming/` sits entirely on the near side of that boundary: a file waiting there is
 not yet reviewed and not yet a citation target, so its being gitignored and readable by an
 ingest session does not weaken anything - the boundary is the promotion into `raw/` itself, not
 the moment a human happened to drop a file somewhere.