ID:ADR-043Status:proposed
A theme renders a vocabulary; it configures no rune
Date:2026-10-12
Name:v0.46.0Status:complete
v0.46.0 — The theme contract
A theme renders a vocabulary and configures no rune (ADR-043); a plugin rune speaks the same vocabulary, and only its novel parts bring their own structure, in tokens (ADR-044). Both decisions were accepted on 2026-10-28. This milestone builds what makes them checkable.
Progress 4/4 work items
Relationships
Related 14
ID:ADR-044Status:proposed
Plugin runes speak the vocabulary; novel parts bring token-only structure
Date:2026-10-12
ID:WORK-670Status:done
All of metaFields is identity
Priority:mediumComplexity:simpleMilestone:v0.46.0
ID:WORK-671Status:done
The engine stops adding rf-badge to field values
Priority:mediumComplexity:moderateMilestone:v0.46.0
ID:WORK-672Status:done
A theme vocabulary coverage check
Priority:mediumComplexity:moderateMilestone:v0.46.0
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:ADR-047Status:proposed
A rune may take editorial runes as a narrative field
Date:2026-10-23
ID:WORK-674Status:done
A composition's narrative field is checked at definition load
Priority:lowComplexity:simpleMilestone:v0.46.0
ID:WORK-675Status:done
The content-boundaries guide documents the narrative field
Priority:lowComplexity:simpleMilestone:v0.46.0
ID:WORK-669Status:done
A theme override aimed at a composed rune is reported and dropped
Priority:highComplexity:simpleMilestone:v0.44.0
ID:SPEC-166Status:draft
Value primitives share one contract
ID:SPEC-162Status:draft
Amount and tally primitives, and budget as a composition
ID:SPEC-165Status:draft
A color primitive, inline compositions, and the design runes
ID:SPEC-177Status:draft
Theme and site templates for composed runes
Work Items
Done 4
WORK-672 main
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.
5/5 criteria
WORK-673 main
A vocabulary report per plugin rune and a token-only lint for plugin CSS ADR-044 lets a plugin rune bring its own structure CSS only for genuinely novel parts, written only in theme tokens. Two checks make the tiers checkable rather than advice. Neither exists.
5/5 criteria
WORK-674 main
A composition's narrative field is checked at definition load ADR-047 lets a rune declare one narrative field that accepts only the editorial runes textblock and mediatext, and says the field is never published as structured data. As amended, the field is inferred from its match, and both rules are checked.
6/6 criteria
WORK-675 main
The content-boundaries guide documents the narrative field The "Content boundaries" section of site/content/extend/rune-authoring/patterns.md puts "Story, editorial, famous quotes" outside recipe. ADR-047 adds a case: a rune may declare one narrative field that takes {% textblock %} and {% mediatext %}, so a template can place the story between the rune's parts. A site's own composed rune can declare one today.
5/5 criteria