v0.45.0 — Steps and the list

A numbered sequence renders its ordinal through CSS:

Every rune that declares sequence: names the container holding its items — except one. Steps builds its <ol> at plugins/marketing/src/tags/steps.ts:166 and pushes it straight into children two lines later, so the element carries no data-name, gets no BEM element class, and cannot be addressed from a layout tree.

A composition template has no way to arrange ordinary slots as a row, except by placing the bar rune, which is a name-resolution boundary (SPEC-145 D19). And it has no way to wrap an each slot's items in a list. SPEC-156 D2 and D3 answer both with one template tag, {% group name="…" layout="bar|list" %}, an engine wrapper with an arrangement. Renamed 2026-10-29: the ladder is ADR-018's canonical list, with the contract SPEC-181 D3 defines; SPEC-181 D4 adds grid and carousel to the same tag later.

Whether an ordinal is information is a fact about the content, so sequence is identity (SPEC-158 D2). A composition declares it in its definition, where a theme's replacement template cannot remove it (SPEC-156 D12, ADR-045). And a list's data-sequence lands on its own items track only, not on every ordered list inside the rune (D14).

steps is a section with a numbered sequence of steps, each a section with a split (SPEC-161 D5). Its numbering needs a sequenced list group, which WORK-676 and WORK-677 provide, and SPEC-169 D4's example is the template.

Track's config is { block, parent, defaultElevation, editHints }. Its artist, duration and date are hand-built spans, and track.css hand-writes the row and the duration's push to the end. The byline form (name above, artist, year and duration beneath) needs no new mechanism, only adoption (SPEC-156 D7).