The collection rune core — a sentinel-emitting schema plus a postProcess resolver that queries the registry (filter/sort/group/limit) and renders the built-in layouts, with the pinned $item bound-variable contract and the per-layout body interpretation.
Tracking started May 25 — check back for trends.
{% collection type filter sort group limit show %} emits a sentinel; the resolver runs in postProcess after expand + xref so item links resolve through the same chainregistry.getAll(type) and applies the shared field-match parser (WORK-261), sort, group, and limitlist (default), cards, grid, table; fields projects named data fields with humanized headers and default per-type rendering (no key=Label)$item bound (WORK-262); $item shape per the pinned contract (id/type/url guaranteed; payload under data.*, no hoisting; url empty-string not undefined; read-only)item-template partial both supported; both set → build error naming bothdata-rune="collection", data-type, data-layout, data-entity-id, data-field; CSS in packages/lumina/styles/runes/collection.css covers list/cards/grid/table + groupingrefrakt inspect collection shows expected HTML; authoring docs cover the display levels and the $item contract