@kolkrabbi/kol-theme 0.106.0 → 0.108.0

package/kol-components-atoms.css

@@ -433,12 +433,15 @@
 }
 
 @media (hover: hover) {
-  .kol-btn:hover .kol-icon-default {
+  /* the trigger is excluded here too — it IS a Button, so a consumer giving it
+   * a hover-icon would animate on hover, and the law is rest and open only
+   * (validate-dd-trigger.mjs T1) */
+  .kol-btn:not(.kol-dd-trigger):hover .kol-icon-default {
     opacity: 0;
     transform: translateY(-4px);
   }
 
-  .kol-btn:hover .kol-icon-hover {
+  .kol-btn:not(.kol-dd-trigger):hover .kol-icon-hover {
     opacity: 1;
     transform: translateY(0);
   }

package/kol-components-molecules.css

@@ -1324,7 +1324,22 @@
  * ink `fg-96`. `.kol-tone-inverse` stays selected for any class
  * hand-stamped on the old name.
  * ───────────────────────────────────────────────────────────────────── */
-/* THE SUNKEN TONE IS `surface-tertiary`, NOT `oq-inverse-96` (measured on
+/* THE WELL TAKES THE PAGE'S WASH TOO (SunkenWellEatenByPageWash, kol-fxr
+ * 2026-08-30). `--kol-surface-sunken` is derived from `surface-primary`, but
+ * `AppShell`'s `pageWash` paints a film ON TOP of that page — and the control's
+ * opaque fill does not receive it. At the ruled `fg-02` rung the light page
+ * lands 250 × 0.98 + 18 × 0.02 = 245, which is EXACTLY the well: measured delta
+ * [0,0,0], four controls rendering as bare text with no pill.
+ *
+ * Deepening the well would have worked by luck and broken on the next rung
+ * change. Instead every sunken surface paints the same film the page does, so
+ * the five levels hold by construction whatever `pageWash` is set to. The
+ * property is unset outside an AppShell and falls back to `transparent`.
+ *
+ * State washes stack ON TOP of it — `linear-gradient(state), linear-gradient(wash)`
+ * — because one background-color cannot carry two translucent layers.
+ *
+ * THE SUNKEN TONE IS `surface-tertiary`, NOT `oq-inverse-96` (measured on
  * kol-fxr's /settings, 2026-08-30). The whole set read `--kol-oq-inverse-96`,
  * which is `color-mix(#0e0e11 96%, #fcfbf8)` — four percent of near-WHITE mixed
  * in. On the dark theme that lands at luminance **23.7 against an 18.2 page**:
@@ -1341,13 +1356,13 @@
  * `surface-tertiary` is `#0e0e11` in dark (14.2, genuinely below the page) and
  * `#ffffff` in light, so it is theme-correct on both sides where a mix toward
  * a fixed near-white could only ever be right on one. */
-.kol-view-toggle.kol-tone-sunken, .kol-view-toggle.kol-tone-inverse { background-color: var(--kol-surface-sunken); }
+.kol-view-toggle.kol-tone-sunken, .kol-view-toggle.kol-tone-inverse { background-color: var(--kol-surface-sunken); background-image: linear-gradient(var(--kol-shell-page-wash, transparent), var(--kol-shell-page-wash, transparent)); }
 .kol-view-toggle.kol-tone-sunken > button[aria-pressed="true"], .kol-view-toggle.kol-tone-inverse > button[aria-pressed="true"] { background-color: var(--kol-fg-08); }
 .kol-view-toggle.kol-tone-sunken > button:not([aria-pressed="true"]):hover, .kol-view-toggle.kol-tone-inverse > button:not([aria-pressed="true"]):hover { background-color: var(--kol-fg-04); }
-.kol-control.kol-tone-sunken, .kol-control.kol-tone-inverse { background-color: var(--kol-surface-sunken); }
-.kol-expand.kol-tone-sunken, .kol-expand.kol-tone-inverse { background-color: var(--kol-surface-sunken); }
+.kol-control.kol-tone-sunken, .kol-control.kol-tone-inverse { background-color: var(--kol-surface-sunken); background-image: linear-gradient(var(--kol-shell-page-wash, transparent), var(--kol-shell-page-wash, transparent)); }
+.kol-expand.kol-tone-sunken, .kol-expand.kol-tone-inverse { background-color: var(--kol-surface-sunken); background-image: linear-gradient(var(--kol-shell-page-wash, transparent), var(--kol-shell-page-wash, transparent)); }
 /* the tone's fill, one selector — nothing left to cancel (2026-08-28) */
-.kol-dd-trigger.kol-tone-sunken, .kol-dd-trigger.kol-tone-inverse { background-color: var(--kol-surface-sunken); }
+.kol-dd-trigger.kol-tone-sunken, .kol-dd-trigger.kol-tone-inverse { background-color: var(--kol-surface-sunken); background-image: linear-gradient(var(--kol-shell-page-wash, transparent), var(--kol-shell-page-wash, transparent)); }
 /* THE PANEL IS OPAQUE (user 2026-08-28: "transparent doesn't work for
  * dropdown") — it floats over page content, and every `fg-*` stop is an alpha
  * wash that the content reads through. `oq-inverse-*`, the opaque tier, bakes
@@ -1355,7 +1370,7 @@
  * lands ~23.5 against the #121215 page's 18: lighter than the page, the wrong
  * side of it. `surface-tertiary` is the flat twin of what the trigger renders:
  * #0e0e11 (14.0) in dark against the trigger's 14.2, #ffffff in light. */
-.kol-dd-panel.kol-tone-sunken, .kol-dd-panel.kol-tone-inverse { background-color: var(--kol-surface-sunken); }
+.kol-dd-panel.kol-tone-sunken, .kol-dd-panel.kol-tone-inverse { background-color: var(--kol-surface-sunken); background-image: linear-gradient(var(--kol-shell-page-wash, transparent), var(--kol-shell-page-wash, transparent)); }
 /* the rest of the set — Button (icon-only especially), IconFrame, ThemeToggle:
  * the well, transparent edge, fg-96 ink; hover the CONTRAST wash, pressed the
  * fg-08 chip — both LAYERED over the well (a gradient image over the fill),
@@ -1373,24 +1388,35 @@
  * when that was first fixed it went to an 8% wash — the same strength as
  * `selected`, which put hover 0.4 from selected in dark and 1.5 in light. A
  * hovered unselected control was indistinguishable from the selected one.
- * 04 and 08 are ~10 apart on both themes; the ladder reads. */
+ * 04 and 08 are ~10 apart on both themes; the ladder reads.
+ *
+ * ⛔ THE TRIGGER IS EXCLUDED. `.kol-dd-trigger` carries `.kol-btn`, so every
+ * `.kol-btn.kol-tone-sunken` state rule matches it unless it says otherwise —
+ * and "REST AND OPEN ARE THE ONLY STATES" for a Dropdown trigger is a law
+ * written TWICE at the top of this file (2026-07-15, re-called 2026-08-09 and
+ * 2026-08-28). The atoms sheet excludes the trigger from all eight variant
+ * hovers; these tone rules did not, so the law held everywhere except the one
+ * tone the settings page uses. Repeatedly reported and repeatedly missed,
+ * because the exclusion was checked in `kol-components-atoms.css` and the
+ * offending rule lives here. */
 .kol-btn.kol-tone-sunken,
 .kol-icon-frame.kol-tone-sunken,
 .kol-theme-toggle.kol-tone-sunken {
   background-color: var(--kol-surface-sunken);
+  background-image: linear-gradient(var(--kol-shell-page-wash, transparent), var(--kol-shell-page-wash, transparent));
   border-color: transparent;
   color: var(--kol-fg-96);
 }
 @media (hover: hover) {
-  .kol-btn.kol-tone-sunken:not(.kol-btn-animate):not(:disabled):hover {
+  .kol-btn.kol-tone-sunken:not(.kol-btn-animate):not(:disabled):not(.kol-dd-trigger):hover {
     background-color: var(--kol-surface-sunken);
-    background-image: linear-gradient(var(--kol-fg-04), var(--kol-fg-04));
+    background-image: linear-gradient(var(--kol-fg-04), var(--kol-fg-04)), linear-gradient(var(--kol-shell-page-wash, transparent), var(--kol-shell-page-wash, transparent));
     color: var(--kol-fg-96);
   }
 }
-.kol-btn.kol-tone-sunken.kol-btn-pressed,
-.kol-btn.kol-tone-sunken:not(:disabled):active {
+.kol-btn.kol-tone-sunken.kol-btn-pressed:not(.kol-dd-trigger),
+.kol-btn.kol-tone-sunken:not(:disabled):not(.kol-dd-trigger):active {
   background-color: var(--kol-surface-sunken);
-  background-image: linear-gradient(var(--kol-fg-08), var(--kol-fg-08));
+  background-image: linear-gradient(var(--kol-fg-08), var(--kol-fg-08)), linear-gradient(var(--kol-shell-page-wash, transparent), var(--kol-shell-page-wash, transparent));
   color: var(--kol-fg-96);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kolkrabbi/kol-theme",
-  "version": "0.106.0",
+  "version": "0.108.0",
   "description": "KOL (Kolkrabbi) design-system tokens + base CSS — brand-neutral. The canonical token/cascade layer every other KOL package and consumer builds on.",
   "license": "MIT",
   "type": "module",