WORK-349
Setting up your dashboard 0 entities found · 8/32 branches scanned
ID:WORK-349Status:done

Aggregate chart layout

Close the one gap between "we have the data" and "we can chart it." Plan entities are already registered in the main site's registry, so {% aggregate type="work" group="status" %} returns real counts today — but aggregate can only render an inline integer or a body-zoned template, not a chart. Add a layout="chart" mode that renders the grouped counts as an SVG, reusing the rf-chart renderer from WORK-333. This is the SPEC-076 "chart layout" future extension, and the clean "data rune feeds viz rune" composition.

Priority:mediumComplexity:moderateMilestone:v0.19.0Source:SPEC-076
main View source

Criteria completion

Criteria completion: 6 of 6 (100%) checked; tracking started on Jun 5, no incremental history yet0%25%50%75%100%Jun 5Jun 15

Tracking started Jun 5 — check back for trends.

Relationships

Related 3
Branches 4
main current done
changeset-release/main readyclaude/v0.19.0-rollups donemain doneclaude/v0.19-milestone-planning ready

Acceptance Criteria

  • aggregate accepts layout="chart" (alongside the existing inline / body-zoned forms); with a group, it charts one bar/point per group keyed by the group label, value = group count (or value/percent when supplied).
  • Output reuses the WORK-333 chart pipeline: emit the same rf-chart element + data-name="data" table source, so the SVG renderer and no-JS table fallback work unchanged.
  • Chart type (bar default, line) and a title are configurable, consistent with the chart rune's attributes.
  • Domain-aware group ordering (SPEC-072) is honored on the axis, so e.g. status groups read in lifecycle order.
  • Empty query renders the empty fallback, not a broken chart.
  • Tests cover: grouped count chart, value/percent chart, ordering, and the empty state.

Approach

In aggregate-resolve.ts, add a chart branch that builds a group→count table and hands it to the chart construction path (the rf-chart element + caption + data-name="data" table) rather than the span/template path. Keep the table as the canonical source so the existing <rf-chart> web component upgrades it.

References

  • packages/runes/src/tags/aggregate.ts, packages/runes/src/aggregate-resolve.ts
  • Chart renderer: packages/runes/src/tags/chart.ts, packages/behaviors/src/elements/chart.ts (WORK-333)
  • SPEC-076 (chart layout future extension)

Resolution

Completed: 2026-06-08

Branch: claude/v0.19.0-rollups

What was done

  • packages/runes/src/tags/aggregate.ts: added layout, chart-type, chart-title attributes + metas.
  • packages/runes/src/aggregate-resolve.ts: added a chart branch in resolveOne + a buildChart() that emits the chart rune's final form — <rf-chart class="rf-chart" data-rune="chart" data-type=…> wrapping a <table data-name="data"> (caption + thead + one row per group). Labels humanized; a value sub-filter adds a Value series. Axis order reuses the same groupEntities→sortGroups→limit path (domain-aware). Empty query → the rf-aggregate__empty fallback.
  • packages/runes/test/aggregate.test.ts: 5 chart tests (grouped count chart, chart-type/title passthrough, value series, domain ordering, empty fallback).
  • site/content/runes/aggregate.md: a "Chart layout" section with a live preview (verified rendering <rf-chart> end-to-end in the site build).

Notes

  • Reuses the WORK-333 rf-chart pipeline verbatim (SVG enhancement + no-JS table fallback), so no chart-renderer changes here — theming/sentiment is WORK-353.
  • "value/percent": a value sub-filter adds the achieved-count series; percent-as-a-series isn't exposed (would be the heading-as-columns body form, a later refinement).
  • The contract regen committed alongside is pre-existing data-layout drift, unrelated to this work.