A theme vocabulary coverage check

A theme that configures no rune cannot promise each rune looks right. It needs to cover the vocabulary instead (ADR-043 decision 5). Lumina's coverage test (packages/lumina/test/css-coverage.test.ts) checks BEM selectors derived from rune configs; it does not check vocabulary values.

claude/post-v0.43-roadmap-mf1ngx View source

Criteria completion

Tracking started Oct 28 — check back for trends.

Relationships

ID:ADR-043Status:proposed

A theme renders a vocabulary; it configures no rune

Date:2026-10-12

ID:ADR-044Status:proposed

Plugin runes speak the vocabulary; novel parts bring token-only structure

Date:2026-10-12

ID:WORK-673Status:done

A vocabulary report per plugin rune and a token-only lint for plugin CSS

Priority:lowComplexity:moderateMilestone:v0.46.0

ID:v0.46.0Status:complete

v0.46.0 — The theme contract

ID:SPEC-166Status:accepted

Value primitives share one contract

claude/post-v0.43-roadmap-mf1ngx current ready

claude/milestone-v0-44-0-ism7ni done main done claude/value-primitives-and-grid ready

Oct 28, 03:15 PM0ec343f
Content editedby bjornolofandersson
Oct 28, 02:54 PMc527aa0
Created (ready)by bjornolofandersson

Acceptance Criteria

A check reports, for every vocabulary value, whether a theme styles it or leaves it to the base stylesheet: each metaType, sentiment, zone layout (bar, definition-list, lead, ladder as they land), section role, media kind and universal-axis value
The vocabulary list is derived from the registries that define it, not restated, so a new value appears in the report without editing the check
It runs for Lumina in the test suite, and its gaps are recorded as known sets that may only shrink, as the selector coverage test does
It is available to third-party themes, through refrakt tooling, as part of a theme's definition of done beside refrakt contracts --check
The theme-authoring docs describe it

References

ADR-043: decision 5.
ADR-044: the plugin half of the same coverage, WORK-673.