Skip to content

P8 integrated reporting: stage ARIEC #198+#199 in exact-SHA Windows trial without changing FAT pin - #763

Draft
masarray wants to merge 2 commits into
release/arsas-integrated-rc0-20261024from
integration/reporting-engine-p8-20261029
Draft

masarray wants to merge 2 commits into
release/arsas-integrated-rc0-20261024from
integration/reporting-engine-p8-20261029

Conversation

@masarray

Copy link
Copy Markdown
Owner

P8 — major integrated reporting candidate, isolated nonrelease consumer qualification

Source + engine identity

Meaningful product deliverable / existing CI topology

One existing CI-P1 shadow workflow + one existing Windows reusable build/test, NO NEW WORKFLOW. Label ci-p1-shadow gates it. Python resolver enforces source-diff selection, exact SHA, approved baseline, no promotion, no automatic RCB mutation, no cyclic MMS fallback. Offline negative regression fixtures included.

  • Windows checkout exact ARSAS PR head and engine staged SHA; validates ephemeral trial-only engine lock, never replaces tracked lock.
  • Single solution restore/build; reporting-focused ARSAS regression includes report/RCB/SG7/StaticDataSet/IedBrowser/MMS tests.
  • Reuses exact ArdIrec native bridge+CTest and existing portable self-contained Windows publish/smoke pipeline with version 1.6.42-reportingtrial and artifact ARSAS-REPORTING-P8-TRIAL-<engine>-win-x64.exe, SHA-256 build identity and explicit nonrelease manifest. Command-read previous build branch/version/name remain intact.
  • No field writes, GI retries, dynamic DataSet mutation or production release.

Gates / expectations

CI pass is code-qualified only, NOT demonstration of 77/77 and 4/4 SG7 in actual IED session. #707 remains open. Preserve user's earlier accepted FAT evidence; DO NOT demand a recapture simply for PR cleanup. No ARSAS main/RC/stable merge or engine lock repin until independently reviewed and field-supported. The goal is a real operator-downloadable read-only reporting candidate, plus test evidence to make an informed pin decision.

Copy link
Copy Markdown
Owner Author

FINAL P8 combined-source validation — 2026-10-29 (draft nonrelease, NOT promotion)

All exact PR HEAD 37165a0cebd27ae9756810c540426f97b3bfad3a checks now complete:

  • CI P0 workflow integrity #40893705578: SUCCESS, including new trial resolver negative fixtures and unchanged CI budget.
  • CI P1 shadow reporting engine trial #40893705654: SUCCESS with exact ARIEC ae1ce23dbc181c2a17aef20802f7517892fe4264, ARSAS reporting-focused 947/947 PASS, full Windows x64 compile 0 errors / 113 warnings, native ArdIrec bridge and regression successful; portable EXE built, launched with --portable-smoke-test, sealed, uploaded as raw Windows PE32+. Artifact 12905563273 ARSAS-REPORTING-P8-TRIAL-ae1ce23d-win-x64.exe 79,359,921 bytes, SHA256 c676a1b0969c81bc4ac74460645a49a7df15e7da18efffb05f95dc259d869896, independently downloaded and hash-checked.
  • Canonical Build ARSAS #40893705520: SUCCESS, pinned baseline ARIEC kept f75e323e9f8443aa20e0a3818a1d5d77255b2c0f; app full 2,990/2,990, pinned engine check 24/24, native CTest 9/9, managed packaged smoke 6/6, canonical Windows package seal/pass. Canonical EXE is baseline engine, not P8 experimental engine; do not confuse build identities.

Product status: PR remains intentionally DRAFT on isolated branch; integrated RC 833dbe328deb2b925ffe0a61823285b24499b37f, main 14e5dddf..., tracked engine lock and v1.6.42 stable not touched. No source/runtime RCB mutation, GI retry or MMS cyclic process polling introduced by this trial integration. This proves reproducible cross-repo code/packaging compatibility, NOT SG7 77/77, 4/4 physical Report delivery, nor C264 live FCD. #707 remains OPEN. No additional hardware capture is requested for GitHub reconciliation.

This branch has not been deployed

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant