Repository navigation
Conversation
…in Event properties drawer
…ard and click routes
…ntal exporter selection tests
…; defer multi-exporter
…d lock package identity
…earm v1.6.41 request
…gine while preserving historical physical qualification
…t altering R10 hardware baseline
…r evidence and CI
Qualify combined SV/IO/FAT path filters with both regression guards. Canonical Windows: 1761/1761 ARSAS, 19/19 engine, 6/6 native managed tests; portable smoke and sealed package; SV/IO and all 12/12 PR workflows green. Supersedes draft PRs #562 and #564; no runtime, engine lock, or stable release modifications.
…r accepted responsive-report baseline
…ected GUI/FAT baselines
… without SG7 authority rollback
…eakening SSOT or palette gates
RC integration progress / M0-M2 source audit — 2026-10-24Single release lane: PR #727 / release/arsas-integrated-rc0-20261024 @ 77c6cd2. No update to main. Subordinate staging integration PR #728, head 416d01e (NOT YET MERGED).
|
…release lane Validated source tree 156663e. Windows Build #40065679419, SV #40065679411, P1 #40065679583 green at synthetic merge 195a272; ARSAS 2955/2955, pinned native bridge 6/6 and packaged EXE smoke. Remaining R7/IO/COMTRADE/Reference Guard on final RC head and physical FAT still mandatory. No production/main promotion.
RC0 M3 — exact-source CI and portable candidate PASS (2026-10-24)AUTHORITATIVE branch HEAD release/arsas-integrated-rc0-20261024 @ f177f34 (PR #727 remains DRAFT, no main merge). GitHub Actions synthetic PR merge 21c45b0, identical git tree 156663ead8efbdb1254ba6e9df64245652cc5506 to branch HEAD. Therefore packaged/tested contents exactly match the integrated RC tree, despite different synthetic merge commit identity. SOURCE CONSOLIDATION: PR #728 merged into isolated release branch as f177f34 after premerge Build #40065679419, SV #40065679411, P1 #40065679583 all SUCCESS. 27 accepted SMV source blobs taken byte-for-byte from final field checkpoint #725; 10/10 Write/post-Write source blobs inherited unchanged from accepted #726. Engine lock f75e323e9f8443aa20e0a3818a1d5d77255b2c0f unchanged, ARDIREC lock unchanged; MainWindow.xaml, SSOT runtime, Write, Control, natural Command ordering kept from latest RC0. EXACT RC0 CI green:
ONE Windows portable EXE: Actions Build #40066246363 artifact #12549765480, name ARSAS-1.6.40-win-x64-portable.exe, EXACT SHA256 2177ff41e0fb9bc043370cf1bca8df37219fc772614a83789826a08e9e54b3ae. This is RC preview candidate, not v1.6.40 public stable equivalence. Do NOT relabel version, stable/release, or previous physical acceptance. QUALIFICATION BLOCKERS (explicit NOT-RUN, NOT PASS): standalone IO List, standalone COMTRADE integration, and Interoperability Reference Guard workflow_dispatch could not be started from this connector session (GitHub integration exposes no workflow_dispatch write; authenticated browser automation unavailable due to depleted wallet). Full ARSAS tests cover existing relevant suites, but are not a substitute for those separately required workflow attestations. Also physical combined 3-IED FAT and WPF p95/p99, SG7 event/BufOvfl/SOE continuity evidence remain pending; no real hardware action was executed by assistant. ARIEC staging PR #192 still DRAFT. Independent 17 main-only commits (release/version/RCB) not reconciled. No main merge or public release/tag. Next operator FAT: use ONLY artifact #12549765480, record SHA256 and diagnostics with SG7 77/77 4/4 RCB (including reconnect and 13 continuity findings), ZIVAVR 8/8 1/1 with integer TapChg and exact post-Write Read, GR_X 13/13 2/2; compare SMV final cool-blue UI/stream HOLD/RAW vs 9-2LE, Smart IP, six Browser sections, Command Dock Tap-first/Status Only, report source/q/t/association, responsiveness/Stop. No unauthorized control. Preserve original accepted checkpoints as distinct physical evidence; do not claim this combined SHA has been field accepted yet. |
…ected IED identity Preserve Reports > DataSets > Data Model > Files > Setting Groups > GOOSE. Bind Name and Endpoint typography to existing reactive IsActive selection authority; no MMS/SSOT/Control/engine changes. Add explicit regressions and update the outdated root-order expectation.
D27 engineering reconciliation: 102 → 51 open PRs (51 resolved in this pass)Three real merges into the integrated RC, guarded by exact head and prior green source CI:
48 old PRs closed with individual audit comments: #479, #653 are explicitly superseded by integrated #759/#757; the other 46 have GitHub exact-ancestry evidence Current RC HEAD: Post-integration GitHub Actions at current RC SHA: 30 PR workflow runs because this RC is used by both #727 and #729. Final outcomes: 16 success, 12 skipped, 2 failure. Both canonical Windows Build ARSAS runs completed SUCCESS. The two RED workflows belong to mainline candidate #729: Remaining 51 open PRs need content/physical integration, not cosmetic mass closure. No manual CI reruns were requested; all merges used expected HEAD leases and did not affect |
D28 — close fulfilled RC staging PR as archival checkpoint (not a main merge)Maintainer instruction: the latest successful operator-accepted evidence is final for the purpose of this backlog cleanup; no further hardware captures will be sought for historic PRs. The integrated staging branch already contains the complete accepted candidate source chronology and D27 merges #759 (P7.6 diagnostic), #760 (exact-PR COMTRADE proof), and #757 (fail-closed CI admission), all three recorded as actual merge commits in the RC history. This PR is a coordination/staging lane, not an extra feature PR that must remain perpetually open, so it is being closed as NOT MERGED. Closing does not delete or rewrite The historical main-promotion PR #729 was separately closed UNMERGED; existing R7/reference guard failures are not made green or silenced. Unique fixes in other closed legacy PRs are not automatically claimed integrated. Any new work should use the accepted baseline/source already on GitHub, not resurrect old field capture demands. No new PR, release, real-hardware capture or engine repin is required for this archival action. |
DRAFT, DO NOT MERGE INTO MAIN OR PUBLISH A RELEASE. Single handoff and RC staging lane for consolidation of the accepted performance/SSOT report engine with exact field-accepted FAT Write + fresh post-Write readback. Base
b1d177885ff8cba6515e19f0aec33d1fc887519b; source integration commit6cc3aa1ab7aa6ea7cb1f2f580f00becca7a51255; full handoff and release acceptance plan indocs/handoff/HANDOFF_ARSAS_ALL_THREADS_TO_RC_2026-10-24.md. Code changes are only the exact ten Write/SSOT files from #679/#726 (byte-for-byte matches), plus this markdown. No SMV or layout/engine changes. CI must run exact SHA (Build Windows, R7, P0/P1, Reference Guard, SV, IO List, COMTRADE). Readiness mainline R10 must not be bypassed; run physical FAT on three IEDs, verify 77/77 SG7 and 4/4 RCB, integer BSC TapChg, Command Dock Status Only, Browser 6-section fixed order, blue-white SMV, Smart IP, WPF responsiveness, SOE BufOvfl before release. Do NOT close #679/#726/#721 until promotion and provenance checked; preserve historic checkpoints.