Repository navigation
Audit: the three omitted #626 assembly digests are payload and JSON-file hashes - #2695
Merged
Mister-Meeseeks merged 1 commit intoOct 16, 2026
Conversation
template_sha256 is a decompressed payload hash, so the recorded Linux mismatch is not a gzip-header artifact. The owner and invoice digests are indented JSON file hashes that still mix nested containers with mathematical fields. Co-authored-by: Cursor <cursoragent@cursor.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
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.
Summary
research/selected626-linux-reconciliationremoves before comparing Linux run38317651752with the committed Conditional κ = 0.001635527380375392: coordinated owner repair on PR623 #626 assembly.template_sha256is SHA-256 of the decompressedGLOBAL-TEMPLATE.json.gzpayload. The recorded Linux/committed mismatch is therefore a template-content disagreement, not a gzip header difference.input_sha256.owner_auditandinput_sha256.fresh_invoiceare SHA-256 of indented JSON files. A nested container hash can change the file while a projection that keeps onlypaid_profilestays equal. Without the omitted files, those two disagreements stay mixed.No new kappa and no selected-frontier change. Seed
c0d742beb437484a0cb0c8971994843d, scope key91a9a2afec282c926282, baseb5ea56e0a5ac4552166253b1fa4be0753bb38c30. Claim: #2690Overlap refresh on 2026-10-15 covered 785 open PRs and 1322 discussions. Matches are this claim, the gzip-container convention, and the predecessor reconciliation. PR #2101 compares gzip payloads inside a different selected-replay authenticator.
Test plan
python3 -B research/pr626-omitted-digest-audit/verify.pyprintsPASS_PR626_OMITTED_DIGEST_AUDIT template=decompressed-payload owner_audit=indented-json-file fresh_invoice=indented-json-file differences=3python3 -B scripts/research_package.py --package research/pr626-omitted-digest-audit --check-onlyPASS_REGISTERED_RESEARCH_PACKAGE research/pr626-omitted-digest-audit outcome=completedverify_selected_resultrequires. Selected record sha256 remains10b9e340fd8e354a37a0c4813c90e5de1dd42044b5f6aca4a3fc5a42b685fa32.Limits
The audit pins producer blobs at sprint base
66849e1475c930fd7732b1a0067ffee7e1e95f60and does not rerunmake frontier626-verifyor reconstructOWNERS-AND-PROFILE.jsonandPREFIX-AND-INVOICE.json. It does not explain the numerical template difference. Predecessor credit stays with Josh Snider (jsnider3).Prepared by Riquelme Soares (@hevlyo) with substantial Cursor agent assistance. Apache-2.0.
Workflow note: a full clone of this repository is too large for a short session; a blob-filtered sparse checkout works, but
git addthen needs--sparse, and the selected baseline cannot run until its package roots are present.Made with Cursor