Component worklist

W2 done: the answer body now uses the main paragraph font (var(--font-body)) and the real text colour (--text-on-page / --text-on-alt) instead of a faint grey --text-muted. Verified on bluelotus — the answer now renders in PT Serif (its real body font) at full black.

Done in W1. Buttons keep the brand fill where it contrasts the surface, but on any surface where the brand would vanish I shift it (lighten on dark / darken on light) to a ~3:1 contrast floor, and every hover now has a guaranteed minimum perceptible change (Δlum ≥ .10) pushed toward the button text — 2250 went .06→.26, addictive .14. WCAG: 2.x has no explicit hover-contrast rule; 1.4.11 wants 3:1 for UI state/boundary, which the floor targets. All CTA components (form submit, pricing, cta-band) inherit this automatically.

W1: submit is now right-aligned and tied to the main .btn--primary, so it behaves exactly like the hero/nav buttons (incl. per-surface hover) — the Divi-vs-Gravity-Forms split shouldn’t recur. STILL TO DO (W3, next): the dark-surface field invisibility — Shoelace fill + Pico underline; I’ll keep the Pico underline distinct from the focus colour. W3 done: on a dark section the Shoelace field borders and Pico underline now use a visible light hairline (rgba(255,255,255,.34)), kept distinct from the brand focus colour. Verified in the gallery dark column (screenshot). Filled libs (OpenProps/DaisyUI) already show a light field on dark. Message textarea shortened: rows 5→3 + min-height 7rem→4rem across all 4 libs, so it reads more like a comment line than a giant box (matches the dark example you flagged). Still vertically resizable by the user.

Done via W1 — the primary button now has a contrast floor against the band it sits on, so it won’t disappear on a dark/emphasis section (absoluteit was the failing case; beechworth already worked). Worth an eyeball in the showcase.

W2 done: the small heading is bumped a step (--type-h4→--type-h3 size) and to a bolder weight (--type-weight-h2) for a clearer heading↔body delta; body text uses a readable colour. The faint ‘Feature’/linework on cakewallet/openprops/daisyui improves with this + the softened --text-muted. Dark elevation: a dark rgba(0,0,0) drop shadow is invisible on a dark surface, so on dark contexts the shadow scale now swaps to a soft LIGHT glow (inverse drop shadow) so cards lift the same way the light version does. Also bumped the dark hairline slightly (.16→.22) so the card edge reads. On the accent-border question: see chat — recommend keeping the card border NEUTRAL (accent stays meaningful on the icon pill + featured/action cards), with the glow doing the lift; a subtle brand-tinted hairline is available if you want a whisper of brand.

Answer to your question: footers ALREADY default to var(--font-body) (set on .section-footer-v1) — so they DO match the paragraph body font. The reason they look the same is the body-font capture: ~47% of teardowns fall back to Inter. That’s W5 (improving googleFontFor + flagging low-confidence). The only heading-font bits left in the footer are the brand NAME and the daisyUI CTA pill, which is correct.

W3 done (border): the Pico image frame now uses a visible light hairline on dark sections (was a currentColor-mix that vanished). The FONT half of your note — body fonts so often identical — is W5 next (improving the Inter catch-all in googleFontFor + a low-confidence flag). W5 (font): you were right — ~47% were defaulting to Inter because googleFontFor mapped any unrecognised face to it. I widened the alias map (DIN→Archivo, Söhne/Switzer→Inter deliberately, Canela/Ogg→Playfair, Clash→Space Grotesk, etc.) and added grotesk routing, and added a font_confidence flag: 23/63 are now flagged ‘low’ (font fell to the Inter default / wasn’t captured). The gallery shows a ‘font?’ chip for those, so a defaulted Inter is now distinguishable from a genuine one. Re-mapped from the stored *_font_id (no re-capture).

W4 done (all 4 libraries): the hamburger now animates its three bars into an X on open (pure CSS :checked transform, no JS). Burgers are always transparent now — removed the DaisyUI border + hover fill and the OpenProps hover/pill background. And the Shoelace nav is now a rounded strip that floats on the page (page-coloured rounded card + soft shadow + margin, dropping the full-width hairline chrome). Verified at mobile width: clean transparent X + open menu.

Done via W1 — pricing CTAs already use .btn--primary, so the dark-safe per-surface fills + min hover roll straight through. The Shoelace ‘dark button on dark bg’ (2250) is fixed by the per-surface contrast floor. Follow-up fix: the W1 contrast floor was computed against each teardown’s OWN surfaces, but the gallery dark column / dark-theme lead REMAP --bg-page to the dark inverse AFTER that — so an on-page button (dark-safe for a light page, e.g. 2250 near-black) was still rendering on the now-dark card and vanishing. Fixed: the dark remap now also swaps the page/alt button tokens to the dark-safe --btn-*-on-inverse. Verified 2250 (#69696b) + absoluteit (#636875) ‘See the menu’ visible on dark.

W2 done (legibility): step body now uses --font-body + the real --text-on-page colour (was the faint --text-muted, which I also softened globally 0.42→0.68). The ‘feels the same / not captured as serif’ part is the body-font capture issue — that’s W5 next (cutting the Inter catch-all + a low-confidence flag); fonts like PT Serif/Lora now come through where captured. W5: the body-font sameness is now visible via the ‘font?’ flag (23/63 low-confidence) and reduced via the widened mapping. Where a real serif was captured (e.g. PT Serif/Lora) it now comes through; where the site used a paid/system face we map to the nearest Google + flag it.