WORK-650
ID:WORK-650Status:draft

Remove property contentSection, the dead Page document nodes and the PageSection config

28 transforms pass property: 'contentSection' to createComponentRenderable, which emits data-field="content-section" on the rune root. Nothing reads it. The one consumer that ever existed, the Page document node, compares the camelCase 'contentSection' against the kebab-cased attribute, so it could never match, and it is never registered by any Markdoc config. Page also stamps typeof="PageSection", which is not a schema.org type. SPEC-133 decided the removal; v0.35.0 deferred it because it changes HTML on every section rune, and nothing has carried it out since.

It lands first in v0.43.0 because it touches the runes SPEC-160 changes next, and it removes one recorded plugin-vs-composed difference from the four composed-storytelling tests before WORK-653 re-runs those comparisons.

Priority:mediumComplexity:simpleMilestone:v0.43.0Source:SPEC-133
claude/v0-42-0-planning-ata7nd View source

Criteria completion

Criteria completion: 0 of 8 (0%) checked; tracking started on Oct 22, no incremental history yet0%25%50%75%100%Oct 22Oct 28

Tracking started Oct 22 — check back for trends.

Relationships

Implements 1
Related 4
Branches 3
claude/v0-42-0-planning-ata7nd current draft
claude/v0-43-0-review-ny4nl1 donemain donechangeset-release/main draft
History 2
  1. fa4981f
    Content editedby bjornolofandersson
  2. abc833f
    Created (draft)by bjornolofandersson

Acceptance Criteria

  • property: 'contentSection' is gone from every transform in packages/runes/src/tags/ and plugins/*/src/tags/
  • packages/runes/src/documents/page.ts and doc.ts are deleted and documents is no longer exported from @refrakt-md/runes
  • The PageSection config entry, packages/lumina/styles/runes/page-section.css and its import in packages/lumina/index.css are removed, and the CSS coverage test passes
  • TransformResult.property stays accepted but is ignored and marked @deprecated for one minor release, so a third-party plugin that still passes it keeps type-checking; its removal is noted for the release after. Before that, check whether any user besides contentSection remains (SPEC-133 names error.ts, which the 2026-10-22 audit could not find)
  • Tests that assert the attribute are updated, and the composed-storytelling tests no longer record data-field="content-section" as a difference
  • The four rune-authoring docs pages no longer document contentSection
  • Contracts are regenerated on both copies and the diff reviewed; the SEO baseline does not move
  • The changeset names the removed attribute, the removed documents export (it never ran, so it is removed outright) and the deprecated property field

References

  • SPEC-133: "Moved here from SPEC-130".
  • SPEC-160: its open question on contentSection is closed by this item.