WORK-713
ID:WORK-713Status:ready

Output and implementation sections leave the rune pages

SPEC-193 D2. Fifteen rune pages carry an Output contract (HTML dumps, BEM classes, data-* attributes), and about 40 explain CSS, custom properties or pipeline internals to content authors. refrakt inspect and the structure contract state the structure, generated.

Priority:mediumComplexity:moderateMilestone:v0.49.0Source:SPEC-193
main View source

Criteria completion

Criteria completion: 0 of 6 (0%) checked; tracking started on Nov 4, no incremental history yet0%25%50%75%100%Nov 4Nov 4

Tracking started Nov 4 — check back for trends.

Relationships

Implements 1
Related 3
Branches 2
main current ready
main readyclaude/composition-usage-rune-pages-c87ar6 ready

Acceptance Criteria

  • The Output contract / Output / Output structure sections are removed from actions, aggregate, badge, bar, card, code, collection, deflist, expand, file-ref, link, progress, relationships, snippet and plan/plan-history
  • backlog, decision-log and plan-activity keep their "Output structure" prose as "What it shows", without theming detail
  • CSS, custom-property, engine and pipeline sections (F1) are removed from rune pages, or moved to the theme- or rune-authoring handbook where worth keeping there, each move named in the resolution
  • Adapter "Theme Integration" sections move to extend/; the maintainer sections ("Keeping this page honest", "Local-development reference") are removed
  • Example content about the engine (feature, plan/work, plan/spec, plan/milestone) is replaced with real content
  • No page links to a removed section

Blocked by

  • WORK-712

References

  • SPEC-193: D2, F1.