R1B — Static DataSet to exact RCB reporting workflow #134

Depends on R1A #131 (PR #130), parent #129. Do not implement or merge this ahead of validated Browser recovery #127.

R1B operator workflow

• Select an exact canonical static DataSet from Signal Catalog (Open SCL or Discovery) and show its matching BRCB/URCB inventory and binding status; never silently choose a different DataSet.
• Show exact ordered DataSet members with FC/MMS reference and resolved signal value/quality/timestamp where available.
• Explicit operator action connects report association and enables the selected static RCB; read-back verifies configuration, and GI is explicit/supported.
• Static DataSet reporting runs report-only; no cyclic MMS polling fallback or mixed dynamic ownership.
• Expose RptID, DatSet, ConfRev, BufTm, IntgPd, TrgOps, OptFlds, RptEna, reservation/owner, report count, entry/sequence continuity, quality/timestamp provenance, and actionable errors.
• Separate dynamic DataSet authoring is labelled advanced and guarded; never automatically create or mutate a static DataSet.
• Runtime and GUI QA verifies both Open SCL and Discovery converge after canonical model creation; synthetic fixture and real device AA1E1F06R4 evidence required.
• Exact-head Qt, C++, sanitizer/security, release and portable Windows artifact pass; no screenshot-only acceptance.

Scope: GUI orchestration and canonical projection first. Any engine defect must be addressed in an isolated reviewed PR (e.g. BIT STRING bounds #132/#133), never hidden by fallback or CI suppression.

Dependency routing (R1A consolidation 2026-10-23)

Issue #131 was consolidated into OPEN parent #129; all remaining R1A requirements and prior QA evidence are preserved there. Treat references to #131 above as historical context, not a closed/accepted prerequisite. R1B gates in this issue #134 remain OPEN, contingent on the relevant R1A acceptance in #129.