Description
Integration sync detail, Per-user detail and Connector health fragment the same entity into repeated sparse rows, leaving sibling measurements blank and making comparison difficult. Filed by TSO-0172 (comprehensive live dashboard audit); outside the approved loop33 implementation set.
Acceptance Criteria
- #1 Each entity has one coherent row for its related measurements at a stated evaluation time.
- #2 Missing measurements remain explicitly unknown and are not silently filled as healthy zero.
- #3 Synthetic multi-entity/multi-measure frames prove correct joins without cross-tenant or cross-entity mixing.
Definition of Done
- #1 just check passes (the full gate; it is what CI enforces)
- #2 just gen leaves no diff (only if a generated artifact’s inputs changed)
- #3 just –fmt –check passes and every new recipe has a # doc comment and a [group(…)]
Implementation Notes
Additional exact audit binding: Subnet routes — advertised vs enabled renders blank Enabled cells despite populated query results. Preserve this as a per-route join/field-render discrepancy, with cause unresolved; a populated enabled/disabled route fixture must show both states in the same row. Backend presence alone does not prove that every route has an enabled counterpart.