P6.2-B: keep monitoring association stable and consume safe static report projection - #219
Conversation
|
P6.2-B CI evidence — ARSAS head
Keep draft/unmerged pending physical SIPROTEC retest. Acceptance focus: first healthy association must stay alive, static RCB must start without a preceding full dynamic mutation, supported MX report structures must project to the exact selected leaf with real q/t, and ambiguous report structures must remain MMS-authoritative rather than being guessed. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
P6.2-B field stability integration
This draft integrates ARIEC61850 PR #89 after physical SIPROTEC evidence showed two distinct regressions:
Integration behavior
instMag.f/mag.forinstCVal.mag.f/cVal.mag.fleaves with decoded q/t;Regression coverage
Do not merge until ARIEC PR #89 and all ARSAS CI workflows are green. Physical SIPROTEC retest is still required before release.