docs(cache): prove isolated projection rebuild

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a023c0-a0a3-7c03-b395-5a0d2757214d
This commit is contained in:
tegwick 2026-08-22 12:31:35 +02:00
parent 6e9c93e7ca
commit 833fa6e746
3 changed files with 135 additions and 1 deletions

View file

@ -480,6 +480,25 @@ the pilot record without identifier writeback. T07 remains in progress because
the full isolated projection rebuild and hub-native centralization proof still
cover more than this one workplan.
**Full isolated rebuild (2026-08-22):** the guarded
`--bootstrap-empty-projection` path rebuilt a fresh disposable State Hub from
the repository's existing authoritative identifiers: 9 workplans, 62 tasks,
2 intakes, and 0 decisions, with no missing records. A second read-only pass
reported zero issues and all 9 source bindings synchronized. The path refuses a
non-empty target projection, multi-repository scans, unsynchronized Forgejo
checkouts, and any authoritative file mutation. State Hub commits `03c7924`
and `059de93`; Repo Manager commits `707fb85` and `6e9c93e`.
The remaining gate is now measured rather than inferred. The workstation hub
has 35 Repo Manager-linked progress events and 13 messages to/from
`repo-manager`; production has 2 and 0 respectively. The disposable rebuild has
zero of each by design. These hub-native records cannot be reconstructed from
files, and mutable message state cannot use unordered append replay. T07 stays
`progress` until the declared central owner migrates or dispositions them and a
repeat comparison passes. Evidence and the non-destructive procedure are in
`docs/evidence/RMGR-WP-0005-isolated-rebuild-2026-08-22.md` and
`docs/cache-rebuild_v1.md`.
## Separate file-derived from hub-native data
```task