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

types/source.schema.yaml

@@ -10,7 +10,7 @@ properties:
     enum: [transcript, analysis, article, document, notes, tracker, unclassified]
     description: >-
       The category of source material. No default - the machine must not pick
-      the vaguest value on the author's behalf (Gitea #66). Use `unclassified`
+      the vaguest value on the author's behalf. Use `unclassified`
       when the category is genuinely unclear; it is a visible, advisory-lint
       catalog slot, not a silent fallback.
   author:
@@ -29,7 +29,7 @@ properties:
     description: >-
       How faithful the capture is to what was actually said or shown. No
       default - a capture field, fixed at `raw accept`/`new source` time and
-      never guessed (Gitea #67). `unknown` is backfill-only: `raw accept` and
+      never guessed. `unknown` is backfill-only: `raw accept` and
       `new source` refuse it, only `wikitool touch` (on a page predating this
       rule) may write it. Deliberately absent from `required:` so an existing
       instance's source pages keep validating without it.
@@ -39,7 +39,7 @@ properties:
     description: >-
       What the material is entitled to claim about its subject - independent
       of `fidelity`, which asks how faithfully it was captured. Same capture,
-      no-default, backfill-only-`unknown` rules as `fidelity` (Gitea #67).
+      no-default, backfill-only-`unknown` rules as `fidelity`.
       Deliberately absent from `required:` for the same reason.
   source_url:
     type: [string, "null"]

types/type-spec.md

@@ -112,7 +112,7 @@ in once it grows past the shard threshold, and whether a `layout:` is already de
 split it recommends.
 
 A lopsided field is a reason to fix the field, not a reason to leave `layout` off forever -
-`source` was exactly this case (Gitea #66): 25 of 29 pages carried one value because the schema
+`source` was exactly this case: 25 of 29 pages carried one value because the schema
 handed out that value as a *default* whenever nobody chose one, not because the material was
 genuinely that uniform. Once the default was removed and the pages reclassified by what they
 actually were, the field split into six areas with none of them small. Declare `layout` for