ID:WORK-107Status:done
Migrate community package runes to inline rune identifiers
Phase 2b of ADR-005. Update all ~65 community package rune transforms across 8 packages to use the new inline { rune: 'name' } signature for createComponentRenderable. Same mechanical change as WORK-106 but across community packages.
Depends on WORK-105 (dual-signature support) being complete.
Priority:highComplexity:simpleMilestone:v1.0.0Source:ADR-005
Packages
| Package | Directory | Approx. runes |
|---|---|---|
| marketing | runes/marketing/ | 9 (hero, cta, bento, feature, steps, pricing, testimonial, comparison, storyboard) |
| docs | runes/docs/ | 3 (api, symbol, changelog) |
| design | runes/design/ | 7 (swatch, palette, typography, spacing, preview, mockup, design-context) |
| learning | runes/learning/ | 2 (howto, recipe) |
| storytelling | runes/storytelling/ | 7 (character, realm, faction, lore, plot, bond, storyboard) |
| business | runes/business/ | 3 (cast, organization, timeline) |
| places | runes/places/ | 3 (event, map, itinerary) |
| media | runes/media/ | 3 (music-playlist, music-recording, + track) |
| plan | runes/plan/ | ~8 (spec, work, bug, decision, milestone, etc.) |
Acceptance Criteria
- Every
createComponentRenderable(schema.X, { ... })call inrunes/*/src/tags/is replaced with inline form - Runes with
schemaOrgTypepass it in the new inline object - No community package file imports from any
schema/directory or registry for Type purposes - Each package's local registry/schema imports for Type creation are removed
refrakt inspect <rune> --type=all --jsonoutput is identical before and after for each rune- All existing tests pass
Approach
Same mechanical approach as WORK-106. For each community package:
- Identify all tag files that call
createComponentRenderable - Replace
schema.Xargument with inline{ rune: 'name' }form - Remove schema/registry imports
- Verify output is identical
Can be done one package at a time. Order doesn't matter.
References
- Replace the useSchema / Type class system with plain rune identifiers (Phase 2)
- Add dual-signature support to createComponentRenderable and update RuneDescriptor (dependency — dual-signature support)
Relationships
Related
ID:WORK-106Status:done5/5
Migrate core runes to inline rune identifiers
Priority:highComplexity:simpleMilestone:v1.0.0
ID:WORK-105Status:done6/6
Add dual-signature support to createComponentRenderable and update RuneDescriptor
Priority:highComplexity:moderateMilestone:v1.0.0
ID:WORK-109Status:done11/11
Remove Type system — delete schema classes, registries, and old signature
Priority:mediumComplexity:moderateMilestone:v1.0.0
History
- 59ded4aContent edited
- f262d7bsource+ADR-005
- f0a845a
- ☑ Every `createComponentRenderable(schema.X, { ... })` call in `runes/*/src/tags/` is replaced with inline form
- ☑ Runes with `schemaOrgType` pass it in the new inline object
- ☑ No community package file imports from any `schema/` directory or registry for Type purposes
- +3 more criteria
- c87b1c2statusready→done
- 721addbCreated (ready, high, simple, runes, types, packages, v1.0.0)