docs: Nachzug zu #119 - Verpflichtungsschicht in Installation, Setup und docs/ (#119)

Files changed:
- AGENTS.md
- CHANGES.md
- INSTALL.md
- README.md
- VERSION
- docs/knowledge-and-commitment.md
- instructions/dev/doc-pull-through.md
- instructions/setup-instance.md
- instructions/upgrade-instance.md
- tools/README.md

README.md

@@ -223,6 +223,29 @@ The LLM will:
 See the [Maintenance](#maintenance) section below for the full schedule and
 command reference.
 
+### Reviewing Commitments (Weekly Review)
+
+Say: `Run the weekly review`
+
+Knowledge and commitments keep different clocks, so they live in different
+places. A page under `kb/gtd/` is one committed initiative's durable memory -
+its goal, who is involved, where it stands, why it is worth doing - and it never
+summarizes the task list. The open items live in a task tracker that owns them,
+configured per checkout in `.wikitool-tasks.json` (see
+[INSTALL.md](INSTALL.md) § Konfiguration; no tracker configured is a valid
+state, and the pages work without one).
+
+Nothing syncs between the two. `tools/wikitool review` joins them at read time
+over the project name and prints what needs a decision: initiatives with no next
+action, waiting-fors past their follow-up date, tracker projects with no page,
+active pages with no open loop, someday items gone stale. It stores nothing -
+not even a report file. The `weekly-review` skill then walks the findings with
+you and turns each one into a decision; `tools/wikitool new project` is what
+gives a new initiative its page and its tracker project under one name.
+
+Why the split runs this way, rather than syncing the two:
+[docs/knowledge-and-commitment.md](docs/knowledge-and-commitment.md).
+
 ## Entity Types
 
 Entities are subtyped as codebase, system, tool, technology, or person, and each subtype has