V0.50.0
Name:v0.50.0Status:active

v0.50.0 — Nothing reads a class

Every fact the output carries is a data attribute, and nothing but a stylesheet reads a class. This is step 1 of ADR-048's implementation order: the parts of SPEC-196 that depend on nothing else, done first because every later step relies on them.

Milestone burndown: 1 open work item remaining; peak 5, started Nov 9024Nov 9Nov 22
Open work items Ideal burndown
Progress 3/4 work items

Work Items

Ready 1
WORK-725 claude/rune-composition-layout-convention-hkqrzx
The UI a behaviour builds carries data-name, and its CSS moves to it
SPEC-196 D6. Behaviours create their own UI (toolbars, buttons, indicators) with about 70 className = writes. Those classes are the behaviour's own, so nothing breaks while they stay. But the CSS styling them reads classes, so a page under classes: "none" would still depend on them. Each element also gets a data-name, and the CSS moves to it.This is the lowest-priority item in the milestone. If it slips, it moves to the next one without holding anything up.
low moderate
0/4 criteria
Done 3
WORK-722 claude/rune-composition-layout-convention-hkqrzx
Every fact a class carries is also an attribute, and the CSS reads the attribute
SPEC-196 D5. Before classes become optional, each fact only a class carries today gets a data attribute, and the engine emits both. The measurement in D5 found two such facts:
high moderate
9/9 criteria
WORK-723 claude/rune-composition-layout-convention-hkqrzx
Behaviour scripts and components select by attribute, and a test forbids class selectors
SPEC-196 D6. @refrakt-md/behaviors has 27 sites that select by .rf- class, and the Svelte components 2 more (ThemeShell.svelte selects rf-docs-sidebar at lines 76 and 95). The prefix is configurable, so any theme with another prefix breaks them today. They move to data-name, data-rune and the other vocabulary attributes.The D6 measurement split the sites:
high moderate
9/9 criteria
WORK-724 claude/rune-composition-layout-convention-hkqrzx
Behaviours write state as data-state, not as classes on rune-owned elements
SPEC-196 D6. Four behaviours write classes onto elements a rune owns. Under a theme that chooses classes: "none", that would put classes back on the page, and under a mapping table it produces junk:
medium simple
7/7 criteria