coulomb/repo-manager
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(cache): prove isolated projection rebuild

Browse source 
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
Download patch file Download diff file Expand all files Collapse all files

29
docs/cache-rebuild_v1.md
View file

@ -5,7 +5,7 @@ title: "Repository projection cache rebuild"
version: "1"
status: active
created: "2026-08-21"
updated: "2026-08-21"
updated: "2026-08-22"
workplan_task: RMGR-WP-0005-T07
---
@ -60,3 +60,30 @@ A database replacement is not authorized by this command. Before replacement:
The old database remains a recoverable source until those gates pass. Repo
Manager does not merge database-local file-derived state back into repositories.
### Prove a file-derived rebuild in an empty projection
Use the registrar bootstrap only against a fresh or disposable State Hub whose
projection for the target repository is empty:
```bash
rmgr registrar-reconcile \
--path /path/to/repository \
--api-base http://127.0.0.1:58005 \
--confirm-primary \
--bootstrap-empty-projection
```
The command requires a clean checkout synchronized with Forgejo and a healthy
target. It refuses multi-repository or remote scans, proves that the selected
repository has zero projected workplans before mutation, scopes registrar
authority to the child consistency process, and then verifies every
authoritative workplan, task, intake, and decision UUID. It restores the
generated `.custodian-brief.md` if that is the only checkout change and fails
closed on any authoritative file mutation.
Run a second read-only consistency pass against the same target. A passing
rebuild has no issues and has the same record identifiers, lifecycle statuses,
and source bindings as the files. This operation deliberately does not copy
progress events, token events, or messages; those hub-native records must pass
their own central-owner gate before any legacy database is discarded.