Repository navigation
Conversation
Enable the release branch test trigger and repair the inert recovery provenance fixture exposed by that run. No production app code changes.
(cherry picked from commit f225c19)
This was referenced Oct 22, 2026
This branch has not been deployed
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.
Requires strict platform installed-byte proofs at the canonical receipt root, all five product observations, Retry and key/PIN UI, with equality across observations and binary hash binding to the recorded build. Previously the separate read-only consumer could accept those observations without the later #7083 proof fields.
Small follow-up to #7085; producer checkpoint preserved. Exact head
546d77261d02c0633e45b2c62df8f8e5580620c0, branchcodex/r5-trusted-installed-byte-proof. Patch-only review. Approximately1k changed code/test tokens.Actual Node22.23.3 checks:182 consumer /203 combined consumer+B1 controls PASS, zero failures/skips. Independent agent rerun203 PASS and source review found no blocker. Negative tests rehash artifact/receipt/attestation before asserting the specific installed-byte failure, including missing/false/truthy/malformed/extra/mutated/mismatched proofs for both platforms. No live canonical receipt exists; all API/artifact controls remain synthetic. iOS inventory and older build tree hashes use different algorithms; executable binding plus complete per-observation inventory equality is deliberate.
Preparation remains read-only and uninstalled: no B1 import or authorization flag change, native execution, protected configuration, signing, upload, distribution, deployment or publication.
Codex local handoff
State: NEEDS_LOCAL
Base: sprint
Head branch: codex/r5-trusted-installed-byte-proof
Head commit: 546d772
Goal and acceptance criteria: Reject incomplete or drifted installed-byte evidence before producing a read-only origin proof.
Changes made: Strict receipt schemas/equality/build binding and actual negative controls.
Cloud checks: Node22 consumer182/combined203 PASS; independent combined203 PASS; whitespace PASS. Native NOT RUN.
Required local checks: IOS, ANDROID
Local checks requested: Genuine exact-canonical hosted upstream receipts after approved installation; no personal Mac required. No application/native code changed.
Risks / known gaps: Full native matrix, installed trust, official analysis/run linkage and future gate integration remain unverified; authorization remains false.