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

instructions/setup-instance.md

@@ -271,7 +271,7 @@ one it needs before that.
 
 8. <!-- setup-question: telemetry --> **Decision point - telemetry.** Every instance installed from
    a release carries a `.wikitool-release.json` and starts with telemetry **off**; nobody asked for
-   it, and nobody reads `EVALS.md` before the first file is written anyway. This step only asks
+   it, and nobody reads up on telemetry before the first file is written anyway. This step only asks
    whether the operator wants to reverse that.
 
    Ask the user once: telemetry on? If yes, create `.wikitool-telemetry.json` in the repo root
@@ -289,7 +289,7 @@ one it needs before that.
    `tools/wikitool doctor` reports the result in step 12 (`telemetry`): on/off, why
    (installation form, this file, or `WIKI_TRACE`), and the current volume against both caps -
    never a `FAIL`, since both directions are a valid state. More on this:
-   [EVALS.md](../EVALS.md) § "Whether it runs at all".
+   [telemetry-and-evaluation.md](../docs/explanation/telemetry-and-evaluation.md#whether-it-runs-at-all).
 
 9. <!-- setup-question: task-tracker --> **Decision point - task tracker.** The instance ships the
    `project` type and the collection its type-spec's `base_dir:` names (`kb/gtd/` here), so
@@ -304,7 +304,7 @@ one it needs before that.
    `.wikitool-telemetry.json` and `.wikitool-remotes.json`), with the provider's own section and
    the three thresholds the review reads as configuration rather than schema. The shape, the
    shipped providers, and what Super Productivity in particular needs are in
-   [INSTALL.md](../INSTALL.md) § Konfiguration; do not restate them here. If no, do nothing - no
+   [configuration.md](../docs/reference/configuration.md#task-tracker); do not restate them here. If no, do nothing - no
    file is created, and adding one later needs nothing from this procedure.
 
    `doctor` reports the result in step 12 (`tasks`): absent is `OK`, a malformed file is the one