v0.44.0 — Hero, cta and testimonial compose

ADR-046 decides that an eyebrow is a paragraph directly before the headline, never a heading. The docs still teach the heading form. The guide's only example of it uses hero, which renders it wrongly (BUG-047), and nineteen rune pages say "a short paragraph or heading" in the same boilerplate sentence.The native page-section runes keep their grammar until each one is composed (ADR-046, decision 4), so some of them still accept the heading form. The docs stop recommending it anyway: it is not the direction, and documenting less than a rune accepts is safe where documenting more is not.

A composed rune's universal attributes land on its own root, which is an empty wrapper around the primitive it places. elevation="raised" there draws a second complete surface around the first (SPEC-145 D14). This item moves the paint group to a carrier: the template's single top-level rune by default, or the one marked chrome (D31). Resolution looks through nested compositions (D24).

WORK-661 places D14's eight attributes. The registry has twelve axes, and prominence, reading, dropcap, frame, bg and stagger have no placement: on a composed root they are dropped with a warning, do nothing, or paint the empty wrapper. scrim is placed wrongly, on the media slot's owner, when the registry files it under bg (SPEC-145 D33).

A native rune states its chrome defaults in config (defaultWidth, defaultElevation, defaultDensity). A composition has no way to, and hero needs width: full, which a template cannot write because width stays on the root (SPEC-145 D34).

The native hero and feature host a media guest with guestFit: 'bleed', a config field. A config field cannot differ between compositions that place the same section, and hero needs bleed where a card-like composition needs clip (SPEC-160 D7).

hero becomes a section with a split, cover, the header and {% actions %}, with no rune CSS of its own (SPEC-160 D7). WORK-654 leaves a composed hero fixture; this item completes it and compares it with the plugin.

cta becomes a section with a header and {% actions %}, with no rune CSS of its own (SPEC-160 D7).

A blocks entry renders through bar (a row) or definition-list (a label/value grid). Neither draws a byline, a lead value with secondary values beneath, which testimonial and cast each hand-roll in their CSS (SPEC-161 D6).

testimonial becomes one section with a portrait media zone, the rating and byline metablocks, and the quote slot (SPEC-161 D1). Its author and role move from a **Name** — Role paragraph to attributes, so the schema table can publish them.

ADR-042 makes a composed rune's config its definition's: a theme cannot know which definition it faces, so an override of a composed rune's blocks or metaFields is a guess that silently resolves to nothing. Nothing enforces this yet. mergeThemeConfig and mergeRuneConfig (packages/transform/src/merge.ts) guard the identity fields on every rune, and nothing else, so a theme's runes: entry keyed to a composed rune's type name applies.v0.44.0 adds the first composed runes a theme could try to override (hero, cta, testimonial), so the guard lands with them.