Skip to content

R1B: preserve exact Static Reporting route through live report attach - #137

Draft
masarray wants to merge 27 commits into
feat/browser-dataset-signals-r1afrom
feat/static-report-route-r1b
Draft

masarray wants to merge 27 commits into
feat/browser-dataset-signals-r1afrom
feat/static-report-route-r1b

Conversation

@masarray

@masarray masarray commented Sep 27, 2026 •

Copy link
Copy Markdown
Owner

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

  • Persist the chosen canonical static DataSet reference as a report route.
  • On live report-service attach/re-attach, restore only an RCB whose live probe succeeded and whose DatSet binding matches that exact canonical reference; when several RCBs bind the same DataSet, use the existing pool selector's best selectable/preferred candidate rather than first-row order.
  • If there is no verified live bound RCB, leave reporting unselected/disabled and surface a diagnostic instead of choosing another RCB.
  • Selecting another DataSet or manually choosing another RCB clears the armed route, so user intent always wins.
  • UI now calls the action Static Reporting… and shows a compact STATIC · <DataSet> indicator before the still-explicit Enable + GI command.
  • No automatic GI, no automatic RCB enable, no DatSet write, and no cyclic MMS polling fallback is introduced.

Behavioral QA

ied_report_workspace_qa now 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 emits STATIC_REPORT_ROUTE_RESTORE_PASS.

Acceptance: exact-head Qt/C++/Release Hardening green. Real AA1E1F06R4 acceptance remains required for full R1.

  • Rendered Browser QA can now save and upload an exact 1024px Browser screenshot from the same functional route test; this replaces relying on the Simulator-tab screenshot for Browser UX review.
  • Qt/Release workflow concurrency now deduplicates push + PR validation by head branch so stale duplicate jobs no longer consume runners.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant