Repository navigation
Conversation
…t discovery overlay churn
…-card flicker overlay
…ed unverified leaf exclusion
…oss selection changes
…V/OR/BL and fixed IED-card progress
|
2026-10-20 integrated field test protocol for exact SHA |
|
CROSS-THREAD P0 ANTI-REGRESSION LOCK (user accepted 2026-10-21 WIB) 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; 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. |
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.cswas 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
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
mainmerge, public release or automatic changes to IED. Avoid retargeting main while it has diverged independent changes; use this exact trial artifact for FAT.