Land the SPEC-083 seam. Move chart onto the two-layer boundary: the data becomes a real <table> in the transform, and the rendering moves into an rf-chart web component that draws svg, full stop. No provider attribute, no registry, no selection — that abstraction is WORK-334, gated on a real second renderer. Chart stays in core; no new package.
Tracking started Jun 3 — check back for trends.
Today chart.ts parses the authored table, JSON.stringifys it into a <meta>, discards the source table, and the engine postTransform re-parses that JSON to hand-build a static <svg> baked into coreConfig. See SPEC-083 for the full critique.
<table data-name="data"> (the no-JS / screen-reader fallback and the data source) — no JSON-in-<meta>.type / title / stacked are modifiers surfaced as data-* for the client; chart emits no field-metas. (No provider attribute.)postTransform (the inline SVG builder) is removed; the rune renders as rf-chart wrapping the data table.rf-chart web component (in @refrakt-md/behaviors, mirroring sandbox / diagram) parses the <table> once and draws the svg. The <table> stays in the DOM (visually-hidden) after a successful render for screen readers.<table> is the single source of truth — rf-chart parses it in place (thead th → headers, tbody cells → rows); no <template> / JSON copy. Cells are read dataset.value ?? textContent (the data-value hook is reserved for future display-formatting; not emitted now). See SPEC-083 "Data sourcing".renderSvg(data, container, opts) function (so a future provider registry is a lift-and-shift, not a rewrite) — but no registry / ChartProvider contract is built here.<svg>).chart.ts to emit <table data-name="data"> + the modifiers; drop extractTableData → JSON meta and the postTransform.rf-chart to packages/behaviors/src/elements/ (register in registerElements()); port the existing axis/bar/scale code into a standalone renderSvg(...) the element calls.packages/lumina/styles/runes/chart.css.data-field meta problem as a side effect (no field-metas once data is a table + knobs are modifiers).data-provider / per-provider packages are all WORK-334, deferred until a concrete second renderer exists.Completed: 2026-06-03
Branch: claude/rune-contract-hardening
Landed the SPEC-083 seam — chart stays in core, svg-only, no provider layer.
<table> as the single source of truth (data-name="data"), injects the title as a <caption>, and emits the rf-chart custom element. Dropped extractTableData → JSON-in-meta entirely.type / stacked are bag-only modifiers (→ data-type / data-stacked) the web component reads.dataset.value ?? textContent), draws the svg via a standalone renderSvg(data, container, opts) (ported from the old postTransform, bar + line + legend), and sets data-rendered so CSS visually-hides the table while keeping it for screen readers. Registered in elements/index.ts..rf-chart[data-rendered]; the svg/title/legend classes are unchanged (now created client-side).title became the table <caption> (semantic, accessible, and the web component's title source) rather than a modifier — only type/stacked are modifiers.renderSvg is the standalone seam it will lift.