Skip to content

P0-FAT: combined Command Dock + Browser leaf + IED-card progress trial - #642

Draft
masarray wants to merge 9 commits into
fix/command-dock-event-driven-20261020from
trial/arsas-command-leaf-fabric-20261020
Draft

masarray wants to merge 9 commits into
fix/command-dock-event-driven-20261020from
trial/arsas-command-leaf-fabric-20261020

Conversation

@masarray

Copy link
Copy Markdown
Owner

Combined field-test candidate (2026-10-20)

This is a deliberate two-parent semantic integration commit from fully-green command PR #641 (17b339c0877e8941a5785ccbf56f5df98434ce3d) and leaf/progress PR #636 (3367f33450987d098f63bd604883bbefa2b3c010). Four leaf-only files copied unchanged. Models/MonitorModels.cs was merged by replaying each exact leaf patch hunk onto the command branch, then verifying the same hunk patch reconstructs the exact leaf file from common base; both command identity-preserving reconciliation and Browser micro-progress remain.

Physical scope

  • Stable Command Dock rows: no unconditional WPF Reset, event-driven row binding, no navigation-triggered MMS read, one dock expanded state.
  • Native control inspection/command admission serialized; fail-closed typed proof on real inspection error; unchanged secure SBOw/Operate/termination and interlock/synchro/Test.
  • Browser SV/OR/BL operator read rules preserved; thin fixed progress below IED IP preserved.
  • P109U/W + P0G dedicated regressions must pass together, plus entire ARSAS/engine/native CI and packaged EXE smoke test on exact merged SHA.

Explicit limits

Engine command-stage evidence is pinned to ARIEC61850 PR #183 by the current command ancestry. 7–13 s field native latency is not proven fixed; compare SBOw service, Operate service, positive termination, feedback on real IED. Do not imply CI establishes relay safety; operator must verify actual isolation/permit-to-test. No main merge, public release or automatic changes to IED. Avoid retargeting main while it has diverged independent changes; use this exact trial artifact for FAT.

Copy link
Copy Markdown
Owner Author

2026-10-20 integrated field test protocol for exact SHA 30a7f18e8e575604eb1306c96753daab9f9c4a51: (1) verify build About/diagnostic commit and ARIEC61850 pinned c85d4e20db722bd0c2729f2533b323b13d3ef735; (2) on isolated/authorized bench IED, connect and select 2+ verified controls, navigate Explorer -> Browser -> Diagnostics -> Explorer 100 times, verify zero grid disappear/reappear and preserved row identity and operator Interlock/Sync/Test selections; (3) expand/collapse Dock and verify no new unsolicited MMS control inspections; (4) run read-only Browser SV/OR/BL on operator action, confirm thin progress stays in fixed under-IP slot; (5) stage/confirm Open/Close ONLY on safe bench equipment and compare click->SBOw request/response->Operate request/response->CommandTermination->feedback with second client using same ctlModel/flags. Compare on-wire service timings, never time an early ACK against final feedback; (6) negative/timeout/late-termination, reconnect, different IED identity and failed read must fail closed; NEVER retry an uncertain physical command automatically. Capture elapsed/serviceMs/postResponseWaitMs evidence and exported diagnostics. If build CI fails or artifacts missing, block field trial; NO main merge/release based on code CI alone.

Copy link
Copy Markdown
Owner Author

CROSS-THREAD P0 ANTI-REGRESSION LOCK (user accepted 2026-10-21 WIB)
Canonical accepted source SHA: 5a33fb101026707caf6410ff097a569cfabf3939, frozen branch checkpoint/arsas-ctlmodel-glyph-command-stable-20261021. Windows CI #39499030618 success (11 workflows, 2,425 ARSAS+24 engine+6 package, native and portable smoke), artifact #12298499086.

Every concurrent leaf-data / engine / command / UI thread MUST read canonical engineering handoff #651 before overlapping edits, rebases, or promotions. Preserve exact selected CO inventory separately from physical operability; ctlModel icon+caption always present (declarative, virtualization-safe); per-IED GoCB gating; stable Command Dock and blue flush IED Card selection/progress; typed runtime safety and zero-reset fast path. Keep checkpoint SHA intact; do not replace the approved baseline with stale main, do not merge to public release without exact-SHA CI and field review. This is a traceable process lock, not a claim of enforced GitHub branch-protection ruleset.

PR #642 is the original combined command+leaf FAT integration; reconcile future leaf-data work against the accepted newer checkpoint, not just the older integration tree.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant