Hero and feature drop a second leading heading and everything after it

Found while settling ADR-046's open question about heading eyebrows. The page-sections guide documents two leading headings as an eyebrow and a headline. cta renders that. hero and feature take the first heading as the headline and silently discard the second heading and the blurb after it.

hero's content zone is a sequence of eyebrow (a paragraph), headline (a heading), blurb (a paragraph) and actions (a list or fence) (plugins/marketing/src/tags/hero.ts:73-78). With two leading headings the eyebrow is skipped, the first heading fills headline, and the second heading matches nothing. It is dropped, with everything after it, before pageSectionProperties runs, so that function's two-heading rule is never reached. feature does the same.

claude/post-v0.43-roadmap-mf1ngx View source

Relationships

ID:ADR-046Status:accepted

Section's header grammar is anchored and explicit

Date:2026-10-23

ID:SPEC-160Status:accepted

Section is the composition base; card is a section with a surface

ID:SPEC-161Status:draft

Marketing runes on section: what each needs to compose

ID:WORK-660Status:ready

Stop documenting heading eyebrows

Priority:mediumComplexity:simpleMilestone:v0.44.0

ID:v0.44.0Status:planning

v0.44.0 — Hero, cta and testimonial compose

ID:WORK-665Status:ready

hero is a composition over section

Priority:highComplexity:complexMilestone:v0.44.0

Oct 26, 05:06 PM44496d2
Created (confirmed)by bjornolofandersson

Steps to Reproduce

Render each rune with this body:

## What's new in v2

# Build with refrakt.md

A content framework.

Compare the header each one emits.

Expected

The author's content is either rendered or reported. ADR-046 decides that a heading is never an eyebrow, so the second heading need not be an eyebrow, but it must not disappear without a word.

Actual

Rune	Output
`cta`	`<h2 data-name="eyebrow">`, `<h1 data-name="headline">`, `<p data-name="blurb">`
`hero`	`<h2 data-name="headline">What's new in v2</h2>`; "Build with refrakt.md" and the blurb are gone
`feature`	the same as `hero`

No warning is emitted.

Fix sketch

The lasting fix is SPEC-160 D7: a composed hero over section reads its header with section's grammar, and content past the header is body, not discarded. feature follows when it is composed (SPEC-161).

If that is more than one milestone away, an interim warning in hero and feature when the content zone leaves nodes unmatched would make the loss visible. The documented example goes in WORK-660 either way.

Environment

main after v0.42.0 (a554ab9)