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

instructions/dev/tracker-testing.md

@@ -167,8 +167,10 @@ job `continue-on-error` to get a green night: a red night with a cause is the pr
 ## Refreshing the fixtures
 
 `tools/chemenu/tests/fixtures/sp/api/*.json` are the raw answers of a real Super Productivity;
-`seed-backup.json` is a backup the app wrote itself, with the three projects the live suite and
-the demo pages use. `MANIFEST.json` says which version and when. Refresh them when a red night
+`seed-backup.json` is a backup the app wrote itself, holding the marker project the live suite
+writes into and the demo projects - with their items - that the `kb/gtd/` pages of the same
+names join against. `MANIFEST.json` says which version and when, and names the one edit made to
+the backup after the app wrote it. Refresh them when a red night
 shows a new answer shape, and when the manifest's version is more than a few releases behind.
 
 1. Get a Super Productivity to record from: the current `chemenu-sp-live` image with the
@@ -183,7 +185,9 @@ shows a new answer shape, and when the manifest's version is more than a few rel
 
 3. Update `MANIFEST.json` (`sp_version`, `recorded`) by hand - it is a fixture, not a generated
    page - and run `test_sp_recorded.py`. If the seed backup is stale because the app's backup
-   format moved, rebuild it from a backup the new version wrote and keep the three projects.
+   format moved, rebuild it the same way: start the new version on the old seed, let it write
+   its own backup, and keep the projects and items `test_sp_recorded.py` expects. A
+   `kb/gtd/` page's name and the demo project's name must stay equal - the join is by name.
 4. Do not edit the recorded answers to make a test pass. A test that fails against a fresh
    recording is the adapter's problem.