ID:SPEC-153Status:implemented
Delivering composed runes
Name:v0.41.0Status:planning
v0.41.0 — Composed runes you can ship
v0.40.0 built composition and proved it on bond and character. Nobody outside the repo can use it yet: a definition reaches the pipeline only as a string passed to defineComposedRune. This milestone closes that gap. A plugin ships definitions from a declared directory, a project writes its own in runes.dir, and the authoring guide makes it a documented feature (SPEC-153, SPEC-145).
It also takes the storytelling replacement (SPEC-147) from two runes to five, leaving only the two that need new primitives.
Progress 1/1 work items
Relationships
Related 16
ID:SPEC-145Status:accepted
Composed runes
ID:SPEC-147Status:draft
Replacing the storytelling plugin with composed runes
ID:WORK-631Status:done
Content no content-model field matches is reported, not silently dropped
Priority:highComplexity:moderateMilestone:v0.41.0
ID:WORK-632Status:done
A by-attribute schema table's rows must cover the attribute's matches
Priority:mediumComplexity:simpleMilestone:v0.41.0
ID:WORK-633Status:done
A plugin ships composed runes from a declared rune directory
Priority:highComplexity:complexMilestone:v0.41.0
ID:WORK-634Status:done
A project defines its own composed runes in runes.dir
Priority:highComplexity:complexMilestone:v0.41.0
ID:WORK-635Status:done
lore as a composed rune
Priority:mediumComplexity:simpleMilestone:v0.41.0
ID:WORK-636Status:done
realm and faction as composed runes
Priority:mediumComplexity:moderateMilestone:v0.41.0
ID:WORK-637Status:done
The authoring guide for composed runes
Priority:highComplexity:moderateMilestone:v0.41.0
ID:WORK-625Status:done
Slice 2 — character as a composed rune, against the SEO baseline
Priority:highComplexity:complexMilestone:v0.40.0
ID:BUG-033Status:reported
playlist and track publish byArtist and duration on types that do not define them
Severity:minor
ID:BUG-034Status:confirmed
Injected design tokens never reach the sandbox iframe
Severity:major
ID:WORK-629Status:draft
Check the SEO baseline's types and properties against schema.org in CI
Priority:lowComplexity:simple
ID:SPEC-156Status:draft
The ladder and row arrangement primitives
ID:SPEC-159Status:draft
Chrome as intent, and the shared surface cascade
History 1
fad3cedCreated (planning)
Work Items
Done 1
WORK-638 main
Plan runes keep the content their content models drop, then content-unmatched becomes an error WORK-631 added content-unmatched: validation reports an authored node that no content-model field matches, because the transform drops it. It shipped as a warning because the measurement found that four shipped runes drop real content today, all in the plan plugin. The plan site renders each entity through its rune ({% expand %}), so the loss reaches plan.refrakt.md.Measured over this repo's plan/ directory (907 files), as of WORK-631:
5/5 criteria