Repository navigation
chore(registry): fix the K9 home hash the format commit invalidated (#1149 follow-up) - #1151
Merged
Merged
Conversation
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 15 minutes. View limit detailsLimit details: You’ve used the included review currently available. Review configuration: ⚙️ Run configuration
📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…ormatted `source_hash` covers every tracked file in a home, so `nickel format` on `1-formats/k9/spec/contract/k9_contract.ncl` moved the `1-formats/k9/` hash again — one commit after the earlier regeneration. Registry Verify caught it on main (`aa1c4dd`), which is the check doing its job. `bash scripts/build-registry.sh --check` passes again; the only changed line is the `1-formats/k9/` source_hash. Scorecards and the compliance dashboard were already in sync. Follow-up to #1149 (M1 · #A, M7 · #F). Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>
hyperpolymath
force-pushed
the
arena/01a10a3b-standards
branch
from
October 5, 2026 04:54
284fe11 to
35948b0
Compare
Contributor
K9 contract conformancerun https://github.com/hyperpolymath/standards/actions/runs/37265527198 K9 normative contract typecheckK9 contract self-testK9 conformance fixturesK9 corpus conformance (L2) |
Contributor
|
Autopilot could not be updated. Open Coding to check access and billing. |
hyperpolymath
force-pushed
the
arena/01a10a3b-standards
branch
2 times, most recently
from
October 5, 2026 04:56
a914af6 to
35948b0
Compare
|
Contributor
K9 contract conformancerun https://github.com/hyperpolymath/standards/actions/runs/37265625692 K9 normative contract typecheckK9 contract self-testK9 conformance fixturesK9 corpus conformance (L2) |
Owner
Author
|
Housekeeping note on this branch's history: a parallel session force-pushed it twice at ~04:57 UTC ( |
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.
Follow-up to #1149 (merged as
aa1c4dd), which landed one commit too early:nickel formaton1-formats/k9/spec/contract/k9_contract.nclmoved the1-formats/k9/source_hashafter the registry had been regenerated, soRegistry Verifyfailed on main.source_hashissha256(git ls-files -s <home>), so the formatted contract — not just the new fixture — is part of the hash. This regenerates.machine_readable/REGISTRY.a2ml; the only changed line is that one hash.Refs: #1058 (M1 · #A, M7 · #F).