The authoring-facing half of SPEC-084: a contract guide for rune authors plus a CLI audit. (The end-user catalog of concrete compositions lives separately in the "Compositions" docs category, WORK-346 — this item is the "how the contract works" reference, not the recipe book.)
Tracking started Jun 5 — check back for trends.
site/content/extend/rune-authoring/ documents the contract: the open-world principle (dependency asymmetry), open containers vs strict requiresParent children, the name-agnostic media-zone/slot styling model, and when to reach for a context modifier.refrakt inspect/audit reports context modifiers that lack CSS coverage.requiresParent violations (a child outside its self-declared required parent) for a given content tree.Extend the existing inspect/audit tooling (packages/cli) — it already derives selectors from config and checks CSS coverage, so the context-modifier check is an extension of that path. The guide is the contract reference; concrete worked patterns live in the compositions category.
packages/cli (inspect/audit), site/content/extend/rune-authoring/Completed: 2026-06-05
Branch: claude/v0.19-composability
site/content/extend/rune-authoring/composability.md — documents the contract: the open-world dependency-asymmetry principle, strict requiresParent children vs open containers, name-agnostic media-zone/slot styling (with the self-declared bleed opt-out), when to reach for a contextModifier, the deferred capability-token generalization, and a Tooling section. Cross-links to the Compositions catalogue (/compositions, WORK-346).refrakt inspect <rune> --audit already derives and checks context-modifier selectors — e.g. .rf-hint--in-feature → hint.css:88, and any declared-but-unstyled modifier shows NOT STYLED. Documented in the guide.requiresParent line to refrakt inspect output (format.ts) — e.g. inspect tab → "requiresParent: TabGroup (validated…)". Violations on a content tree are reported at build time by the WORK-337 engine validation (and inspect-ing a stranded child prints the diagnostic).requiresParent violations) is delivered by the build-time validation from WORK-337 rather than a separate offline CLI pass — the transform runs at build and emits the warning/error with the rune + its actual parent context.