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

instructions/evolve-subtypes.md

@@ -17,7 +17,7 @@ procedure for changing that list once it is running, not for choosing it the fir
 
 The tooling for this loop already exists end to end; this file only names the sequence and the
 two rules that keep it from repeating what created `kb/sources/`'s old `notes` catch-all in the
-first place (Gitea #66): a schema `default:` that the compiler applied whenever nobody
+first place: a schema `default:` that the compiler applied whenever nobody
 disagreed, silently turning the least specific value into the collection point for everything
 unclear.
 
@@ -60,10 +60,10 @@ choice of an instance's starting vocabulary - that is
    2. **Apply the ≥3-page admission threshold.** A value is admitted *after* it has proven
       itself against real material, never in expectation of some. `spec` and `image` are the
       cautionary case: both were added to `source_type` ahead of any matching page, both sat at
-      zero for a year, and both were removed in Gitea #66. A smaller count is only ever an
-      operator's explicit, named exception (`tracker` at two pages in #66, kept because the
-      corpus was expected to grow into it from ongoing issue ingests) - never a reason to lower
-      the threshold itself.
+      zero for a year, and both were eventually removed again unused. A smaller count is only
+      ever an operator's explicit, named exception (`tracker` survived that same cleanup at two
+      pages, kept because the corpus was expected to grow into it from ongoing issue ingests) -
+      never a reason to lower the threshold itself.
    3. Add the enum value in the type-spec's schema (`types/<t>.schema.yaml`) and its `layout:`
       entry (`types/<t>.md`) in the same edit - a value with no `layout:` line has nowhere to be
       moved to.