G2.7 native per-IED Dynamic RCB field capability runtime

[masarray]

Goal

Add a native per-IED field-capability path for Dynamic RCB runtime without weakening ProductionEligible.

Why

ARSAS P1.6 can generalize member coverage only for the one legacy hard-bound AA1C1F08R4 witness. A different physical IED may advertise Write + DefineNVL + free Dynamic URCB capacity yet remain polling-only because it has no identity-bound field-capability witness.

Contract

• require an identity-compatible persisted InformationReportProven profile whose current InformationReport proof is real DataChange;
• require a separate durable native capability witness bound to the exact activation/report evidence IDs, RCB, DataSet, current identity/fingerprint/profile revision;
• require actual NO-GI dchg, exact included-member mapping, healthy association, monitor cleanup, proof-field restore, and fresh cleanup closure;
• treat that witness as mechanism capability, not a runtime member whitelist;
• keep fresh exact live-member resolution, fresh verified-free RCB availability, planner bounds, static precedence, and MMS residual fallback;
• keep ProductionDynamicActivationAuthorized=false / ProductionEligible independent;
• preserve deterministic per-RCB AR_HYB_<hash> DataSet identity.

Tests cover general residual expansion beyond the commissioning envelope and fail-closed behavior when cleanup or exact binding is missing.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 916af063f1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Record the completed runtime in the required documentation

This adds a completed G2.7 runtime capability, but a repository-wide search finds no G2.7/native-field-capability entry in README.md, docs/ENGINE_MATURITY_MATRIX.md, CHANGELOG.md, or the validation documentation. Consequently, the published scope and evidence remain stale even though the new API is present; update the applicable maturity, changelog, and validation documents with the unit-tested claim and remaining physical-validation limits.

AGENTS.md reference: AGENTS.md:L115-L124

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Reject null included-member collections

When this durable witness is deserialized from JSON containing "IncludedMemberReferences": null (or supplied by an external caller with that property set to null), evaluating evidence?.IsSuccess throws on Count instead of returning a withheld authorization reason. Treat the collection as potentially malformed and fail validation explicitly so unsupported evidence remains visible rather than crashing planning.

AGENTS.md reference: AGENTS.md:L88-L94

Useful? React with 👍 / 👎.