fix: bind Signal Selection one-to-one to static DataSet members

[masarray]

Field evidence

Real Siemens CID validation on ARSAS 147c664... improved from 0/58 to 5/58 represented static members, proving offline recovery runs but resolved members still lose their protocol identity. The same diagnostic also exposed a startup SingleOrDefault() exception in the first-run launcher.

Root cause

ARIEC mandatory inventory was descriptor-centric: 58 static FCDA/FCD members produced 68 semantic descriptors. ARIEC PR #78 now makes the inventory member-centric and preserves exactly one descriptor per (DataSetReference, MemberIndex), keeping the static member identity separate from any resolved runtime primary leaf.

ARSAS changes

• pin ARIEC PR Strengthen release trust and download conversion #78 merge 761fa0df9ca84fbe15352d2670f03fddbe8784ba
• restore authoritative DataSet identity again at content-render time as a defensive post-construction guard
• keep recovery idempotent and selection-neutral
• remove the decorative first-run Border synchronously during Loaded before the queued legacy SingleOrDefault() launcher discovery executes
• add regression contracts for the new engine pin, post-construction DataSet authority, and startup tint ordering

Expected Siemens CID result

• 2 static DataSets
• 58 static members
• 58/58 represented
• Analog 22/22
• Digital 36/36
• 0 missing static members
• no startup Sequence contains more than one element diagnostic

Physical CID validation remains required after merge.

[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.