Repository navigation
Re-pin rewritten RFIsher and RadioFisher commits - #9
Merged
Merged
Conversation
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
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.
RFIsher and RadioFisher now live on rewritten histories, so the old commit IDs no longer resolve. This re-pins every reference to them (same trees, same abbreviation length):
ca_os_archive_bulk_2026-09-29andch37_rank_injection_2026-09-30selection_policy_7edf11c_detector_entries.json)The evidence checksums are recomputed over the edited files (
release-manifest.json,MANIFEST.json, and the manifest hashes and byte totals inF1_INVENTORY.md). Re-pinned copies are labeled as such, andsource_sha256still names the original source bytes. Bothverify.pycheckers pass. No results change.Checked with the full test suite, ruff, the doc-spec, vocabulary, profile, configuration, and schema checkers, and the twiddle-table check.