Migrate runes that have multiple groups, context-dependent group logic, or light custom processing. These need more careful mapping but don't require the custom escape hatch.
No incremental history — criteria tracking started on Apr 17.
| Rune | Location | Challenge | Content model |
|---|---|---|---|
| nav | packages/runes/src/tags/nav.ts | Multiple heading-based sections with nested structure | sections |
| pricing | runes/marketing/src/tags/pricing.ts | Multi-section layout with header/features/footer split | sections |
| map | runes/places/src/tags/map.ts | Sections with location extraction from child content | sections |
| storyboard | runes/storytelling/src/tags/storyboard.ts | Image-triggered panel accumulator with caption grouping | custom |
nav rewritten using createContentModelSchema with sections content modelpricing rewritten using createContentModelSchema with sections content modelmap rewritten using createContentModelSchema with sections content modelstoryboard rewritten using createContentModelSchema with custom content modelrefrakt inspect <rune> --type=all output is identical before and after for each runenav: Map the heading-level group splits to a sections model. Heading content becomes section names; nested content follows naturally.pricing: Header/body/footer groups map to named sections. Feature list extraction stays in the transform function.map: Section-based content with location metadata extraction in transform.storyboard: The image-triggered panel accumulator is genuinely stateful — use custom content model with the panel grouping logic in processChildren.