Skip to content

ci(p3b): promote sealed canonical portable into Field Capture - #453

Merged
masarray merged 12 commits into
mainfrom
ci/p3b-field-capture-sealed-package
Oct 7, 2026
Merged

masarray merged 12 commits into
mainfrom
ci/p3b-field-capture-sealed-package

Conversation

@masarray

@masarray masarray commented Oct 7, 2026

Copy link
Copy Markdown
Owner

Supersedes stale PR #450. Continues #449.

Why this supersedes #450

The old branch predated CI-P3 sealed Windows package reuse and the artifact-readiness hardening. This version uses the same ARSAS-windows-package-input verifier as installer validation rather than introducing a second gh run download path.

Changes

  • Seal the canonical portable build-identity JSON inside ARSAS-windows-package-input.
  • Cross-check that identity against exact source, ARIEC61850, ArdIrec, portable and native-bridge hashes before materialization.
  • Expose verified portable + identity paths from the shared package verifier.
  • PR Field Capture consumes the exact sealed package, copies exact canonical portable + build identity, then runs its own portable smoke and publishes under the existing field artifact contract.
  • Field-specific P0-5c/P0-5d/physical checks remain independent.
  • Manual workflow_dispatch keeps reusable full regression + independent publish fallback.
  • Shared bounded transient archive-404 retry from fix(ci-p3): retry transient sealed-artifact download readiness #452 is inherited automatically.

Authority

No release/installer/physical/runtime authority change. The normal PR path removes duplicate native/.NET portable publish only after P3A proved byte parity across two independent builders.

Acceptance

All package-verifier fixtures, P0 budget/contracts, canonical Build ARSAS, installer validation and Field Capture must PASS on the fresh synthetic merge. Field Capture must not execute its independent PR publish path, but its smoke and artifacts must remain green.

masarray commented Oct 7, 2026

Copy link
Copy Markdown
Owner Author

CI-P3B final acceptance on exact head def5d86dcfede180583d80cbb2d07edd56bb77d5 / synthetic merge 4fd389eccd8f7a55385bba154be39272731c9ecb:

  • 12/12 triggered workflows SUCCESS, including CI-P0, Build ARSAS, Field Capture, installer, Mainline, Merge/Production, Golden/Repeat and SV.
  • Canonical Build ARSAS sealed package run: 37604636188/1.
  • Full regression: 1323 passed / 0 failed / 0 notExecuted.
  • Exact engine: 648124097621046f5f127ceb1cf853fea54db730.
  • Exact ArdIrec: 7dbc7149db668126a493ce338264363a6ec5ec00.
  • Exact native bridge SHA-256: fa8efcaf26e8ebb0a29808a2e52ad5c9f466ec2df146945d29c5d662987c41ce.
  • Sealed canonical portable: 78,789,760 bytes, SHA-256 db3c6fd366f8d757637dcefe15ae315b4aaffcc48891e8838d25d9f1f41ecfba.
  • Field Capture promoted portable: same 78,789,760 bytes and same SHA-256.
  • Portable build-identity JSON is also byte-identical between sealed canonical package and Field Capture artifact.
  • Field Capture P0-5c/P0-5d/physical checks PASS, then Promote exact sealed canonical portable PASS.
  • On PR, Field Capture independent .NET setup/publish steps are confirmed skipped; runtime smoke and field artifact publication remain PASS.
  • Installer consumes the same sealed package, manual rebuild/publish steps are skipped, installer compile + silent install/runtime smoke PASS.
  • Shared verifier preserves bounded transient-404 retry and all exact source/engine/ArdIrec/TRX/file-hash/build-identity checks.
  • releasePromotionAuthority=false remains explicit; release mutation is not changed by this PR.

@masarray
masarray marked this pull request as ready for review October 7, 2026 10:12
@masarray
masarray merged commit 9fd31e9 into main Oct 7, 2026
17 checks passed
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-07T10:15:55.916220Z def5d86 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant