Repository navigation
Conversation
…CB after live attach
…o endpoint authority
…MMS reference syntax
… not first matching row
Stage-main stacked dependency audit 2026-10-23Parent R1A source PR #136 is closed unmerged solely as redundant stacked review tracking. Verified: #136 head 1d3899e is a true ancestor of this OPEN #137 head b47ac16 (behind=0). Original feature branch remains intact; this PR still targets |
Stage→Main stacked Workbench source audit · 2026-10-23GitHub ancestry: CLOSED unmerged PR #127 head This #137 now carries R0 Browser recovery + R1A canonical static Dataset Signals + R1B exact-bound-RCB route. Old PR base |
Historical PR reconciliation / archival — 2026-10-24Disposition: CLOSED AS SUPERSEDED HISTORICAL SOURCE — NOT MERGED, NOT ACCEPTED AS COMPLETE. Original review head preserved: Remaining requirement: exact static DataSet/RCB choice preserved through live Reporting attach, fail closed on mismatches. Canonical open feature owner(s): #129. Cross-PR migration index: #308. All source commits remain accessible through this PR. Port only behavior proven missing in the present mainline, in reviewed and tested small patches with exact-commit CI and external evidence where required. Closed PR is an archival/reconciliation status, not a claim that functionality passed a test. No M3.H Stable binary, tag or checksum is changed. |
Stacked on R1A PR #136 and milestone #129. Do not merge independently into main.
Problem fixed
The Dataset Signals → bound RCB selection could be made from the canonical offline/discovered model, but entering Reports attaches the live report service. That attach rebuilds the live DataSet/RCB inventory and previously reset selection to row 0, so the operator's exact static DataSet choice could silently drift.
R1B behavior
STATIC · <DataSet>indicator before the still-explicit Enable + GI command.Behavioral QA
ied_report_workspace_qanow selects the Dataset Signals route, disconnects/re-attaches the Reports association, verifies the same canonical DataSet + a live-probed selectable RCB are restored, then proceeds to the existing explicit GI test. Success emitsSTATIC_REPORT_ROUTE_RESTORE_PASS.Acceptance: exact-head Qt/C++/Release Hardening green. Real AA1E1F06R4 acceptance remains required for full R1.