Review every declared contextModifiers entry across core and plugins, decide whether the pairing is meaningful, and either style it or remove it. The lone KNOWN_MISSING_SELECTORS context entry — Hero's feature → in-feature — is the first casualty: it has no sensible rendering, so the modifier comes out rather than getting CSS.
Tracking started Jun 5 — check back for trends.
contextModifiers entry is inventoried (rune → parent → modifier) with a keep/remove decision recorded.feature: 'in-feature' context modifier is removed from plugins/marketing/src/config.ts..rf-hero--in-feature is dropped from KNOWN_MISSING_SELECTORS; css-coverage passes with no context-modifier carve-outs remaining (or each remaining carve-out has a written justification).Cross-reference the contextModifiers declarations with the styled selectors in packages/lumina/styles/runes/*.css (the composability research already mapped these). Removing a modifier is a config-only change; the engine stops emitting the BEM class automatically.
packages/runes/src/config.ts, plugins/marketing/src/config.ts, plugins/design/src/config.tspackages/lumina/test/css-coverage.test.ts (KNOWN_MISSING_SELECTORS)Completed: 2026-06-05
Branch: claude/v0.19-composability
{ hero→in-hero, feature→in-feature } — keep (styled){ bento-cell→in-bento-cell } — keep (the bleed pattern){ design-context→in-design-context } — keep (design-context composes them){ feature→in-feature } — keep (styled){ hero→in-hero, pricing→in-pricing } — keep (styled){ hero→in-hero, grid→in-grid } — keep (styled){ feature→in-feature } — REMOVE (nonsensical; the lone unstyled carve-out)contextModifiers: { feature: 'in-feature' } from plugins/marketing/src/config.ts..rf-hero--in-feature from KNOWN_MISSING_SELECTORS in css-coverage.test.ts — no context-modifier carve-outs remain; every kept modifier has CSS coverage (css-coverage green).contracts/structures.json, packages/lumina/contracts/structures.json)..rf-hero--in-feature selector.