Paint the SPEC-107 axes in Lumina and retire the rune-name lists in surfaces.css — the last cross-rune file that enumerates runes (SPEC-094 §8).
Tracking started Jun 15 — check back for trends.
a269c1bdata-elevation rung to a chrome bundle (fill / border / radius / shadow) via low-specificity attribute selectors — the rung's shadow is the rune surface's resting box-shadow depth, kept distinct from frame-shadow's per-guest drop-shadow (SPEC-107 §1); map each data-prominence value to a header type register (using the v0.22.0 type tokens).defaultElevation / defaultProminence (and defaultWidth where a rune was a banner) so today's appearance is preserved: card-bucket runes → raised/flat, inline → flush, inset → sunken, banner → flush + width: full.surfaces.css rune-name buckets (and the two nested :where(.rf-card, …) media-chrome lists) with [data-elevation] / [data-prominence] selectors.surfaces.css (the content transform — rune-names → [data-elevation]). It does not introduce @layers; the skeleton/skin layering of that file belongs to the re-bucketing (WORK-438), which consumes this output. 425 hands 438 an already-attribute-keyed file.surfaces.css no longer enumerates rune names; chrome is selected by [data-elevation="…"] (and media-chrome by attribute, not the :where rune lists).prominence registers are wired to the type tokens; CSS-coverage tests + structure contracts stay green.packages/lumina/styles/dimensions/surfaces.css · packages/lumina/src/config.ts.Completed: 2026-06-15
Branch: claude/refrakt-theme-system-analysis-9whpoq (v0.23.0 Batch 2)
defaultElevation across core packages/runes/src/config.ts (CodeGroup/Embed/Gallery/Figure/Reveal/Form/Budget → flat; Chart/Diagram → sunken; Hint/Details/Sidenote/Conversation/Annotate/PullQuote/TextBlock/Nav/Breadcrumb/TableOfContents/DataTable → flush) and the 8 content plugins (card-bucket runes → flat; banner runes hero/cta/feature/steps/bento/storyboard/map → flush). Verified in the static gallery: flat ×134, flush ×73, sunken ×10 all emit from defaults (gallery transforms with base+plugins, so Option A is gallery-visible without a browser).surfaces.css is now rune-name-free. Retired the four rune-name buckets (card/inline/banner/inset) and both media :where lists; chrome is selected by [data-elevation="flat|sunken|raised|floating|overlay"] (surface fill/border/radius/padding + resting shadow rungs) and [data-prominence="quiet|prominent|display"] (title type register via --rf-title-size). The chart/diagram media-guest reset is keyed on [data-section="media"] > [data-elevation="sunken"].[data-elevation="flat"] [data-section="media"]:not([data-media="portrait"]) — the data-media discriminator excludes character/testimonial floated avatars exactly as the old rune list did. The hand-rolled card / bento-cell surfaces (which sit outside the elevation axis — bento-cell's bg is intentionally zero-specificity for per-cell tints) carry the same media chrome from their own CSS files; the juxtapose media-guest reset moved to juxtapose.css.[data-elevation=none|sm|md|lg] shadow rules from base/attributes.css (the engine maps those deprecated aliases onto the ladder before they reach the DOM, so they never matched).defaultElevation/defaultProminence is styled by the axis dimension, so it counts as covered (coverage back to 93%, 176/176).packages/transform elevation+prominence suites green; full package suites green (2885 tests across transform/runes/lumina/content/svelte/cli/ai/plugins).--check clean (root-axis attributes aren't captured by contracts, so no drift).var(--rune-padding, xl|sm|md) only ever hit the fallback when --rune-padding was unset — but every rune with a density already sets it, so the effective padding was always --rune-padding. The new flush/flat/sunken rules reproduce that exactly; no per-rune padding additions were needed.width: full to steps/bento/storyboard/map. The scope bullet said "banner → flush + width:full", but those four are currently content-width (only hero/cta/feature carry width:full). Making them full-bleed would be a visual change, violating the "no unintended change" AC — so they got flush only. hero/cta/feature keep their existing width:full. Flag for review if full-bleed banners were actually intended.assembleThemeConfig, like the site) — not a blocker here since base defaults render in the gallery, but needed before theme-level surface overrides are visible in the regression net.surfaces.css (no @layers introduced — that's 438's job).