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

Rune-page metadata backfill

The generated rune catalogue (WORK-386) needs every /runes/<name> page to carry category, plugin, and status frontmatter. Hand-editing ~100+ pages is a slog and drifts — so backfill it with a script.

Priority:mediumComplexity:moderateMilestone:v0.21.0Source:SPEC-092
claude/v0.21-work-breakdown View source

Criteria completion

Criteria completion: 0 of 3 (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 4
Branches 3
claude/v0.21-work-breakdown current ready
changeset-release/main readyclaude/work-385-rune-catalogue donemain done
History 1
  1. 5a2b530
    Created (ready)by bjornolofandersson

Decisions (locked)

  • Backfill by script, not by hand: derive plugin from the owning package, category from the rune's nav group, status default stable. Idempotent (re-runnable; only fills missing keys, never clobbers authored values).
  • status is a fixed vocabulary — stable | beta | experimental | deprecated — chosen so it can later drive a sentiment-coloured nav badge (a separate, deferred nav feature; this item only lands the data, forward-compatibly).

Acceptance Criteria

  • A repeatable script writes category / plugin / status frontmatter to every rune reference page (core + plugin runes), idempotently.
  • status uses the fixed four-value vocabulary, documented; default stable.
  • With WORK-383 indexing, the fields are queryable — verified by a live aggregate type="page" filter="url:/runes/*" group="category".

Dependencies

  • WORK-383 (so the frontmatter is indexed and queryable).

References

  • SPEC-092 · the rune catalogue (defineRune set + each plugin's Plugin.runes) · site/content/runes/_layout.md (nav groups → categories)