[masarray]

A+B synchronization — two missing fixes from Thread A's PR #566

Base is current UI PR #571 SHA 15947f4efd18, itself stacked over #570 → #569 → #568 → #567 → #563 → #560. Thread A's consolidated PR #566 independently diverged from #563, and contains strict unified composer routing plus CF historical/current/stale distinction. Do not overwrite one branch with the other.

Reconciled changes

• Preserve all of UI: exact six operator SVG icons with resize-safe navigation #571's UI/icon changes, M2.14: suppress erroneous angles on scalar MV measurements #570's no-angle-on-scalar MV guard, M2.14 SG: show model-verified active setting values in parameter rows #569's SG leaf binding, M2.14B/C: inventory-proven read-only SGCB and GoCB status inspector #568's inventory-safe read-only control state, and M2.14 A/B: shared phasor compatibility gate for extra IEC vectors #567's CanPair source/timestamp/association check.
• Incorporate the missing behavior from Integration A+B: M2.13 SSOT + M2.14 Browser with unified phasor authority #566: one WPF Browser composite dispatcher for standard and extra neutral/net/res IEC vectors. The independent vector adapter is invoked only inside IedBrowserEngineeringComposite.TryCompose, so it cannot bypass the same CanPair gate or truncate valid fourth neutral components.
• The CF units parent now differentiates Historical discovery CF vs Verified IEC CF configuration vs Stale IEC CF configuration; stale values show Offline ·, preserving existing canonical provenance.
• Three independent regression tests for four-component source/timestamp mismatch, CF history/current/stale/reconnect authority, and continued scalar MV protection. Updated prior test expecting dual-path WPF renderer.
• No duplicate runtime store, inferred angle, cyclic MMS read, RCB/SG writes, GI, engine pin change or public stable merge.

Gates and acceptance

Require exact-SHA Windows build + application/engine/native tests + portable artifact. Coordinate with A through #563/#566; PRs remain Draft. This is a narrow semantic reconciliation, not a full merge of all engineering branches. Physical BCUGE/ZIV field acceptance remains necessary.

[masarray]

M2.13 Thread A synchronization (no branch mutation): new Draft PR #573 #573 uses your latest #572 HEAD 6da4200031d48ee19a055a0563b1aef604b34602 as FIRST merge parent and prior #566 A+B adca74da9497a367d46b2b7668c596b1697de350 as SECOND. Its tree preserves all #572 changes (SG/SGCB/GoCB, scalar-MV angle guard, icon layout, joint CanPair and CF evidence) and adds only M213KCrossThreadSsotStressTests.cs covering 8 simulated report ingress lanes/6,144 Report+Read updates, 128 reconnect cycles, strict case+FC isolation. New CI exact SHA d7313f11993c32634403153640d2f991ec8e6abc ongoing; previous green #566/#572 artifacts do not prove this SHA. Keep PR #572 as owned upstream; physical BCUGE field acceptance and measured p95 WPF/multi-RCB remain pending. No main merge or engine pin change.

[masarray]

D28 legacy candidate archived, not merged. Per the operator's explicit instruction, the latest accepted ARSAS working evidence is the baseline; no new hardware/packet capture cycle is required for cleaning up outdated PRs. Historical candidate 6da4200031d48ee19a055a0563b1aef604b34602 is withdrawn from the integration queue, with source/review history intact. Closing it does not assert its unmerged source fixes shipped, does not authorize weakening protocol safety, and does not modify main, stable, RC or engine pins.