[masarray]

Baseline

• Native Qt Workbench only; builds on merged M2H PR M2H: visible contextual q/t evidence for native Data Model and DataSets #171, main 9a780133157db207314ce5256bde446de761b778.
• Prior screenshot CI captured only overview Data Model/DataSets, not selected q/t, leaving a visual acceptance blind spot.

Implementation

• Add opt-in --qa-browser-evidence-output DIR only for CI/QA, requiring a real opened SCL fixture. It resolves q/t DA directly from the authoritative DataSet and canonical MMS item index (no shadow semantic model, parser, or new polling).
• Create typed Quality and UTC evidence using existing decodeEngineeringEvidence and inject samples only into MmsLiveTreeModel in this explicitly flagged synthetic QA mode.
• Render and assert actual visible typed evidence in each of Data Model (inline DO/DA selection) and DataSets (shared user-click DA selection path) and save four screenshots:
  data-model-quality.png, data-model-timestamp.png, datasets-quality.png, datasets-timestamp.png.
• Reject malformed 13-bit Quality as Unknown, verify stale selection clears when DataSet changes, and reject identical screenshots from distinct chosen states.
• Reuse one canonical DA selection function for DataSets direct and lazily expanded member rows. Add only QML objectNames for robust component-scoped GUI QA.
• Extend existing Browser source contract and one existing native Qt workflow, without spawning new CI runners.

Acceptance

• Exact-head Browser convergence, QML smoke, 60k-node large-model regression, malformed/negative data, MMS & reporting, multi-IED, screenshot upload and CI routing must pass.
• Review real screenshot artifacts; do not claim IEDScout pixel parity or real physical-IED interoperability from synthetic fixture screenshots.
• Do not merge without exact-head completed CI and review.

No firmware, PTP/SMV, Studio release/installer, legacy web app, protocol parsing or q/t semantic changes.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e166d72aba

ℹ️ 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]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-14T23:43:14.183488Z	e166d72	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[masarray]

Historical PR reconciliation / archival — 2026-10-24

Disposition: CLOSE AS SUPERSEDED OLD SOURCE, NOT MERGED, AND NOT A FEATURE ACCEPTANCE PASS. Verified historical head: 3c11cd3a132516930409cac18c556ce5dad4b69c. This source diverges substantially from the current integrated main (M3.H Process Bus tested baseline already merged through #299).

The distinct acceptance remains: selected Quality/TimeQuality visual QA screenshots and negative cases. Canonical engineering owner: #128; migration index #308.

All commits and review notes remain reachable from this closed PR. A new narrowly scoped PR must branch from current main, first identify genuinely missing behavior and then pass targeted Qt/MMS/schema/GUI tests. Do not bulk-merge the historical branch, silently lose unknown MMS type safety, or claim physical IED acceptance from old CI. No M3.H Stable asset is modified by this closure.