From e5303f82173975c25269711d407ea9256734ecdd Mon Sep 17 00:00:00 2001 From: dev Date: Fri, 12 Jun 2026 22:16:48 +0200 Subject: [PATCH] =?UTF-8?q?fix(eidos):=20button=20tonal=20variants=20rende?= =?UTF-8?q?r=20bg/border=20+=20variants=C3=97colors=20gallery?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The recipe defined per-color tonal tokens inconsistently — only fulfill/loss had `track`/`border`, so soft/surface/outline rendered with no background or border for the other 6 colors (primary/secondary/neutral/affirm/risk/threat): `palette-track`/`palette-border` referenced undefined `--button-{color}-track`/ `-border`, which collapsed the background/border declarations. Added the missing track+border to all 6 (mapped to `var(--color-{role}-track|border)` like fulfill/loss); the recipe is now uniform (7 slots per color). Verified all 8 colors × soft/surface/outline in dark + light. Demo: new "Gallery" tab — a 6 variants × 8 colors matrix of real + @@ -455,6 +472,32 @@ {/if} + {#if tab === 'gallery'} +
+

Variants × colors

+

+ Every eidos variant across all 8 color roles. + Hierarchy (primary / secondary / neutral) rides the + color prop; the evaluative palette (affirm / fulfill + / risk / threat / loss) rides intent, + which wins on data-color. +

+
+ {#each variants as v} +
+ {v} + {#each gallery as c} + + {/each} +
+ {/each} +
+
+ {/if} + {#if tab === 'api'}

API reference