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.
Tracking started Nov 2 — check back for trends.
rf-badge to field values; CHIP_METATYPES is removed[data-meta-type="status"], "category" and "tag", and Lumina's skin follows, in the same change, so no value loses its pill{% badge %} keeps rf-badge, and the base rule covers it through its default data-meta-type="tag"Completed: 2026-11-02
Branch: claude/milestone-v0-44-0-ism7ni
packages/transform/src/engine.ts: CHIP_METATYPES, fieldRendersAsChip, buildChip and buildPlainValue are replaced by buildValue (data-meta-type plus mapped sentiment, no class). renderBlockValue and the definition-list use it, so a <dd> always holds the value element. types.ts docs updated.dimensions/metadata.css: the pill's white-space: nowrap is keyed on .rf-badge and [data-meta-type=status|category|tag].runes/badge.css: the pill rule takes the same selector list.dimensions/metadata.css: a non-pill def-list value inherits its row's size, and an id/code row sets monospace.runes/work.css, bug.css: the assignee prefix is retargeted to dd > [data-meta-type], and the complexity dots set in tabular numerals.skin.css: the pill selector list.engine-blocks.test.ts is rewritten for classless values, and the composed snapshots (character, lore, realm, faction, section header grammar) are updated.dimensions.md and blocks-and-layout.md; SPEC-145 D28's open question and attribute table..changeset/engine-no-rf-badge.md.rf-badge (36: rune pages, plan, storytelling, theme showcase pages, docs) was full-page screenshotted before and after, light and dark. All 72 are pixel-identical after the def-list size and font follow-ups.StructureEntry in a first-party config has a pill type, so none newly became a pill.