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)
|
Coordination from protected-release preparation #7096, head Coordinate review/adoption and real compatibility with canonical #7084/#7095 (including explicit live Variables-reader identity/preflight), exact-canonical latest-run/current-attempt original Actions/artifact provenance, complete parent matrix and strict root/all-five/Retry/key installed-byte proofs. Official CodeQL security analysis-to-selected-run linkage remains unverified; successful workflow execution or API403 cannot clear it. Actual acceptance by producer AND stricter consumer is required before future separately reviewed gate integration. Native owner coordination is on #7082: one combined-source hosted window, no competing dispatch from this preparation. Fresh dedicated release environments absent; custody/signing/store identity UNKNOWN. Exact setup and reusable cloud-only operator handoff are in #7096. No credentials/config/protection changes, signing, upload, merge, deployment or personal Mac dependency. |
Adds a separate read-only consumer of original installed Actions provenance and exact canonical artifacts. Check/status names or JSON assertions cannot mint its private origin proof. It binds current protected source/driver/pin, latest exact-source producer run/current attempt, original job/check-suite/check IDs, official CodeQL security outcome, artifact API/digest/ZIP bytes, complete seven-case matrix, raw observations and production source hashes, then rechecks mutable authority.
PREPARATION ONLY / NO AUTHORIZATION CAPABILITY. B1 remains disabled (#7074); this module is not imported into it or the signing workers. Proofs explicitly retain release_authorized:false, authorization_eligible:false, execution_allowed:false. Official security-analysis-to-selected-run linkage remains UNVERIFIED (actual analysis API403), marked security_analysis_run_linkage_verified:false; successful Actions CodeQL execution does not clear its separate failed security result.
Exact head
a1e167cab4e8485bb84418cadfb2313cbcedb644, branchcodex/r5-trusted-origin-consumer. Patch-only comparison. Roughly9k code/test tokens; separate from canonical producer, platform signing adapters and orchestration.Actual source checks under Node22.23.3: 89 consumer/B1 controls PASS;100 full Node controls PASS when including the inherited .github controls; actionlint1 and whitespace PASS. All API/artifact cases are synthetic negative/positive controls, not live installed-provider verification. Current canonical producer cannot produce complete acceptance while its parent obligations are missing; this consumer rejects blocked/incomplete evidence.
No credentials/configuration/protection changes, native build/dispatch, signing, upload, deployment or publication. Setup inventory and limitations are in docs/r5-trusted-release-origin.md. Future integration must bind full security analysis/run provenance and keep every owner/environment/version/config/certificate/artifact gate; this read-only object must not mint B1's authorization capability.
Codex local handoff
State: NEEDS_LOCAL
Base: sprint
Head branch: codex/r5-trusted-origin-consumer
Head commit: a1e167c
Goal and acceptance criteria: Verify original installed exact-canonical test/artifact origins without granting release authorization.
Changes made: Read-only provenance consumer, bounded ZIP parser and fake API/artifact contract suite; no gate import or operation entry point.
Cloud checks: Exact source89consumer/B1 and100fullNode controls PASS; actionlint1/whitespace PASS. Live analysis API403 remains unresolved and capability is disabled.
Required local checks: IOS, ANDROID
Local checks requested: Genuine upstream hosted canonical receipts after approved installation; no personal Mac required. This package changes no native application code.
Risks / known gaps: Official analysis/run linkage, installed API permissions/pin, complete native matrix and future gate integration are unverified. No native or release acceptance claimed.