Buttons are a convention, not a primitive. hero and cta render links through linkItem, and Lumina draws the first as primary and the rest as outlined by list position, with the CSS duplicated in hero.css and cta.css. No other rune can get buttons without copying both. {% actions %} makes it a core rune (SPEC-160 D6).
Tracking started Oct 22 — check back for trends.
{% actions %} is a core rune that takes a list of links, and optionally fences, and renders each link as data-name="action" with data-rank="primary" for the first and secondary for the restcommand block, as in hero todayhero.css and cta.css into actions.css, styled by rank, not list positionhero and cta, still plugin runes, render their actions through it with no visual change, checked in the galleryhero fixture over section with a delimited content model renders its media and content zones and wraps its actions list in {% actions %} (the fixture SPEC-169 D1 specifies)Rank stays positional, as today (SPEC-160 D6's default). Authorable rank is left for when a rune needs it.
hero fixture needs section's splithero fixture needs the delimited modelhero fixture places eyebrow, headline and blurb slots in section, so it is recorded against the final header grammar