WORK-387
Setting up your dashboard 0 entities found · 9/32 branches scanned
ID:WORK-387Status:ready

Rune-doc drift guardrail

Frontmatter-driven catalogues can drift from code — add a defineRune without a doc page and it silently vanishes from the generated catalogue. Turn that into a build signal. Fast-follow to the catalogue work.

Priority:lowComplexity:simpleMilestone:v0.21.0Source:SPEC-092
changeset-release/main View source

Criteria completion

Criteria completion: 0 of 2 (0%) checked; tracking started on Jun 11, no incremental history yet0%25%50%75%100%Jun 11Jun 15

Tracking started Jun 11 — check back for trends.

Relationships

Implements 1
Related 3
Branches 3
changeset-release/main current ready
claude/work-385-rune-catalogue donemain doneclaude/v0.21-work-breakdown ready
History 3
  1. 8939b35
    Content editedby Claude
    feat: generated rune catalogue + drift guardrail (SPEC-092)
  2. 7d00ec5
    Created (ready)by github-actions[bot]
  3. 5a2b530
    Content editedby Claude
    plan: v0.21.0 work breakdown — SPEC-092 + SPEC-093 (WORK-383..390)

Acceptance Criteria

  • A check (a refrakt inspect mode and/or a test) asserts every core defineRune and every plugin Plugin.runes entry has a corresponding /runes/<name> doc page, and flags doc pages with no backing rune.
  • Runnable in CI; a missing page is a clear failure naming the rune.

Dependencies

  • WORK-385 (establishes the /runes/<name> doc-page convention to check against).

References

  • SPEC-092 (drift guardrail) · refrakt inspect --list / refrakt reference (the existing programmatic catalogue)