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.

main View source

Criteria completion

Relationships

ID:ADR-005Status:accepted

Replace the useSchema / Type class system with plain rune identifiers

Date:2026-04-02

ID:WORK-105Status:done

Add dual-signature support to createComponentRenderable and update RuneDescriptor

Priority:highComplexity:moderateMilestone:v1.0.0

ID:WORK-109Status:done

Remove Type system — delete schema classes, registries, and old signature

Priority:mediumComplexity:moderateMilestone:v1.0.0

main current done

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

Apr 21, 01:46 PMe900a90
Created (done)by bjornolofandersson
Apr 10, 06:58 PMf262d7b
Content editedby Claude
Apr 3, 05:40 PMf0a845a
- ☑ 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
- ☑ Each package's local registry/schema imports for Type creation are removed
- ☑ `refrakt inspect <rune> --type=all --json` output is identical before and after for each rune
- ☑ All existing tests pass
by Claude
Apr 2, 05:57 PMc87b1c2
statusready→done
by Claude
Apr 2, 05:30 PM721addb
Created (ready)by Claude
Break ADR-005 into work items (WORK-105 through WORK-109)

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 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
Each package's local registry/schema imports for Type creation are removed
refrakt inspect <rune> --type=all --json output 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.X argument 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

ADR-005 (Phase 2)
WORK-105 (dependency — dual-signature support)