V0.48.0
Name:v0.48.0Status:planning

v0.48.0 — Compositions go live

The first composed runes replace their plugin counterparts: hero, cta and testimonial move from site/staged-runes/ into the marketing plugin (SPEC-181 D5). Beside them, every rune reference page gets a generated intro that says what the rune is and shows its source (SPEC-187).

Not enough history yet — burndown needs at least one completed day of activity.

Progress 9/9 work items

Relationships

Related 12

Work Items

Done 9
WORK-702 main
The composed hero goes live in the marketing plugin
site/staged-runes/hero.md has been reviewed on staging.refrakt.md and shows no difference from the plugin hero (WORK-689). SPEC-181 D5 makes going live its own item. This is the first one, so it is also the first use of a plugin runeDir (SPEC-153 D2) and of the contract and baseline diffs a go-live produces.
high moderate
7/7 criteria
WORK-703 main
The composed cta goes live in the marketing plugin
site/staged-runes/cta.md was reviewed with the hero in WORK-689. It goes live on the path WORK-702 opens: the marketing plugin's runeDir.
high simple
5/5 criteria
WORK-704 main
The composed testimonial goes live in the marketing plugin
The staged testimonial has been approved on staging.refrakt.md. Its final form places a featured quotation (WORK-700), so it goes live after that lands, on the path WORK-702 opens.
high simple
6/6 criteria
WORK-705 main
Generate a per-rune intro record from each reference page and the rune's resolution
SPEC-187 D5: the rune intro renders from data. One record per rune, beside the attribute records scripts/generate-rune-attributes.mjs already writes.
medium moderate
6/6 criteria
WORK-706 main
The rune-intro partial renders a section with the package, title, description and bar
SPEC-187 D2, D3, D8 and D9: site/content/_partials/rune-intro.md, included as {% include file="rune-intro.md" variables={r: "rune:<name>"} /%}, renders a section whose eyebrow is the package, headline the title, blurb the description, and whose body is a bar. The spec's sketches show the intended result for a composition, a native plugin rune, a core rune, a non-stable rune and a staged rune.
medium moderate
9/9 criteria
WORK-707 main
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. A page cannot tell which site it is rendered for today, so this adds a $site page variable first (D7, amended).
low moderate
7/7 criteria
WORK-708 main
Every rune page opens with the intro, the install hint goes, and the guard keeps it gone
SPEC-187 D1 and D6: all 119 pages under site/content/runes/ open with the intro include. The hand-written # Title, the "This rune is part of @refrakt-md/…" hint (on 45 pages) and any opening paragraph that only restates the description are removed.
medium moderate
5/5 criteria
WORK-709 main
A link to a drawer opens it, and the rune intro's actions are actions in a bar
SPEC-187 D10–D12. The rune intro's Install and Source are text links built with ref and file-ref (WORK-706): neither rune can carry an icon, the two render in different styles, and actions cannot place them, because only those runes open a drawer. This item makes an ordinary link open a drawer, gives actions a bar context, and moves the intro onto both.
medium moderate
11/11 criteria
WORK-710 main
Rune source files carry comments only where the code would mislead
The rune intro's Source drawer shows every rune's source file to readers. Those files carried 2,278 comment lines against 13,095 lines of code, 382 of them citing specs, work items, bugs and ADRs: history and cross-references written for whoever was implementing, not for someone reading the rune. The call-to-action alias was also dropped by omission when cta went live, not by a decision, and comes back.
medium moderate
4/4 criteria