WORK-523
ID:WORK-523Status:pending

Migrate the config-modifier loop and retire seedAxes

Make step 1's generic config-modifier resolution — plus contextModifiers (1b) and staticModifiers (1c) — facets, and delete FacetInput.seedAxes once nothing needs it. This is the last structural migration and the one that removes the migration scaffolding: every after reference resolves to a real facet, and the registry's dependency graph becomes complete rather than partly seeded.

Priority:mediumComplexity:complexMilestone:v0.30.1Source:SPEC-124
claude/spec-124-facet-registry View source

Criteria completion

Criteria completion: 0 of 9 (0%) checked; tracking started on Aug 27, no incremental history yet0%25%50%75%100%Aug 27Sep 6

Tracking started Aug 27 — check back for trends.

Relationships

Implements 1
Related 9
Branches 2
claude/spec-124-facet-registry current pending
claude/transform-package-refactor-7mxi8a donemain done
History 2
  1. 7b91f9a
    Content editedby bjornolofandersson
  2. de0030a
    Created (pending)by bjornolofandersson

Acceptance Criteria

  • modifiers, context-modifiers and static-modifiers are facets; steps 1, 1b and 1c are gone from transformRune
  • valueMap / mapTarget / noBemClass and the present-but-empty (renderWhenEmpty) case all behave unchanged
  • attrModifierNames — used to strip attribute-source modifiers from pass-through output — is carried by the facet resolution rather than a local
  • Every axis previously seeded (media-position, content-place, color-scheme) is supplied by a facet; consumers are unchanged because a facet value already shadows the seed
  • FacetInput.seedAxes, the seeded option on orderFacets, and SEEDED_AXES are deleted
  • {% ref "SPEC-091" /%} config variants still resolve before the facet pass, since they rewrite the config the facets read
  • Class-string order and modifierValues key insertion order are unchanged
  • All 630 pre-existing transform tests pass unmodified, including value-mapping, variants, fields and context-modifiers
  • npm run build, the full repo suite, and refrakt contracts --check pass

Approach

This is the riskiest single migration in the spec: every rune goes through the modifier loop, and its edge cases (value mapping, mapped targets, suppressed BEM classes, present-but-empty values) are subtle. It is scheduled last for exactly that reason — by this point the interface is settled and the remaining facets are proven against it.

Ordering is the main hazard. The modifier facets must run first so their axes are available to everything else, and their BEM classes must land at the front of the class string. Registration order handles both, but verify against a rune that combines config modifiers, context modifiers, static modifiers, a tint and a background.

Watch for the interaction with variants: resolveVariantConfig rewrites config from modifier values before the rest of the transform reads it, so it must stay ahead of the facet pass rather than becoming a facet itself.

Blocked by

  • WORK-519
  • WORK-520
  • WORK-521
  • WORK-522

Blocks

  • WORK-525

References

  • SPEC-124 — facet registry (the spec this work item realizes)
  • SPEC-091 — config variants, resolved ahead of the facet pass
  • SPEC-082 — the typed field-data channel the modifier loop reads