docs: source-synced head advance
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: sonnet
Assistant-Process: 101414@bnt-lap001
Assistant-Session: 60b5a221-d435-42b9-b778-983c90c7eed6
This commit is contained in:
tegwick 2026-09-30 18:08:25 +02:00
parent cfb038d76b
commit 9b429f91e8

View file

@ -121,6 +121,11 @@ trust an old-slug redirect as identity. Verify the Forge numeric ID and head,
register the new path against the existing State Hub UUID, commit canonical
source/frontmatter updates, and run `statehub fix-consistency` in the new clone.
The Forge head may advance past the preflight baseline through the source-synchronization
revision pushed from the fresh clone. `source-synced` therefore requires the clone's
`head_commit` to equal the current Forge head, records the baseline and `head_advanced`,
and later phases anchor on that recorded head. Drift beyond it still fails closed.
The private source evidence file must include the assertions enforced by State
Hub. Extra non-secret references are allowed: