[masarray]

Freeze — no new Write development

User has physically tested and accepted MMS Write -> popup closes -> exact DA MMS Read -> canonical LiveValues/SSOT -> IED Browser leaf updates. User requests hard freeze; SSOT V2 performance and SMV advanced work take priority.

Field-accepted frozen checkpoint: checkpoint/arsas-write-damodel-field-accepted-20261024 -> 04350e15f9be9d429cf1a908b81bab922c36f093. Previously green Windows Build/R7/SV at source 96ba20175c3a6f984f043ac9f8c692c2bff09a6f and user-confirmed relay UI acceptance.

Rehearsal, no upstream merge

This branch starts from latest SSOT V2 responsive/static-report head fb4932d127807fa83bf3b1fb70058fbdfdb3c966 (#724) and overlays only the 10 changed Write and post-Write exact SSOT readback files from frozen field-accepted FAT tree. It does NOT take the old FAT branch as merge parent and does NOT change App.xaml, MainWindow.xaml, MainWindow.xaml.cs, Models/IedBrowserLiveValues.cs, performance journal, Views/SmvInlineViewer.*, or SMV presentation/phasor/clock/GOOSE/PTP/native engine files.

No merge into #724, #679, SMV checkpoint, or main without SSOT and SMV owners coordinating. Require exact-head Windows Build, SSOT large-grid/SG7 regressions, R7, SV, SMV visual/power, and physical spot-check of Write afterward. Advanced SMV accepted checkpoint checkpoint/smv-tab-v1640-fat-accepted-20261024 (84b6e15f...) is authoritative for SMV; do not reverse merge this candidate over that checkpoint. Resolve SMV separately with SMV-side preservation. This PR is a non-release interoperability proof, not a request to change frozen operator Write.

[masarray]

2026-10-24 user handoff — FREEZE Write, do NOT regress SSOT V2 / SMV

User has physically confirmed Write -> popup closes -> exact leaf re-read updates IED Browser Data Model and wants this Write feature CLOSED/FROZEN; no new Write UI changes. Verified permanent checkpoint checkpoint/arsas-write-damodel-field-accepted-20261024 = 04350e15f9be9d429cf1a908b81bab922c36f093 (PRs #718 and #723 merged to draft FAT #679). Integration rehearsal PR #726 HEAD 42c7cfe1364faaeeee64180bd82e5dbef4f7355a: exact-head Windows Build 40054496892, R7 40054496908, SV 40054496938, P1 all SUCCESS; only 10 Write/readback paths vs responsive SSOT #724 base. #726 is still OPEN DRAFT, not merged.

HARD non-regression gate: user explicitly prioritizes SSOT V2 responsive/static-report work (#724) and advanced SMV accepted checkpoint/smv-tab-v1640-fat-accepted-20261024 = 84b6e15f0e7a94b419d172921b366c4cb7f28793. We compared advanced SMV checkpoint vs #726: histories are DIVERGED (103 commits behind / 264 ahead from advanced SMV to #726) and differ in actual Views/SmvInlineViewer.xaml, SMV presentation/grid/measurement files and App.xaml. Therefore do not merge FAT #679 or #726 wholesale onto SMV, do not overwrite SMV UI, and do not declare global integration complete. SSOT + SMV owners should construct a coordinated candidate from their latest accepted baseline, apply only the frozen Write slice if required, review diff, then run exact-head Build, 2885+ app regressions, SSOT SG7 large-grid stress, SMV visual/RMS/sync regressions, R7, SV and physical Write spot-check before mainline or release. Write development thread can close; cross-thread integrator owns remaining work. No main merge authorized here.

[masarray]

Cross-thread immutable SSOT/performance merge anchor — 2026-10-24

PR #724 MERGED into isolated integration/arsas-ssot-performance-p0-20261024; merge commit b1d177885ff8cba6515e19f0aec33d1fc887519b, test artifact commit b136b927636219e03c9ce092311f673c46201645, HEAD fb4932d127807fa83bf3b1fb70058fbdfdb3c966, all three have identical complete Git tree 2e1a209b72039e2277b2d8af621f812416307ad7.

Immutable staging refs: checkpoint/arsas-ssot-performance-field-accepted-20261024 (physical test merge b136) and checkpoint/arsas-ssot-performance-merged-20261024 (real integration merge b1d). Operator DIAG at 10:07 WIB: SG7 77/77 live, 4/4 routed RCB, 156/156 static descriptors; ZIV 8/8+1/1, GR_X 13/13+2/2; control two successful SG7 CSWI OPEN/CLOSE; 0 cyclic MMS process polling. New timing SG7 discovery 9.835s, Static UI inventory 2.123s, full selection 2.941s. 2,891 app +1,272 pinned engine regression PASS; EXE smoke PASS.

High-priority merge gate for PR #726 and all sibling threads:

1. SSOT process-value authority and WPF responsive work must be retained exactly, no restore to earlier pre-P0: Responsive Static DataSet reporting and green IED progress (SSOT preserved) #724 signal matcher, no UI-thread quadratic scan, no implicit cyclic polling or unsafe command/write authority.
2. The accepted advanced SMV tab is separate: checkpoint/smv-tab-v1640-fat-accepted-20261024 @ 84b6e15f.... Its Views/SmvInlineViewer.xaml blob is 13559d76..., whereas SSOT branch blob is 7deb737c...; advanced SMV also has additional Views/SmvAnglePresentation.cs, Views/SmvPowerMeasurements.cs, Views/SmvSyncPresentation.cs not present in the current P0: Responsive Static DataSet reporting and green IED progress (SSOT preserved) #724 tree. So P0: Responsive Static DataSet reporting and green IED progress (SSOT preserved) #724 merge does not mean advanced SMV has been incorporated. Preserve those exact accepted SMV features by targeted forward reconciliation; never overwrite using old MainWindow.xaml, Views/Smv*, App.xaml, native engine or lockfile blindly.
3. Preserve IED Browser category/navigation order Report → DataSet → Data Model → Files → GOOSE → Setting Groups, and all existing Browser/Write/Command Dock ordering/state tests. Do not merge PR Fix verified tap-first Command Dock visual order (WPF sort SSOT, viewport, regression) #721 tap-first dock-order or this Write PR by merely copying whole MainWindow files. PR INTEGRATION GATE ONLY: user-accepted Write onto latest SSOT V2; preserve advanced SMV #726 head 42c7cfe1364faaeeee64180bd82e5dbef4f7355a is currently untouched by P0: Responsive Static DataSet reporting and green IED progress (SSOT preserved) #724 merge; avoid changing it without exact-head CI/FAT.
4. No merge to divergent public main (was 45348eccf24e941dd185e5fb729217923846c610) until full multi-branch merge reconciliation, exact-tree/code review, per-feature browser layout+SMV visual regression, Windows CI, R7, SV and relevant operator spot check. Existing R10 mainline physical readiness gate must stay enforced.
5. Report continuity remains unresolved: SG7 21 findings/4 BufOvfl, ZIV one BufOvfl, GR_X one discontinuity; do not claim lossless SOE, see P10.9Z: lossless buffered IEC 61850 events and command outcomes in SOE #544/P10.8: isolate BCUGE BRCB BufOvfl and SqNum/EntryID discontinuities with same-slot wire-order evidence #520. P0 static 21-pending/3-unrouted issue P0 SG7_BCU: 21/77 static Report values pending, 3/4 RCB streams have no proven ingress #707 is closed only for the resolved static process-value/traffic acceptance.

This PR remains its own isolated Write integration proof. This comment is a required coordination guard, not approval to merge Write/SMV into #724 or main.

[masarray]

Cross-thread integration notice — RC0 handoff (2026-10-24)

Authoritative draft RC consolidation PR #727, source branch release/arsas-integrated-rc0-20261024, exact head 77c6cd2dccd27de155bbad6799b3d914be118c9a. Full plan docs/handoff/HANDOFF_ARSAS_ALL_THREADS_TO_RC_2026-10-24.md.

This DOES NOT merge into main or close your PR. Reconciliation on the SSOT/performance accepted base b1d177885ff8cba6515e19f0aec33d1fc887519b proves the final FAT Write/post-Write readback delta is exactly 10 files with identical blob SHAs in #679 and #726. We staged those ten files ONLY on the isolated RC branch. All other baseline blobs, including Views/SmvInlineViewer.xaml, MainWindow.xaml, and the engine pin are unchanged. Do not re-merge a stale whole-branch #679/#726 over RC0 or overwrite advanced SMV/IED Browser/Smart IP.

RC0 remains DRAFT; exact CI, protected visual regression, three-IED field FAT, report continuity/SOE and R10 release gates are pending. Resolve conflicting future changes on the one RC lane with expected-SHA checks and preserve checkpoint history. PR closure should be provenance-based after accepted integration, not premature mass-closing.