@kolkrabbi/kol-theme 0.107.0 → 0.109.0

package/kol-components-molecules.css

@@ -1324,7 +1324,16 @@
  * 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
+/* ⚠️ `SunkenWellEatenByPageWash` IS NOT SOLVED HERE — see the ticket.
+ * On 2026-08-30 these rules briefly painted `--kol-shell-page-wash` as a
+ * background layer so the well would track a washed page. That was the wrong
+ * layer (user: *"we are talking about components, wash affects background"*):
+ * a control has no business reproducing a page-level film, and portalling
+ * proved it — `.kol-dd-panel` renders at document.body, could not inherit the
+ * property, and drew a different colour from its own trigger. Reverted.
+ * The collision is a PAGE/token question and belongs there.
+ *
+ * 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**:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kolkrabbi/kol-theme",
-  "version": "0.107.0",
+  "version": "0.109.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",