V0.41.0
Name:v0.41.0Status:complete

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.

Milestone burndown: 0 open work items remaining; peak 1, started Oct 801Oct 8Oct 11
Open work items Ideal burndown
Progress 6/6 work items

Relationships

Related 16

Work Items

Done 6
WORK-632 main
A by-attribute schema table's rows must cover the attribute's matches
SPEC-145 D27 (c). validateSchemaTable (packages/runes/src/lib/schema-table.ts) checks two things: that by names a declared attribute, and that a fallback exists. It never compares rows keys with that attribute's matches. So a misspelt row (podcasts:) or a newly added enum value silently selects the fallback, and {% playlist type="podcast" %} would publish MusicAlbum.D15 already requires an exact two-way correspondence for template variants. The schema by gets the same check. It needs no composition, and it applies to every hand-written table today (playlist, track, organization and others).
medium simple
5/5 criteria
WORK-633 main
A plugin ships composed runes from a declared rune directory
SPEC-153 implementation note 3, the plugin side. In v0.40.0 a composed definition reached the pipeline only as a string passed to defineComposedRune. A plugin now declares runeDir (package-relative, resolved the way fileRoots resolves, D2). Every <rune>.md in it is loaded as a composed rune.Decisions:
high complex
8/8 criteria
WORK-634 main
A project defines its own composed runes in runes.dir
SPEC-153 implementation note 4, the project side, and the step that opens composition to users. A project declares runes.dir in refrakt.config.json, following contentDir's shape, with a recommended default of runes (D4). The loader discovers every <rune>.md in it.Decisions:
high complex
7/7 criteria
WORK-635 main
lore as a composed rune
SPEC-147 lists lore as the simplest storytelling rune. It has a title, a body, an Article schema row (title → headline, category → articleSection) and a registered entity. It follows the pattern WORK-624 and WORK-625 set:
medium simple
5/5 criteria
WORK-636 main
realm and faction as composed runes
SPEC-147: realm (Place) and faction (Organization) share character's shape, sections plus a preamble, and each has a -section child rune that composition removes. Their media split maps to {% mediatext %}. Both follow WORK-625's pattern:
medium moderate
7/7 criteria
WORK-637 main
The authoring guide for composed runes
Composition ships to users in this milestone, and SPEC-153 D9 makes the definition file the user-facing authoring surface. Today the only documentation is a PluginRune note in rune-authoring/authoring-overview.md. Add a page under site/content/extend/rune-authoring/ written from SPEC-145's "template vocabulary, in one place" table. The guide is the spine of that table rather than a summary of it.It covers:
high moderate
6/6 criteria