fix: regenerate REGISTRY.a2ml — stale RSR source_hash after #515#519
Merged
Conversation
`Registry Verify` has been failing on `main` since #515 (feat(rsr): scaffold lifecycle canon, archetype presets, oracle-aligned profile checker) merged at ~12:34 today. That PR changed tracked files under `rhodium-standard- repositories/` without regenerating the derived registry, so the RSR entry's `source_hash` — a sha256 over `git ls-files -s <home>` — no longer matches the tree. Every open PR inherits the failure, because pull_request checks run against the merge ref. This is the sole cause of the current red on #518. One line, produced by `bash scripts/build-registry.sh` with no manual editing. Verified: `scripts/build-registry.sh --check` exits 0 on this commit ("OK: registry + topology are in sync with the file tree") and non-zero on `origin/main`. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Registry Verifyhas been failing onmainsince #515 merged at ~12:34 today.#515 changed tracked files under
rhodium-standard-repositories/without regenerating the derived registry, so the RSR entry'ssource_hash— a sha256 overgit ls-files -s <home>— no longer matches the tree:Every open PR inherits this, because
pull_requestchecks run against the merge ref. It is the sole cause of the current red on #518.The change
One line, produced by
bash scripts/build-registry.shwith no manual editing:Verified
scripts/build-registry.sh --checkorigin/mainDRIFT: .machine_readable/REGISTRY.a2ml is staleOK: registry + topology are in sync with the file tree.(exit 0)Run history confirms the regression point —
maingreen at 04:48, red at 12:37, withfeat/scaffold-lifecycle-canonred at 12:34.Worth considering as follow-up:
just hooks-install(the pre-commit guard the failure message already points at) would have caught this before push.🤖 Generated with Claude Code