Setting up your dashboard0 entities found · 7/34 branches scanned
Name:v0.23.0Status:planning
v0.23.0 — Surface axes & the skeleton/skin extraction
The second slice of the SPEC-094 theme-platform epic. Where v0.22.0 tokenized type and built the gallery safety net, v0.23.0 attacks the differentiation surface: it extracts skeleton from skin and replaces the last cross-rune rune-name lists with engine-emitted, theme-overridable config.
Its centerpiece is SPEC-107 — the surface-axis decomposition. It amends SPEC-094 §8: the single surface enum (card/banner/inline/inset) splits into three orthogonal, theme-defaulted axes — an ordered elevation depth ladder (sunken/flush/flat/raised/floating, folding in today's shadow-only elevation), width carrying the bleed, and a page-section-family prominence scale (quiet/normal/prominent/display). The motivating outcome: the same recipe reads as a bordered card in prose and a full-bleed, large-title hero at the top of a page.
Not enough history yet — burndown needs at least one completed day of activity.
The milestone's exit gate. The skeleton/skin extraction's goal is "theme #2 is a token file + layout + skin, not a fork" — but theme #2 is deferred (SPEC-094), so the extraction would otherwise ship with no consumer to prove it worked. The harness inert-proof only shows Lumina didn't regress; it does not show the skeleton is actually skin-agnostic. A thin proof skin closes that gap.
The wholesale pass the WORK-410 spike sized: re-bucket Lumina's CSS into the two @layers per the spike's cut-line rule, so structure ships in @refrakt-md/skeleton and aesthetics stay in Lumina's skin. Mechanical and low-risk per declaration, but large (~114 files / ~6,058 declarations; the spike estimates ≈40% skeleton / 55% skin / 5% content).
Close the loop on the use case that motivated SPEC-107: the same content rune reading as a contained card and as a full-width hero, by composing the axes — no rune fork.
Stand up the packaging + cascade-layer infrastructure the WORK-410 spike settled, so skeleton and skin can ship and version separately. The structural home the re-bucketing fills.
The "content, not CSS" finding from the WORK-410 spike (SPEC-094 §8's icon-from-config): rune CSS embeds glyph shapes as data:image/svg+xml mask-images. Move them to the theme icon registry so a theme swaps glyph sets without touching CSS.