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

AGENTS.md

@@ -88,7 +88,6 @@ What a file is called says who it is for and how it is loaded. This is a rule, n
 | Name | For | Loaded |
 |------|-----|--------|
 | `README.md` | Humans - technical documentation and how to develop the thing in that directory | Never by an agent as instruction |
-| `EVALS.md` | Humans - how telemetry and evaluation work; routes to the contracts that bind | Never by an agent as instruction |
 | `AGENTS.md` | Agents | Always, every session |
 | `CLAUDE.md` | Agents on Claude Code | Automatically by that harness, which does not load `AGENTS.md` on its own - so it imports this file, carrying no rule of its own. It also links the one remaining Claude-Code-only decision (model/effort selection), per [instructions/CONTRACT.md](instructions/CONTRACT.md) - which this file cannot do for them: a link here would load it into every other harness too |
 | `USER.md` | Agents | Always, every session |
@@ -135,8 +134,8 @@ whether it ever leaves this checkout.
    lives in `kb/CONVENTIONS.md`'s `language:` and nowhere else; an instruction that models a
    sentence for the user writes it in English like the rest of the control plane, and the agent
    says it in that language.
-3. **The stack's human documentation is written in English** - `README.md`, `INSTALL*.md`,
-   `EVALS.md` and everything under `docs/` - whatever an instance's `language:` says. It is the
+3. **The stack's human documentation is written in English** - `README.md`, `INSTALL.md` and
+   everything under `docs/` - whatever an instance's `language:` says. It is the
    same text in every instance, and the parts of it that are generated come from English
    sources, so there is no instance whose language it could follow. `CHANGES.md` is a log, not
    documentation, and is not covered.
@@ -366,7 +365,7 @@ Changes to this schema, the contracts, the instruction layer, `tools/wikitool`,
 READMEs go in [CHANGES.md](CHANGES.md) - never in an inline version-history table here. Wiki
 *content* operations are logged separately via `tools/wikitool log append` into `kb/log.md`.
 
-**A stack change is not finished until the human docs describe it.** `README.md`, `EVALS.md`,
+**A stack change is not finished until the human docs describe it.** `README.md`,
 `tools/README.md`, the pages under `docs/tutorials/`, `docs/how-to/`, `docs/reference/` and
 `docs/dev/`, `tools/CONTRACT.md` and the touched `<stage>/CONTRACT.md` are part of the change
 that introduced a stage, a command or a workflow, not follow-up work: nobody comes back for them,