WORK-669
ID:WORK-669Status:ready

A theme override aimed at a composed rune is reported and dropped

ADR-042 makes a composed rune's config its definition's: a theme cannot know which definition it faces, so an override of a composed rune's blocks or metaFields is a guess that silently resolves to nothing. Nothing enforces this yet. mergeThemeConfig and mergeRuneConfig (packages/transform/src/merge.ts) guard the identity fields on every rune, and nothing else, so a theme's runes: entry keyed to a composed rune's type name applies.

v0.44.0 adds the first composed runes a theme could try to override (hero, cta, testimonial), so the guard lands with them.

Priority:highComplexity:simpleMilestone:v0.44.0Source:ADR-042
claude/post-v0.43-roadmap-mf1ngx View source

Criteria completion

Criteria completion: 0 of 5 (0%) checked; tracking started on Oct 28, no incremental history yet0%25%50%75%100%Oct 28Oct 28

Tracking started Oct 28 — check back for trends.

Relationships

Implements 1
Related 1
History 1
  1. c527aa0
    Created (ready)by bjornolofandersson

Acceptance Criteria

  • A theme override keyed to a rune whose config came from composedRuneConfig is reported, naming the theme, the rune and the path, and dropped whole
  • It is reported through the same sink and once-per-path rule as identity violations
  • Native runes' overrides are unaffected: identity fields stay guarded and the rest stays overridable
  • A test pins that an override of a composed rune's blocks is reported and dropped, and that Lumina's config trips nothing
  • The theme-authoring docs say a composed rune's config cannot be overridden, and point to ADR-042 and to template replacement (ADR-045) as the route a theme has

Approach

assembleThemeConfig already carries provenance for plugin runes (packages/transform/src/assemble.ts). Composed runes need the same marker, so the merge can tell a composed config from a native one without inspecting its shape.

References

  • ADR-042: Decision 1, and Implementation.