WORK-115
ID:WORK-115Status:ready

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.

Priority:mediumComplexity:moderateMilestone:v1.0.0Source:SPEC-033
changeset-release/main View source

Criteria completion

No incremental history — criteria tracking started on Apr 19.

Branches 3
History 4
  1. f2b3512
    Content editedby Claude
    Add {ID}-{slug}.md filename convention + migrate filenames subcommand
  2. 59ded4a
    Content editedby Claude
    Implement SPEC-037 plan package hardening: all 7 work items
  3. f262d7b
    Content editedby Claude
    Backfill source attributes on all 123 work items
  4. 41d5c52
    Created (ready)by Claude
    Accept SPEC-033 and break down into work items WORK-110–116

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

  1. For each rune, capture the current refrakt inspect output as a baseline
  2. Replace the postTransform with the equivalent declarative config
  3. Compare inspect output to confirm identical HTML
  4. 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)