FAT P5.4: semantic structured report projection

[masarray]

Scope

Stacked physical-field fix on top of FAT v2 P5.3 / PR #236. This PR intentionally changes only the structured InformationReport projection seam needed for controlled relay retest.

Exact head before this patch: 937f57f46753968d4a6dbe0699848a841cde1f8a.
Exact production commit: 4dd3880f1767a0af305aa80ed7bfa6d570c43486.

Physical failure being closed

The relay proved static DataSet/RCB acquisition is healthy, but whole structured analog members such as I_MHAI1.ThdA / V_MHAI1.ThdPPV reached the ARSAS report receive seam as REPORT_RAW_STRUCT. The old receive path always called the baseline MmsReportValueProjector, so model-backed scalar descendants never reached the existing live point cache.

P5.4 wiring

• pins ARIEC61850 to exact green engine SHA 888545bbca1e26040b3f7a86193e2dae013e964f from draft engine PR Add bounded two-cycle Sampled Values snapshot proof #106;
• supplies the exact per-IED hybrid planning authority (LiveDiscoveryModel or opened SCL design model) to a small semantic report projection bridge;
• changes the production report receive seam to use the semantic overlay;
• caches semantic context only inside the NativeIec61850Client instance and resets it on reconnect/replanning, so no model state crosses IEDs;
• preserves the exact static DataSet membership/index as protocol identity;
• fans out every schema-proven scalar descendant and never chooses a sibling phase as the primary value;
• fails closed: unexpected semantic projection failure preserves the baseline raw projection and emits REPORT_SEMANTIC_FALLBACK rather than inventing evidence or dropping the MMS association;
• existing runtime point matching/FAT row identity remains unchanged.

Regression

SemanticReportProductionWiringRegressionTests locks both boundaries:

1. the production ReceiveReportMonitorSliceAsync path must call the model-backed semantic bridge, and hybrid planning must supply/reset its authority;
2. a whole three-phase structured ThdA static member remains semantically ambiguous at membership level (PrimaryValue == null) but a valid InformationReport fans out to phsA/phsB/phsC.cVal.mag.f with semantic-structured-leaf projection status and no REPORT_RAW_STRUCT parent update.

Exact-head evidence

Engine:

• ARIEC PR Add bounded two-cycle Sampled Values snapshot proof #106, SHA 888545bbca1e26040b3f7a86193e2dae013e964f
• .NET CI #432 / run 33489485962: SUCCESS

ARSAS SHA 4dd3880f1767a0af305aa80ed7bfa6d570c43486:

• Validate IO List Testing #534 / run 33495383195: SUCCESS, 169/169 focused tests
• Validate SV evidence bundles #700 / run 33495383165: SUCCESS
• Validate ARSAS Windows installer #479 / run 33495383203: SUCCESS
• Build ARSAS #1591 / run 33495383266: SUCCESS
  • solution build: SUCCESS
  • full ARSAS regression: 565/565 passed
  • real win-x64 portable single EXE publish: SUCCESS
  • portable EXE smoke test: SUCCESS

Locked exclusions

• no new SCL/XML parser
• no fuzzy reference guessing
• no phase-primary heuristic
• no operator checkbox/disposition mutation
• no injected/reference value, tolerance, error %, or analog auto-PASS
• no main merge / no ready-for-review transition before controlled physical IED retest

Software gates are GO for controlled physical retest. Physical GO is not claimed until the same relay/CID confirms the previously raw structured members reach the live FAT rows as valid scalar descendants without identity drift.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.