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.
Operator GUI FAT finding and surgical repair — 2026-10-24Field report from integrated RC portable version RC0 fix, not a new integration lane:
Changed files across this correction: CI on current SHA:
Do NOT claim portable binary ready until Build uploads new |
…ted operator order
M2 GUI visual FAT correction ACCEPTED BY EXACT-SOURCE CI — 2026-10-24Final RC0 branch/PR #727 HEAD: Operator screenshot regression fixed:
Effective five changed files relative to previously green RC:
Exact final source CI: ALL GREEN:
New Windows single EXE direct artifact (NOT the previous prerefix build): Previous screenshot diagnostic was taken on prefixed artifact with pre-fix SHA |
…and centered actions Narrow the fixed dialog from 480 to 410 DIP, widen symmetrical content insets, stretch IPv4/IPv6 editor and history to the available column, increase octet readability and tap targets, center accessible Cancel/Connect pair. Preserve existing IP parsing, history, manual IPv6 mode and advanced port behavior. Strengthen WPF layout regression contracts.
…mpact balanced geometry Keep all clean-room, disclosure, keyboard/history popup, palette, WPF STA and scroll safety checks. Replace obsolete 480x350 / fixed-265 expectations with 410x348 and stretch width assertions.
Smart IP / Add IEC 61850 IED — compact dialog integration (2026-10-24)Single release lane: PR #727 / release/arsas-integrated-rc0-20261024, head Operator approved a narrower, balanced modern form matching the reference mockup. Production-only change is Regressions strengthened in Exact final-head CI in progress: Windows Build #40071354642; R7 #40071354635; SV evidence #40071354652; P1 #40071354650. Do not publish or label candidate qualified until exact final-source Windows portable EXE smoke/test artifacts succeed. Previous #40069214420 portable is pre-form-redesign and does not contain the geometry fix. Hardware visual FAT at 100/125/150% DPI still required. |
M4 Smart IP modern compact dialog — implementation and exact-source Windows CI PASS (2026-10-24)Single RC integration lane PR #727 HEAD Operator-approved design implemented in Exact integrated source CI (all completed SUCCESS):
New final Windows RC preview portable (not previous artifact): Qualification note: CI includes WPF STA construction and source layout contracts but not actual Windows 100%,125%,150% scaled user visual comparison against approved reference; operator still needs to check final dialog screenshot. Other previously documented 3 standalone gates IO/COMTRADE/Reference Guard and integrated 3-IED physical FAT remain open. No public stable promotion. |
…out reverting accepted v1.6.42 candidate Preserve eight-tab IED Browser, cool-blue SMV, typed Write/Control, responsive SSOT v2 and latest Smart IP; import main-only safe Windows release fixes and published stable metadata, use new 1.6.42 prerelease identity, retain old stable v1.6.41 publication request without triggering automatic stable release. Main remains unchanged; prerelease/stable promotion still gated on current SHA and physical FAT.
…r and published ledger Manual release from a non-main ref is always prerelease even when input is misconfigured; --latest is restricted to stable releases, and .release/published.json cannot be written by a public preview. Add fail-closed workflow regression. No WPF, engine, reporting, control or runtime changes.
PUBLIC RC v1.6.42 — release milestone after mainline source reconcileHEAD Real work done: prior New high-priority release blocker fixed in Gate results and status: Original #727 RC source Next manual prerequisite from operator: On final 1.6.42 portable, record 3-IED FAT (SG7_BCU 77/77 4/4, ZIVAVR 8/8 1/1, GR_X 13/13 2/2), initial Report/Read q/t/source parity, SG7 BufOvfl and EntryID continuity across reconnect, fail-closed control + signed BSC integer TapChg + fresh Write readback, SMV/cool-blue/Smart-IP/IED Browser order and idle/active WPF input responsiveness. Include exact binary hash + timestamp + observed failures, do NOT use pre-1.6.42 FAT as proof. Field scope acceptance must be explicit before stable. Release route after gates: GitHub Actions |
…motion PR R10 positive/negative scenarios must receive their own explicit GITHUB_BASE_REF and GITHUB_REF_NAME; an outer PR to main must not contaminate a synthetic non-main test. Actual R7 and Reference Guard physical promotion checks remain untouched and fail-closed.
v1.6.42 release gate — exact final source verification at 2026-10-24Locked promotion candidate HEAD Build and portable on EXACT SOURCE TREE:
Release engineering fix: Immediate next gate for operator: Download above exact binary, run 3-IED FAT and confirm UI/reporting/Control/Write/SMV while classifying SG7 4 BufOvfl and SOE/EntryID continuity. Run manual release packaging workflow on this branch with |
…ease branch Filter Build ARSAS candidates by exact event PR display title before selecting latest run, preventing PR #729 synthetic merge evidence from shadowing PR #727 with the same head SHA and branch. Retain exact source SHA, engine SHA, TRX, full-test PASS, artifact run/attempt and latest-failure checks. Add adversarial same-head two-PR fixtures; no production or engine changes.
M5 Exact-source CI reconciliation CLOSED — 2026-10-24RC0 authoritative HEAD: Real code fixFour files only:
Final exact-SHA CI resultsPR #727 integration lane ALL RELEVANT GREEN:
PR #729 main-promotion lane (same source tree):
ONE designated field-FAT portable (PR #727, do not mix rebuilt binaries)Artifact: https://github.com/masarray/arsas/actions/runs/40085996337/artifacts/12557486215 Gates still open: (1) Manually run release-windows.yml on RC branch with version=1.6.42, prerelease=true, publish_release=false to verify installer, checksum, SBOM, provenance; this was NOT observed completed. (2) Operator must perform current-binary combined 3-IED FAT and explicitly classify SG7 SOE/BufOvfl and responsiveness, type/quality/source and Write/readback. (3) ARIEC engine PR #192 still DRAFT, cannot mainline-stable promote R7/Reference Guard without real physical authority. Public stable v1.6.41 unchanged; no tag/public 1.6.42 release. PRs #727/#729 remain OPEN DRAFT; main unchanged. |
…GITHUB_ENV export Manual 1.6.42 release packaging built its EXE but failed Get-FileHash because GITHUB_ENV does not populate within the writing step. Resolve, verify and hash the local EXE before exporting path and SHA to later smoke/provenance steps. Add regression for correct step-local ordering and downstream hash verification. No application/engine or stable-release authority changes.
M6: Manual Windows Release packaging failure diagnosed and fixed — 2026-10-24Failed operator workflow (correct RC branch): https://github.com/masarray/arsas/actions/runs/40091592899
Surgical correction committed:
|
Release manual packaging hotfix verified — 2026-10-24Operator reported RED manual run https://github.com/masarray/arsas/actions/runs/40091592899 on exact RC branch at Surgical fix HEAD: CI on exact new HEAD (completed): PR #727 Windows Build #40092124039 SUCCESS, R7 #40092123991 SUCCESS, IO #40092123999 SUCCESS, SV #40092124098 SUCCESS, COMTRADE #40092124030 SUCCESS, P0 Workflow Integrity #40092124024 SUCCESS, P1 #40092124028 SUCCESS. PR #729 Build #40092125889 SUCCESS, IO #40092125843 SUCCESS, SV #40092125765 SUCCESS, COMTRADE #40092125886 SUCCESS, Workflow Integrity #40092125667 SUCCESS. The R7 and Reference Guard for mainline promotion remain FAIL intentionally pending real physical engine authority; do not bypass. Still NOT yet proved: manual release workflow successful after hotfix. Next NEW |
RC0 visual integration prepared for release — PR #733 (operator preview available)The P0+P1 UI stack has been consolidated without merging anything to RC/main. Integration PR: #733
Independent release blockers seen on RC head DO NOT release/promote by this comment alone. See PR #733 exact-head CI and approval from preview testing first. |
Exact RC + P0 + P1 build is GREEN — preview readyIntegrated merge commit Exact-head GitHub Actions:
NEW exact combined release-candidate GUI preview:
Awaiting operator visual acceptance at 100/125/150% scaling, normal/restore/maximized positions, all tabs, GOOSE/SMV, smart IP wizard, and Command Dock. PR remains draft until user approves visuals and release owner reconciles independent physical R7/R10 interoperability authority blockers identified on the unchanged RC parent. Integration instruction: once accepted, merge PR #733 only to |
P0 visual field feedback hotfix — integration order for imminent RC releaseThe user tested the integrated P0+P1 preview (PR #733) on 1425×835 and 1709×895 Windows screenshots and reported three visual / performance issues.
New hotfix PR #735 #735 — targets the #733 branch; source SHA 5236263. Four added regression tests cover sizing, verified vs owned RCB proof, tab switching, and IED quick start. Integration: #735 CI green + Windows operator acceptance before merging #735 into #733; then merge #733 only into RC0 release branch after existing release gates. Do not ship earlier #733 portable EXE as final because it lacks these fixes, do not cherry-pick #735 separately into main, and do not waive physical R7/R10 interoperability acceptance. No MMS, RCB remote write/enable, GOOSE capture engine, subscription authority, or SSOT changes. |
Field GUI hotfix consolidated — PR #735 merged into the P0+P1 preview PR #733Merge commit on GUI candidate branch: 48808f8. Exact hotfix source CI (PR #735 head 5b0060a): all SUCCESS
Download hotfix GUI preview: ARSAS v1.6.42 Windows x64 portable artifact #12564825815 (GitHub provides an artifact ZIP containing the EXE; extract and run). Do not use older preview #12560446537 for hotfix visual validation. Changes: first launch 1740×960 DIP (fit to monitor work area), truthful current-session RCB enabled/active padlock UI, asynchronous shared Npcap adapter enumeration, no GOOSE model scan on tab selection, async route selection on IED quickstart with stale-selected-device guards. No engine/MMS command modifications. NEXT: Exact merge-commit CI on #733 head 48808f is running (Build ARSAS #40105608250 / IO #40105608282). Require its completion and operator screenshots (window 1425×835 and 1709×895, RCB icon while live, GOOSE tab timing) before merge #733 into RC. Two pre-existing R7/R10 interoperability authority failures on the RC parent remain independent blockers; do not waive. Do not merge #735 again into RC/main (it is already in #733). |
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.