From 9b429f91e80367380253772960ac16ec296bea88 Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 30 Sep 2026 18:08:25 +0200 Subject: [PATCH] docs: source-synced head advance Co-Authored-By: Claude Sonnet 5.5 Assistant: claude-code Assistant-Model: sonnet Assistant-Process: 101414@bnt-lap001 Assistant-Session: 60b5a221-d435-42b9-b778-983c90c7eed6 --- docs/repository-rename-operations.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/repository-rename-operations.md b/docs/repository-rename-operations.md index 117d3ba..a997120 100644 --- a/docs/repository-rename-operations.md +++ b/docs/repository-rename-operations.md @@ -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: