Durable reports produced by .github/workflows/daily-dashboard-language-spec-review.md in githubnext/central-agentic-ops.
.github/workflows/daily-dashboard-language-spec-review.md
Daily Dashboard Language Specification Review Reviewed docs/dashboard-language-specification.md against dashboard/report/report.mjs; no GitHub issue created because the only gap found is already covered by built-in page requirements, and custom-view shortcomings do not block deterministic rendering of the observed report surfaces as currently scoped.
Summary The specification contains one actionable renderability gap for custom charts and tables that need deterministic series ordering within grouped outputs. Several realistic dashboard requirements require ordering by a grouped dimension or aggregate after grouping, but the current ordering model and tie-break rule become undefined for non-entity aggregate groups because no canonical entity ID exists at that output grain. Simulated profile checks Backend Engineer: daily run failures by workflow over 30d filtered to rollout-mode: live is representable as a custom chart from runs with temporal x, counted y, and color: workflow. Frontend Developer: open findings table with severity, summ...
Summary The specification is broadly expressive for built-in pages and many custom views, but it has one actionable renderability gap: custom views cannot deterministically express or validate empty and unavailable states at the view level when a profile requirement depends on a link-bearing or status-bearing table/chart over a source that may return no rows or no usable result. The data-state section normatively requires presenters to expose availability, completeness, freshness, provenance, and source identity for every page or view, but the custom-view model does not define what semantic output a presenter must emit for a view whose aggregate channels become absent, whose href channel ...
Summary The custom-page vocabulary cannot deterministically express ranked dashboards that are explicitly required by the review scenarios and by built-in page semantics, because order-by is defined against source fields or encoded aggregate outputs but aggregate outputs have no normative identifier model and no requirement ties row ordering to the aggregated field definitions used in encoding. Affected requirements and sections Section 7.4, DLS-AGG-008 Section 11.2 (order-by) Section 11.3, DLS-VIEW-010 and DLS-VIEW-012 Appendix B, DLS-E006 and DLS-E010 Observed ambiguity The specification requires rankings to disclose the ranked measure, direction, filters, time range, scope, and tie beh...