Description
SKT-0011 scenarios G2-G5 pushed and snapshot-rendered two generated dashboards only after an undocumented gcx setup. The path produced dashboard PNGs rather than a panel-by-panel rendered/empty inventory, generated resources had no explicit datasource references despite multiple same-type datasources, no native-histogram panel could be identified, and the target folder had to exist before generation.
Acceptance Criteria
- #1 Dashboard generation or push creates its required folder on a bare stack
- #2 Every generated panel resolves an explicit or deterministic datasource when multiple same-type datasources exist
- #3 The verification path enumerates every panel as rendered, empty, or errored and reports its query
- #4 Empty panels are classified as emission gap, query defect, or missing datasource
- #5 At least one native-histogram panel is generated and its live render is verified
Definition of Done
- #1 just check </dev/null (fmt-check, lint, gen-check, env-check, docs-check, test, race, hygiene, ui-check, compose-check, helm-test, lab-check, signal-fidelity)
- #2 just gen </dev/null (only if a blueprint field, construct/workload config struct, or a skill under plugins/synthkit/skills/ changed)
- #3 just dump </dev/null — inventory diffed against signals/
Implementation Plan
Lane D makes generated dashboards folder- and datasource-complete with panel inventory; root pushes, snapshots, inspects, and classifies live panels.
Implementation Notes
2026-08-30 closeout: one generated folder and 15 dashboards validated, dry-ran, and pushed with explicit datasource mappings. The verifier produced 1,351 query observations with zero empty ref IDs and zero duplicate keys. A native-histogram quantile returned data and panel 798 rendered p50/p95/p99 lines.
Final Summary
Generated dashboards are folder-complete, datasource-explicit, panel-verifiable, and live-proven for a native histogram.