v0.46.0 — The theme contract

SPEC-158 D3 made metaFields.*.metaType identity and left label, sentimentMap and transform overridable, so a theme had something to change. ADR-043 decision 2 reads all three as claims about content: a label is copy, a sentiment map says what the content means, and transform names a kind of formatting whose style is now formats (SPEC-166 D6). So metaFields becomes identity as a whole, for native runes too.

CHIP_METATYPES (packages/transform/src/engine.ts) gives status, category and tag values the rf-badge class, so the engine decides that those values look like pills. Under ADR-043 decision 3 the engine emits meaning, not shape: the pill comes from the base stylesheet, keyed on data-meta-type, and a theme restyles it like any other rule.

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.

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.

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.

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.