coulomb/state-hub
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

repository-rename verify: accept descendant heads and retired dispatch after source-synced
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 12s
Details
Build and Publish Multi-Context Image / build-and-push (push) Successful in 41s
Details

Browse source 
Finishing work during the operation retires it from active dispatch, and the
source repository legitimately advances after source-synced. verify now treats
retired dispatch ids as present and accepts a Forge head that contains the
recorded source-synced head (Forgejo compare); unrelated drift still fails.

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 19:37:35 +02:00
parent 6924d2410f
commit b451bd10e5
4 changed files with 114 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/repository-rename-operations.md
View file

@ -126,6 +126,12 @@ revision pushed from the fresh clone. `source-synced` therefore requires the clo
`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.
After `source-synced` the source repository keeps moving. `verify` accepts a later Forge head
only when it contains the recorded `source-synced` head (Forgejo `compare`); unrelated drift
still fails. Tasks or workplans finished during the operation leave active dispatch and are
reported as `retired_dispatch` rather than missing; a dispatch id whose record no longer
exists is still a failure.
The private source evidence file must include the assertions enforced by State
Hub. Extra non-secret references are allowed: