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

docs/how-to/query-the-wiki.md

@@ -0,0 +1,50 @@
+# Query the wiki
+
+Ask the wiki a question and get an answer built from its compiled pages, with the pages and sources
+it came from. The agent answers using the `wiki-query` skill
+([skill catalogue](../reference/skills.md)), which only reads unless you ask it to keep an answer.
+
+## What you say
+
+Ask the way you would ask a colleague:
+
+```text
+What projects use MQTT?
+Show me the architecture of HA Integration
+Compare gdeploy and plugnburn-edl
+What decisions were made about E3DC integration?
+```
+
+## What you get back
+
+An answer that names the wiki pages it came from and the sources behind them. Where the wiki has no
+source for a claim, the agent says so instead of filling the gap. An answer it cannot back is never
+written into the wiki either.
+
+If an answer is worth keeping - a comparison you will want again, a synthesis across several pages -
+the agent proposes filing it back as a page. It names the pages it would create before it creates
+any, and nothing is written unless you agree.
+
+## Searching yourself
+
+The agent searches with the same command you can run:
+
+```bash
+tools/wikitool search "<text>"
+tools/wikitool search --field entity_type=system
+tools/wikitool search --field '!sources'          # pages without a sources: list
+```
+
+`search` covers all of `kb/`, by text, by frontmatter or both. Each hit carries the page's path and
+full title, so you can open it directly. It only reads, and it does not count against the
+session's call budget, because looking before acting is the habit worth encouraging. The predicate forms are in the
+[command reference](../reference/commands/finding-and-checking.md).
+
+For browsing rather than searching, `kb/index.md` is the catalog map, and each collection carries
+its own `INDEX.md`. All of these are generated. Read them, but never edit them. To browse the pages as
+a graph, see [Browse the wiki in Obsidian](browse-with-obsidian.md).
+
+## Asking from another machine
+
+A consumer that is not a terminal on this machine can ask the same questions through the MCP read
+server and get the same answers: [Set up the MCP read server](set-up-the-mcp-server.md).