Separate the prose capability from the body role

body carries two meanings that were merged by accident of timing:

main View source

Criteria completion

Tracking started Sep 6 — check back for trends.

Relationships

ID:SPEC-125Status:draft

Theme-independent attribute applicability

ID:SPEC-108Status:accepted

Reading role: an editorial treatment for body text

ID:WORK-534Status:ready

Narrow rune schemas to applicable universal attributes

Priority:highComplexity:complexMilestone:v0.32.0

ID:SPEC-124Status:accepted

Facet registry for the identity transform's universal axes

ID:WORK-531Status:ready

Correct section roles — media and places runes

Priority:mediumComplexity:simpleMilestone:v0.31.0

ID:WORK-532Status:ready

Lint slot/role mismatches

Priority:mediumComplexity:simpleMilestone:v0.31.0

main current ready

claude/transform-package-refactor-7mxi8a ready main ready

Shape

Declare the gate rather than inferring it, per SPEC-125's governing rule:

readingAxis.requires = 'prose'
TextBlock: { provides: ['prose'] }

Only one axis needs it initially, so this is close to a bespoke field in cost. It is worth the general shape because SPEC-124 already gave every facet a declaration point — requires sits beside contract and describeForRune, and flows into the structure contract for free. A bespoke proseSection on RuneConfig solves the same case and leaves the next axis to invent its own.

Acceptance Criteria

reading and dropcap gate on a declared prose capability, not on the body role
The capability is declared by the facet and provided by the rune, so the next axis needing one does not invent a bespoke field
The structural body role and every stylesheet keying on [data-section="body"] are unchanged
The ~21 body-role runes are audited for whether they bear authored prose
DataTable, Showcase, Form, Api and Symbol no longer offer reading/dropcap; Blog, TextBlock, PullQuote, Sidenote and Lore still do
The structure contract's unavailable reasons reflect the new gate rather than still citing the body role
A breaking changeset records the runes that lose the attributes
npm run build, the full repo suite, and refrakt contracts --check pass

Approach

Sequenced after WORK-534, and the order is load-bearing. The design question is the default:

Default-on (a body role implies prose unless a rune opts out) keeps the migration tiny, but preserves the lossy proxy as the default — so this same bug recurs for the next non-prose rune.
Default-off (a rune must declare that it bears prose) is honest, but a forgotten declaration silently disables reading — today's failure mode returning.

Default-off is right only once schemas have narrowed: with WORK-534 in place a forgotten declaration is no longer silent — the attribute is not offered and refrakt reference says so. Running this first would forfeit that, so take default-off and rely on the narrowing to make omissions discoverable.

Note Playlist may arrive here from WORK-531 with a newly-added structural body role and no prose — that is the intended interaction between the two items, not a conflict.

Blocked by

WORK-534

References

SPEC-125 — Phase 4, and The governing rule
SPEC-108 — where the proxy was introduced
SPEC-124 — the facet declaration point this reuses