A metaFields entry can render its value as marks: rating: { total } makes the engine emit total spans, the first value of them data-filled="true" (buildRatingValue, packages/transform/src/engine.ts). The mechanism is generic (its own doc comment says "star ratings, progress dots, etc."), but the output is not:
Tracking started Oct 10 — check back for trends.
8dca765marks: { total, values? }; rating: { total } keeps working as an alias for one release, with a deprecation notemetaType as data-meta-type, like the other shapes; a field with no metaType gets nonevalues maps an enum to a filled count ({ trivial: 1, simple: 2, moderate: 3, complex: 4 }); a value with no entry renders as plain textrole="img" and aria-label="3 of 4", localisable), asserted in a testmetaType gains rating; testimonial declares metaType: 'rating' and renders exactly as today[data-meta-type="rating"] marks and neutral dots for every other marks elementwork renders complexity through marks, and the five [data-complexity] ::after rules in work.css are deletedrating still publishes ratingValue)buildRatingValue becomes buildMarksValue, reads f.field.marks ?? f.field.rating, resolves the filled count through values when present, and copies f.field.metaType onto the element as buildIconValue does. ResolvedField.ratingTotal follows the rename. The metaType unions in packages/transform/src/types.ts gain 'rating'.
A composed rune declares marks through metaFields in frontmatter, as testimonial's does in SPEC-161 D1, so the composition path needs nothing beyond the rename.
testimonial, which measured the rating shape publishing through a composition.