itemModel and render emitTag and template in the rune referenceFor a rune whose primary syntax is a Markdown list, refrakt reference documents that a list is accepted and nothing about what goes in it. Three facts are lost at two points:
Tracking started Sep 24 — check back for trends.
SerializedContentField carries a projection of itemModel, including each item field's match, extract, and pattern (regex source as a string, or the literal 'remainder')renderField renders emitTag, so a dual-syntax field states both what an author writes and what it becomesfield.template is either rendered or removed — a hand-written snippet that nothing displays does not staymatch: 'tag' declarations that render as a bare "tag" are tightened to match: 'tag:<name>' where the rune accepts one specific tagrefrakt reference playlist and refrakt reference cast show enough to write a list item without reading the plugin sourcesite/content/_data/rune-attributes.json) regenerate without unrelated driftThe capability already exists one struct over. SerializedSectionsModel projects headingExtract with pattern documented as "Regex source, or the literal string 'remainder'", and knownSections with aliases and hasModel. Project itemModel the same way rather than inventing a second representation.
Tone: the sections branch renders the authoring shape — "Content is split into sections by heading elements. Each section becomes one named block." Field-level should read the same way, not as a dump of the model.
A concrete trap this must surface. playlist's date pattern is /—\s*(.+)$/ — U+2014 EM DASH. A plain hyphen does not match, the field is optional, so an author who types - gets no date and no warning. cast's own description sentence writes "Name - Role" with a hyphen. Rendering the pattern is what makes this findable.
pattern that is a RegExp with flags — serialize the source, and decide whether flags are shown or dropped.itemModel (playlist's cuePoints) — render one level or recurse; one level is probably enough, but say which in the output.match: 'text' fields with no pattern — these consume remaining text implicitly and should not render as if they matched a node type.