[BLOCKED: ARIEC stabilization] Consume hybrid report planner with physical evidence

[masarray]

Integrates ARSAS with the ARIEC61850 MmsHybridReportAcquisitionPlanner as the authoritative static/dynamic BRCB/URCB acquisition planner.

Integration stabilization gate

DO NOT MERGE while ARIEC61850 local Codex bug-fix work is still active.

ARSAS currently pins the last validated baseline engine SHA 2af88f51df759c7a7083795b3804ab8dc41e8922 only to preserve a reproducible regression baseline. ARIEC main has already advanced to 32351b42b4719e5dccfa068fbbd797c2414a6b4b via PR #75 (Fix live dataset and cross-domain report planning), which directly changes the same integration surface: live DataSet-directory evidence, MmsClientSession.DiscoverAsync, and MmsHybridReportAcquisitionPlanner dynamic cross-domain behavior.

No ARIEC source changes are part of this ARSAS PR. Do not copy engine heuristics into ARSAS to compensate for an engine-under-development state.

Before this PR can leave draft status:

1. local ARIEC bug-fix work must be finished/merged and a stable final engine SHA identified;
2. compare the final ARIEC API/behavior against the current baseline, especially live DataSet discovery, RCB availability, hybrid static/dynamic segmentation, persistent report activation, and report projection;
3. re-pin engines/ARIEC61850.lock.json to that exact final SHA;
4. rerun full ARSAS build/regression/package/smoke CI on the exact re-pinned head;
5. run static BRCB, static URCB, dynamic BRCB, dynamic URCB, residual polling, report-silence, and failure-path characterization again;
6. only then perform/accept physical IED evidence. Cloud CI is not physical report proof.

Consumer scope

• build/consume the existing ARIEC typed signal catalog from the device live model;
• map selected ARSAS points only through literal engine-exposed references, never fuzzy/vendor aliases;
• obtain fresh RCB availability from the active MMS association;
• consume engine segments for StaticBrcb / StaticUrcb / DynamicBrcb / DynamicUrcb;
• execute the exact MmsReportSubscriptionPlan emitted by ARIEC without app-side re-planning;
• leave MmsPollingFallback, Uncovered, unmapped, planner failure, and report silence on safe polling semantics; none imply SIGNAL MISSING;
• preserve the existing app planner only as compatibility fallback when no typed live-model authority exists;
• collect physical-validation evidence per plan: activation result, subscription/member/setup-write details, report frame/update counts, change-verified point count, and first/last report time.

Baseline evidence

ARSAS head 0057fd1b87b93186bec486a5d7452db36f9cab55 is green against baseline ARIEC 2af88f51df759c7a7083795b3804ab8dc41e8922: full application build/test/package/smoke, installer smoke, IO List regression, and SV regression all succeeded. This proves the current consumer branch is internally stable against the old engine baseline; it does not prove compatibility with the in-progress ARIEC bug-fix state or real IED traffic.