The composed hero and cta adopt marquee and display, and are compared against the plugins

The staged hero defaults to marquee and the staged cta declares display (SPEC-183 D1). Their comparison tests then check that every value the plugin stylesheets set comes from the register instead (D6). Whatever differences remain are explained, as SPEC-181's review gate requires.

main View source

Criteria completion

Tracking started Oct 30 — check back for trends.

Relationships

ID:SPEC-183Status:shipped

Prominence is a register: a marquee step, and the header and band scale with it

ID:WORK-688Status:done

Prominence gains a marquee step and sizes the whole header and flush band

Priority:mediumComplexity:moderateMilestone:v0.45.0

ID:SPEC-181Status:accepted

Staged runes: a composition is reviewed on its own reference page before it replaces a plugin rune

ID:v0.45.0Status:complete

v0.45.0 — Steps and the ladder

ID:v0.48.0Status:complete

v0.48.0 — Compositions go live

ID:WORK-702Status:done

The composed hero goes live in the marketing plugin

Priority:highComplexity:moderateMilestone:v0.48.0

ID:WORK-703Status:done

The composed cta goes live in the marketing plugin

Priority:highComplexity:simpleMilestone:v0.48.0

main current done

changeset-release/main in-progress claude/milestone-v0-44-0-ism7ni done main done

Acceptance Criteria

site/staged-runes/hero.md defaults to prominence: marquee, and site/staged-runes/cta.md declares prominence: display
The comparison tests assert the title size, blurb size, band padding, gradient and button size of each against the plugin rune, through the register's custom properties
The blurb's measure, and any inline-padding difference, are recorded as explained differences, unless the staging review finds them wrong (D6)
The composed-runes guide says the composed hero and cta take their header and band from marquee and display; the plugin reference pages are unchanged until the runes go live
refrakt validate --site staging reports nothing beyond main's, and staging.refrakt.md is reviewed against refrakt.md on the hero and cta pages

Blocked by

WORK-688

References

SPEC-183
SPEC-181: the rollout gates.

Resolution

Completed: 2026-10-31

Branch: claude/milestone-v0-44-0-ism7ni

What was done

site/staged-runes/hero.md defaults to prominence: marquee, and site/staged-runes/cta.md declares prominence: display.
packages/content/test/composed-landing-register.test.ts (new) compares each composition against the plugin stylesheet, value by value: title size, blurb size, band padding, gradient and buttons. The hero and cta comparison tests now assert the step.
The staging review on a phone (#744) found and fixed:
- {% bg %} / {% tint %} landing on the composed rune's empty root. They now go to the paint carrier, and [data-bg] hosts are positioned.
- A full-width composed root not moving its gutter onto the carrier.
- The marquee gradient resolving the section's colours, not the title's (a dark cover title).
- The section header growing past its column, and stretching a pill eyebrow.
- A stacked end split putting media first.
- Missing 2rem inline band padding, and phone block padding.
- The 65ch header measure wrapping a marquee title.
After #744 the user found no difference between staging.refrakt.md and refrakt.md on the hero pages.

Notes

SPEC-183 D2/D4 (the cta's gradient and text-lg blurb) and D3/D6 (inline padding, cover-only phone padding, the measure) were amended during the review.
The blurb's measure is no longer an explained difference: the loud steps put the 40rem measure on the blurb, as the plugins do.