feat: docs reference generates a skill catalogue and a page-type reference under docs/reference/ from the shipped defaults, checked and written in the origin repo only (#189)

Files changed:
- CHANGES.md
- README.md
- VERSION
- docs/reference/README.md
- docs/reference/commands/README.md
- docs/reference/commands/types-instructions-and-docs.md
- docs/reference/page-types.md
- docs/reference/skills.md
- instructions/dev/doc-pull-through.md
- tools/CONTRACT.md
- tools/README.md
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/reference_doc.py
- tools/chemenu/tests/test_reference_doc.py

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2

README.md

@@ -314,11 +314,13 @@ way `task new` opened it, or the way the weekly review proposes it for a
 Why the split runs this way, rather than syncing the two:
 [docs/explanation/knowledge-and-commitment.md](docs/explanation/knowledge-and-commitment.md).
 
-## Entity Types
+## Page Types
 
-Entities are subtyped as codebase, system, tool, technology, or person, and each subtype has
-its own directory under `kb/entities/`. The authoritative list - and where each one is
-written - is declared by the type-spec, so ask the tool rather than a table here:
+Every page type the stack ships - entity, concept, source, comparison, project - with its
+subtypes, the directory each is written to and its required fields, is listed in
+[docs/reference/page-types.md](docs/reference/page-types.md), generated from the type-specs. An
+instance adopts those type-specs and may change them, so for the types *this* instance has, ask
+the tool:
 
 ```bash
 tools/wikitool types list
@@ -340,16 +342,9 @@ tools/wikitool types describe entity
 
 `AGENTS.md` is the cross-cutting schema/policy; the step-by-step procedures
 themselves live as independently-discoverable skills under `.agents/skills/`
-(mirrored to `.claude/skills/` for Claude Code via `tools/wikitool instructions sync`):
-
-| Skill | Purpose |
-|-------|---------|
-| `wiki-ingest` | Process a new source into the wiki: read it, discuss its content and any commitment with the user, promote it from `incoming/` into `raw/`, then source summary, entity/concept pages, cross-references, index/log, publish |
-| `wiki-query` | Answer a question from the compiled wiki; read-only, can optionally file a valuable answer back as a new page |
-| `wiki-lint` | Health-check the wiki: structural scan, raw coverage, semantic review |
-| `wiki-manage` | Create a new entity/concept/source/comparison page, or update an existing page with new information |
-| `wiki-status` | Read-only snapshot: page counts, orphans, uncovered raw files, most-connected pages |
-| `gtd-weekly-review` | Turns `wikitool review`'s findings into decisions and page updates - the GTD weekly review |
+(mirrored to `.claude/skills/` for Claude Code via `tools/wikitool instructions sync`).
+Which skills ship, what each does and which requests start it:
+[docs/reference/skills.md](docs/reference/skills.md), generated from the skills themselves.
 
 Each skill's underlying mechanical work (frontmatter, cross-references, index/log,
 decay math, publishing) is delegated to `tools/wikitool` - never hand-edited.
@@ -580,11 +575,8 @@ The LLM will create and maintain:
 - `kb/index.md` - Always up-to-date catalog
 - `kb/log.md` - Complete audit trail
 - `kb/provenance.md` - Raw-file reverse index
-- Source pages in `kb/sources/`
-- Entity pages in `kb/entities/`
-- Concept pages in `kb/concepts/`
-- Comparison pages in `kb/comparisons/`
-- Project (Vorhaben) pages in `kb/gtd/`
+- Pages of every page type, each in the directory
+  [docs/reference/page-types.md](docs/reference/page-types.md) names for it
 - Lint reports, session traces and eval scores in `reports/` (gitignored)
 
 ## Changelog