ADR-047 lets a rune declare one narrative field that accepts only the editorial runes textblock and mediatext, and says the field is never published as structured data. As amended, the field is inferred from its match, and both rules are checked.
Tracking started Nov 2 — check back for trends.
match names editorial runes (tag:textblock, tag:mediatext) and nothing else is recognised as the narrative fieldreference and inspect show which field is the narrative fieldstory field renders the story between two template parts, publishes no part of it in JSON-LD, and raises no slot-role warning (ADR-046)Completed: 2026-11-02
Branch: claude/milestone-v0-44-0-ism7ni
packages/runes/src/lib/composition.ts:isNarrativeMatch (exported) and modelFieldDefinitions;schemaSourceNames walks properties and text in rows, fallback, entities and children;compileComposition rejects a second narrative field (narrative-field-twice) and a mapped one (narrative-field-mapped), and records CompositionInfo.narrativeField.composition-errors.ts: the two codes.packages/runes/src/reference.ts and packages/cli/src/commands/inspect.ts print the narrative field; inspect's JSON carries it.packages/runes/test/composition-narrative.test.ts: inference, the dish fixture (story between section and card; no property in the story; no slot-header-role finding), both rejections, the mixed-match case, and reference.