The staging site's rune intro shows a staged rune as staged

SPEC-187 D7: the committed intro data describes main, so staging.refrakt.md would call a staged rune native. On staging, a rune runes.prefer resolves to site/staged-runes/ shows a Staged badge and that file as its source.

changeset-release/main View source

Criteria completion

Tracking started Nov 3 — check back for trends.

Relationships

ID:SPEC-187Status:accepted

Every rune reference page opens with a generated intro: package, title, description and a bar

ID:SPEC-181Status:accepted

Staged runes: a composition is reviewed on its own reference page before it replaces a plugin rune

ID:WORK-706Status:done

The rune-intro partial renders a section with the package, title, description and bar

Priority:mediumComplexity:moderateMilestone:v0.48.0

ID:v0.48.0Status:planning

v0.48.0 — Compositions go live

changeset-release/main current ready

main done claude/composition-usage-rune-pages-c87ar6 done

Nov 3, 07:39 PMfe601a4
Created (ready)by github-actions[bot]
Nov 3, 06:15 PM506a927
Content editedby Claude
plan: SPEC-187 decides the schema.org badge and the Install drawer
Nov 3, 06:02 PMf91f637
Content editedby Claude
plan: v0.48.0 — compositions go live, and the rune page intro (SPEC-187)

Acceptance Criteria

On the staging site, a staged rune's intro shows a Staged badge in place of Composition, and its Source drawer shows site/staged-runes/<rune>.md
On the main site, the same page is unchanged
The SPEC-181 D3 test that staging matches main apart from runes still passes
The resolution records whether this is a per-site data file or a value computed at build time, and why

Blocked by

WORK-706

References

SPEC-187: D7.
SPEC-181: D1, D3.