feat: docs/ carries the operator's how-to guides, a configuration reference and the architecture and telemetry explanations carved out of README.md, INSTALL.md, INSTALL-MCP.md and EVALS.md; the last two retired (#190)

Files changed:
- .gitea/workflows/ci.yml
- .gitignore
- .vibe/hooks.toml
- AGENTS.md
- CHANGES.md
- EVALS.md
- INSTALL-MCP.md
- INSTALL.md
- README.md
- VERSION
- docs/dev/development.md
- docs/explanation/README.md
- docs/explanation/architecture.md
- docs/explanation/language-boundaries.md
- docs/explanation/telemetry-and-evaluation.md
- docs/how-to/README.md
- docs/how-to/browse-with-obsidian.md
- docs/how-to/capture-repository-docs.md
- docs/how-to/export-guidelines.md
- docs/how-to/ingest-a-source.md
- docs/how-to/maintain-the-wiki.md
- docs/how-to/query-the-wiki.md
- docs/how-to/run-the-weekly-review.md
- docs/how-to/set-up-the-mcp-server.md
- docs/how-to/trace-and-score-sessions.md
- docs/how-to/troubleshoot.md
- docs/how-to/update-an-instance.md
- docs/reference/README.md
- docs/reference/commands/distribution-and-versioning.md
- docs/reference/commands/instance-health.md
- docs/reference/commands/raw-material-and-uploads.md
- docs/reference/commands/telemetry.md
- docs/reference/commands/types-instructions-and-docs.md
- docs/reference/configuration.md
- instructions/dev/dev-setup.md
- instructions/dev/doc-pull-through.md
- instructions/dev/stack-build/SKILL.md
- instructions/dev/testing-conventions.md
- instructions/dev/version-parts.md
- instructions/setup-instance.md
- instructions/upgrade-instance.md
- reports/CONTRACT.md
- tools/.coveragerc
- tools/CONTRACT.md
- tools/README.md
- tools/chemenu/commands/dist_cmd.py
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/commands/doctor.py
- tools/chemenu/commands/eval_cmd.py
- tools/chemenu/commands/git_publish.py
- tools/chemenu/commands/upload_cmd.py
- tools/chemenu/commands/version_cmd.py
- tools/chemenu/evals/__init__.py
- tools/chemenu/evals/scorecard.py
- tools/chemenu/evals/trajectory.py
- tools/chemenu/telemetry/policy.py
- tools/chemenu/tests/test_dist_cmd.py
- tools/chemenu/tests/test_git_publish.py
- tools/chemenu/tests/test_instructions_shell.py
- tools/chemenu/tests/test_pipeline_l0.py
- tools/chemenu/toc.py

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

tools/CONTRACT.md

@@ -1746,7 +1746,7 @@ List every MCP submission currently waiting in the quarantine (`mcp-upload/`).
 **SEE ALSO**
 
 - `wikitool upload show` - one submission's manifest
-- `INSTALL-MCP.md` § "Schritt 7: Optional - den `submit`-Pfad freischalten"
+- `docs/how-to/set-up-the-mcp-server.md` § "Optional: the submit path"
 
 #### `upload show`
 
@@ -2607,7 +2607,7 @@ Create, refresh or remove the generated table-of-contents region.
 
 - Creates, refreshes or removes the generated table-of-contents region on every reference file over 100 lines: `AGENTS.md`, every stage contract, `kb/CONVENTIONS.md`, every `kb/*/COLLECTION.md`, every flat `instructions/**.md` file, every `types/*.md` type-spec, and every `docs/` page - each together with the `<name>.template` it ships as, where one exists.
 - The scope is computed from those categories rather than listed, so a file added later is in scope without a code change.
-- Out of scope: every `SKILL.md`, the human docs (`README.md`, `CHANGES.md`, `EVALS.md`, `INSTALL.md`, `tools/README.md`), and every subtype template `types/<type>.<value>.md` - `new` copies it into a page, so it never carries a region whatever its length.
+- Out of scope: every `SKILL.md`, the human docs at the root and beside the code (`README.md`, `CHANGES.md`, `INSTALL.md`, `tools/README.md`), and every subtype template `types/<type>.<value>.md` - `new` copies it into a page, so it never carries a region whatever its length.
 - Dry-run by default (prints which files would change); `--apply` writes. Idempotent: a re-run after an interruption converges rather than doubling a region.
 - If `docs verify` still reports a stale region after `--apply`, the file's `##` headings changed in between; run it again.
 
@@ -2792,7 +2792,7 @@ List the sessions that have a trace under `reports/telemetry/`.
 **SEE ALSO**
 
 - `wikitool eval score` - scores one of them
-- `EVALS.md` - how telemetry and evaluation work
+- `docs/explanation/telemetry-and-evaluation.md` - how telemetry and evaluation work
 
 #### `eval score`
 
@@ -2837,7 +2837,7 @@ Score one traced session.
 **SEE ALSO**
 
 - `wikitool eval sessions` - which session ids exist
-- `EVALS.md` - the scoring levels
+- `docs/explanation/telemetry-and-evaluation.md` - the scoring levels
 
 ### Distribution and versioning
 
@@ -2884,7 +2884,7 @@ Write a contentless, distributable copy of this repo's machinery.
 **NOTES**
 
 - Writes a contentless, distributable copy of this repo's machinery into an empty or new `<target>` directory.
-- Ships `AGENTS.md`/`README.md`/`EVALS.md` with any `dist:strip-start`...`dist:strip-end` marker region removed, `instructions/` (minus `instructions/dev/`), `types/` (the `root: kb` page type-specs, their schemas and their subtype templates `types/<type>.<value>.md` re-keyed as `.template`, the stack's own verbatim), `docs/` verbatim (minus `docs/dev/`), `tools/` (no venv/caches, and not the dev-only test suite `tools/chemenu/tests/` with its `pytest.ini`/`.coveragerc`), the `.github/hooks/`+`.vibe/` session-tracing config plus `.claude/settings.json`, `kb/CONTRACT.md` (no pages, no areas) and `VERSION`.
+- Ships `AGENTS.md`/`README.md`/`INSTALL.md` with any `dist:strip-start`...`dist:strip-end` marker region removed, `instructions/` (minus `instructions/dev/`), `types/` (the `root: kb` page type-specs, their schemas and their subtype templates `types/<type>.<value>.md` re-keyed as `.template`, the stack's own verbatim), `docs/` verbatim (minus `docs/dev/`), `tools/` (no venv/caches, and not the dev-only test suite `tools/chemenu/tests/` with its `pytest.ini`/`.coveragerc`), the `.github/hooks/`+`.vibe/` session-tracing config plus `.claude/settings.json`, `kb/CONTRACT.md` (no pages, no areas) and `VERSION`.
 - Ships `raw/` and `incoming/` as flat roots, each with a `.gitkeep` and no subdirectories. `incoming/.gitkeep` is trackable and survives becoming a git repository, so a plain clone gets the directory without any bootstrap step.
 - Ships templates, never the filled files: `USER.md.template`/`SOUL.md.template`, `kb/CONVENTIONS.md.template`, and each collection's contract re-keyed as `kb/<name>/COLLECTION.md.template`. The filled `USER.md`/`SOUL.md`/`kb/CONVENTIONS.md`/`kb/<name>/COLLECTION.md`/`types/<page-type>.md`/`types/<page-type>.<value>.md` bind their instance; `find_leaks` refuses a plan carrying one.
 - Writes a generated `.wikitool-release.json` stamp: version, export date, origin, and a sha256 per exported file - the base a later upgrade compares against.
@@ -3040,7 +3040,7 @@ Apply a stack update `dist export` produced - the write half of `version check`.
 - `wikitool version check` - finds out whether an update exists
 - `wikitool version notes` - the notes of the release `--expect` should name
 - `instructions/upgrade-instance.md` - the order after the swap
-- `INSTALL.md` § "Version und Updates" - which release, whether to take it, where the tarball comes from
+- `docs/how-to/update-an-instance.md` - which release, whether to take it, where the tarball comes from
 - `wikitool migrate status` - the migrations the report names
 
 #### `version show`
@@ -3127,14 +3127,14 @@ Ask the origin's release feed whether a newer stack exists.
 - The only command whose whole job is the network call - `version notes` reaches the same feed too, but only as a fallback on a distributed instance, and `dist upgrade --latest` asks it which release to download.
 - Never reached implicitly from another command (`dist upgrade` asks only when passed `--latest`), needs no key, and times out after `--timeout` seconds (default 10).
 - The feed is `--url`, else `$WIKITOOL_UPDATE_URL`, else the release stamp's, else the built-in origin. `$WIKITOOL_UPDATE_TOKEN` is only needed if that feed is not readable anonymously.
-- For `update` or `migration` it prints that applying the release is a separate, manual step (`INSTALL.md` § "Eine Instanz aktualisieren").
+- For `update` or `migration` it prints that applying the release is a separate, manual step (`docs/how-to/update-an-instance.md`).
 - Read-only; exempt from the Iteration Budget Gate.
 
 **SEE ALSO**
 
 - `wikitool dist upgrade` - applies the update this reports
 - `wikitool version notes` - prints the release notes
-- `INSTALL.md` § "Version und Updates" - what the operator decides before an update
+- `docs/how-to/update-an-instance.md` - what the operator decides before an update
 
 #### `version notes`
 
@@ -3644,8 +3644,8 @@ Check that this instance is correctly configured.
 
 - `instructions/setup-instance.md` - the setup steps most findings point back to
 - `instructions/preflight.md` - what `tool-paths` and `install-dir` point back to
-- `INSTALL.md` § "Konfiguration" - the per-checkout configuration files
-- `EVALS.md` - telemetry state and caps
+- `docs/reference/configuration.md` - the per-checkout configuration files
+- `docs/explanation/telemetry-and-evaluation.md` - telemetry state and caps
 - `instructions/session-setup.md` - setting `WIKITOOL_SESSION_ID`
 <!-- /wikitool:commands -->
 ## Design notes
@@ -3728,8 +3728,8 @@ cd tools
 .venv/bin/python -m pytest -q             # add --cov for a coverage report
 ```
 
-Neither is in `requirements.txt`, and `pytest-cov` is CI-only by intent - see
-[EVALS.md](../EVALS.md).
+Neither is in `requirements.txt`, and `pytest-cov` is CI-only by intent: `requirements.txt` is
+what an instance needs at runtime, and an instance does not measure this suite.
 
 ## Maintenance schedule