fix: demo corpus follows the decided project pages - three states, seed with their items, fixtures re-recorded (#156)

Files changed:
- CHANGES.md
- VERSION
- instructions/dev/tracker-testing.md
- kb/gtd/INDEX.md
- kb/gtd/technik/Aufgabenverwaltung mit Tracker-Anbindung.md
- kb/gtd/technik/Chemenu 8.0.0 - Installation und Windows.md
- kb/gtd/technik/Chemenu 8.0.0 freigeben.md
- kb/gtd/technik/Reproduktionslauf des Korpus.md
- kb/gtd/technik/Windows nativ unterstützen.md
- kb/index.md
- kb/log.md
- tools/chemenu/tests/fixtures/sp/MANIFEST.json
- tools/chemenu/tests/fixtures/sp/api/projects.json
- tools/chemenu/tests/fixtures/sp/api/tags.json
- tools/chemenu/tests/fixtures/sp/api/tasks.json
- tools/chemenu/tests/fixtures/sp/seed-backup.json
- tools/chemenu/tests/test_sp_recorded.py

CHANGES.md

@@ -59,7 +59,7 @@ concern - readable here, never shipped as something to parse.
 
 ---
 
-## 8.0.0-beta.3 - 2026-09-30 - Live tracker suite: WIKITOOL_TASKS_CONFIG override, real-tracker tests for Super Productivity and CalDAV, nightly workflow and test image
+## 8.0.0-beta.4 - 2026-09-30 - Demo corpus follows the decided project pages: three states, seed with their items (#156)
 
 **Author:** Torben Nehmer
 
@@ -108,8 +108,28 @@ concern - readable here, never shipped as something to parse.
 - cli.py: removed a stale duplicate help-patch line outside the typer._click fallback's try (Gitea #148)
 - new: concept/source record notes name their layout-computed subdirectory; source usage names its required fields (Gitea #150)
 - new_page/type_resolver comments no longer claim only entities declare a layout:
+- Demo corpus follows the decided project pages: three states, seed with their items (#156)
 <!-- /wikitool:bumps -->
 
+### Demo corpus follows the decided project pages: three states, seed with their items (Gitea #156)
+
+The first build of the live tracker suite shipped two demo project pages whose names came from a
+draft seed rather than from the decision the operator had made. This replaces them with the
+decided three, one per `state:` the weekly review treats differently:
+`Chemenu 8.0.0 - Installation und Windows` (active), `Aufgabenverwaltung mit Tracker-Anbindung`
+(completed) and `Reproduktionslauf des Korpus` (dormant).
+
+- **Seed backup.** Rebuilt by starting Super Productivity on the three projects, filing the
+  items through wikitool's own writer and keeping the backup the app then wrote itself: eight
+  open items in the active project, one of them `waiting` with an overdue follow-up, and one
+  someday item. `MANIFEST.json` names the one edit made after the app wrote it - the REST API
+  cannot file a backlog item, so that item was moved there in the backup.
+- **Recorded answers** re-recorded against 19.1.0 from the new seed. `test_sp_recorded.py` now
+  checks the demo projects too - counts, the waiting item and its date, the someday item - on
+  both read paths.
+- `review` against the seed reports `waiting_overdue` for the waiting item and stays quiet on the
+  completed and the dormant project, which is the join the demo exists to show.
+
 ### Live tracker suite: WIKITOOL_TASKS_CONFIG override, real-tracker tests for Super Productivity and CalDAV, nightly workflow and test image (Gitea #156)
 
 The task-tracker adapters were only ever tested against fakes, which is how #162 stayed hidden.
@@ -141,8 +161,10 @@ workflow against a real tracker, and the machinery to run it on a clock.
   agent dispatches the nightly run, what a red night means and how to refresh the fixtures;
   `testing-conventions.md` names the live suite as the one deliberate exception to the hermetic
   default. `docs verify` gained an ignore canary for `.wikitool-tasks.d/`.
-- **Demo corpus.** `kb/gtd/technik/` gains two project pages taken from the Windows and release
-  work, matching projects in the seed backup, so `review` has something to join.
+- **Demo corpus.** `kb/gtd/technik/` gains three project pages taken from this repository's own
+  work, one per `state:` the weekly review treats differently (active, completed, dormant); the
+  seed backup carries matching projects with their items, so `review` has something to join. The
+  first build shipped two differently named pages; the entry below corrects them.
 
 The Docker package `chemenu-sp-live` has to be linked to this repository once, by hand, after the
 first image build.