Today each iterates a list only when the field has an itemModel with an emitTag. A list whose items need no extraction, where each item's content is placed as it is, has no way in. That blocks steps, which takes its steps from headings or from an ordered list (SPEC-169 D4).
Tracking started Oct 24 — check back for trends.
each on a non-greedy field matching one list iterates its items, with the bare slot as each item's content and no $each bindingssteps fixture renders the same steps from headings and from an ordered list, with one model and no conditionaleach over a greedy list field, or a field that can match several lists, is a construction error naming the fieldeach beside itemModel, including that itemModel patterns consume the text they match in order (from BUG-038)steps example places the items in {% group layout="ladder" %}. The ladder is SPEC-156's and still draft, so the fixture uses a plain container. It proves the model, not the look.itemModel patterns in the same part of the resolver. Land it first if both are in flight, so the list each tests run beside working itemModel tests.Completed: 2026-10-25
Branch: claude/v0-42-0-planning-t31f5e
composition.ts: a non-greedy field whose match alternatives are all lists is listItems; each iterates the list's items, giving a tight item's inline content a paragraph, and binds no $each. A greedy field that can match a list (no emitTag) is ambiguousList, and each on it is each-on-list-ambiguous. A field that may match something other than a list stays each-on-single-field.packages/runes/test/fixtures/composed/steps.md, in a plain grid until SPEC-156's ladder exists, and included in the guide beside the itemModel docs and the pattern-order note.