@kolkrabbi/kol-theme 0.114.0 → 0.116.0

package/kol-animation.css

@@ -279,12 +279,21 @@
  * showed nothing at 3% while dark UI screenshots beside them read correctly.
  * The card publishes `--kol-card-feature-zoom` from its `zoom` prop; 1.03 is
  * the fallback, so nothing moves for anyone who does not set it. */
-.kol-card-feature:hover .kol-card-feature-visual {
+/* ONE TREATMENT, TWO WAYS IN (CardSetInViewAttention, kol-website 2026-08-31).
+ * `data-attention` is stamped by the card when it holds the viewport's centre on
+ * a coarse pointer, and it is added to the SAME rule the hover uses rather than
+ * given rules of its own — two parallel sets would drift, and the whole reason
+ * this state exists is that variance was already costing more than the
+ * behaviour. On a phone a card is an anchor: a tap navigates, so hover was never
+ * reachable and the zoom simply never fired. */
+.kol-card-feature:hover .kol-card-feature-visual,
+.kol-card-feature[data-attention] .kol-card-feature-visual {
   transform: scale(var(--kol-card-feature-zoom, 1.03));
 }
 @media (prefers-reduced-motion: reduce) {
   .kol-card-feature-visual { transition: none; }
-  .kol-card-feature:hover .kol-card-feature-visual { transform: none; }
+  .kol-card-feature:hover .kol-card-feature-visual,
+  .kol-card-feature[data-attention] .kol-card-feature-visual { transform: none; }
 }
 
 /* Media hover zoom — opt-in via `mediaHover` (SectionSplit ruling, 2026-08-15).

package/kol-components-shell.css

@@ -110,6 +110,27 @@
   z-index: calc(var(--kol-z-sticky) + 2);
   width: 32px;
   height: 32px;
+  transition: transform 220ms cubic-bezier(0.4, 0, 0.2, 1);
+}
+
+/* THE TRIGGER RIDES THE DRAWER'S TRAILING EDGE WHEN OPEN (device report from
+ * kol-chess, 2026-08-31 — user: "menu is on the wrong side it overlaps close
+ * button when open"). Fixed at 12/12 it sat INSIDE the drawer it opens: the
+ * drawer spans 0–240 from the same edge, so the close × was drawn on top of the
+ * rail's own logomark row, both in the same 32px. It stayed clickable — z-order
+ * was right, and the scrim and Escape both closed — so it read as "the close
+ * button is gone" rather than as a trap. Unreadable, not unusable.
+ *
+ * One transform, no new markup: the control stays where the thumb last touched
+ * it and does not need NavRail to grow a close row of its own. Not moved to the
+ * right permanently — a trigger that changes corner between states is worse than
+ * one that travels. */
+[data-rail-drawer="open"] .kol-shell-drawer-trigger {
+  transform: translateX(var(--kol-shell-drawer-width, 240px));
+}
+
+@media (prefers-reduced-motion: reduce) {
+  .kol-shell-drawer-trigger { transition: none; }
 }
 
 .kol-shell-drawer-scrim {

package/package.json

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