ID:SPEC-145Status:accepted
Composed runes
Name:v0.39.0Status:complete
v0.39.0 — Declarations, part two
v0.38.0 deleted what was provably inert and made two declarations reach the reader and the runtime. This milestone continues on the same line, one level up: the remaining places where a rune's behaviour is written as code but is really data, plus the one place where the two schema resolvers' disagreement already publishes wrong structured data.
These are also the self-contained foundations of the composed-runes work (SPEC-145, SPEC-153, SPEC-156). Each one is valuable on its own and does not depend on composition landing. Composition itself is deliberately not in this milestone.
Not enough history yet — burndown needs at least one completed day of activity.
Progress 0/1 work items
Relationships
Related 23
ID:SPEC-153Status:shipped
Delivering composed runes
ID:SPEC-156Status:draft
The ladder and row arrangement primitives
ID:SPEC-146Status:shipped
Name resolution across rune boundaries
ID:SPEC-144Status:accepted
Declarative entity and edge registration
ID:SPEC-143Status:accepted
Declarative slot labelling
ID:BUG-027Status:fixed
A {% snippet %} produced by a {% data %} row template resolves before its row is bound
Severity:majorMilestone:v0.39.0
ID:SPEC-141Status:shipped
Preprocess is a rune concern, resolved in tree order
ID:WORK-609Status:done
Stop findChildren retyping author-nested runes of a colliding name
Priority:highComplexity:moderateMilestone:v0.39.0
ID:WORK-610Status:done
Let findAllByName resolve owner-marked nodes across a rune boundary
Priority:mediumComplexity:simpleMilestone:v0.39.0
ID:WORK-611Status:done
Add the registers declaration and its core registration hook
Priority:highComplexity:complexMilestone:v0.39.0
ID:WORK-612Status:done
Migrate storytelling's entity and bond registration onto registers
Priority:mediumComplexity:moderateMilestone:v0.39.0
ID:WORK-613Status:done
Migrate design's registration onto registers
Priority:lowComplexity:simpleMilestone:v0.39.0
ID:WORK-614Status:done
Add the slot declaration and generate a rune's transform from it
Priority:highComplexity:complexMilestone:v0.39.0
ID:WORK-616Status:done
work, bug and decision drop their transforms for the slot declaration
Priority:mediumComplexity:moderateMilestone:v0.39.0
ID:WORK-617Status:cancelled
character, realm and faction drop their transforms for the slot declaration
Priority:mediumComplexity:moderateMilestone:v0.39.0
ID:SPEC-147Status:draft
Replacing the storytelling plugin with composed runes
ID:WORK-615Status:done
Remove snippet's standalone figure wrapper
Priority:mediumComplexity:simpleMilestone:v0.39.0
ID:WORK-618Status:done
Resolve preprocessors in one tree-order walk
Priority:highComplexity:complexMilestone:v0.39.0
ID:BUG-018Status:fixed
breadcrumb auto loses every ancestor below depth 1
Severity:majorMilestone:v0.39.0
ID:BUG-025Status:fixed
Grouping by a multi-value field keys on the whole comma-string
Severity:majorMilestone:v0.39.0
ID:BUG-028Status:fixed
figure silently drops every child that is not an image
Severity:majorMilestone:v0.39.0
ID:SPEC-142Status:draft
Infer the transform signature from the rune's own declarations
Work Items
Draft 1
WORK-617 main
character, realm and faction drop their transforms for the slot declaration The second proving set for SPEC-143: the storytelling entity runes whose sections arrive as already-rendered child runes (emitTag). Together with WORK-616 this covers both sides of the emitTag split, which is what proves the mechanism rather than one shape of it.Same gate (D7): no drift in contracts or the SEO baseline, per rune.recipe is the standing proof that the escape hatch is still needed (D3). It is not migrated, and it is not bent to fit.
0/6 criteria