Migrate community package postTransform uses to declarative config

With WORK-110 through WORK-114 complete, convert the 5 postTransform uses identified in SPEC-033 to their declarative equivalents. Validate identical HTML output before and after each migration.

main View source

Criteria completion

Tracking started Apr 21 — check back for trends.

Relationships

ID:SPEC-033Status:accepted

Structure Slots and Declarative Flexibility

ID:WORK-110Status:done

Add value mapping to modifier config

Priority:highComplexity:simpleMilestone:v1.0.0

ID:WORK-113Status:done

Add repeated element generation to structure entries

Priority:mediumComplexity:moderateMilestone:v1.0.0

main current ready

changeset-release/main ready claude/file-naming-convention-LJdwR ready main ready claude/align-sidenav-styling-4MuxV ready

Acceptance Criteria

Beat rune (runes/storytelling/src/config.ts) — postTransform replaced with valueMap/mapTarget on the status modifier
ComparisonRow rune (runes/marketing/src/config.ts) — postTransform replaced with valueMap/mapTarget
Testimonial rune (runes/marketing/src/config.ts) — postTransform replaced with repeat on structure entry for star ratings
refrakt inspect output is identical before and after for each migrated rune
All existing tests pass
CSS coverage tests pass (no selector regressions)
The 4 remaining postTransform uses (genuinely complex cases) are untouched

Approach

For each rune, capture the current refrakt inspect output as a baseline
Replace the postTransform with the equivalent declarative config
Compare inspect output to confirm identical HTML
Run full test suite after each migration

References

SPEC-033 (Validation section)
WORK-110 (value mapping — enables Beat, ComparisonRow migration)
WORK-113 (repeated elements — enables Testimonial migration)