@kolkrabbi/kol-theme 0.118.0 → 0.120.0

package/kol-components-atoms.css

@@ -173,12 +173,16 @@
  * 2026-08-01 — it brings its own box, border, colour set and states, so this
  * class stopped painting one. It used to hand-draw a bordered square around a
  * literal `×` CHARACTER, which is why the button had no hover, no focus ring
- * and no glyph. The inset is --kol-spacing-3, the rung that already carried
- * this value. */
+ * and no glyph.
+ * `right: 0` (FullscreenOverlayCloseIdiom, kol-chess 2026-09-01): the sheet
+ * hugs the consumer's panel, so a --kol-spacing-3 inset floated the X 12px
+ * inside the content column's right edge — lined up with nothing the fields
+ * below it establish. On the edge, the button's box sits on the same vertical
+ * as the controls under it. */
 .kol-overlay-close {
   position: absolute;
   top: var(--kol-spacing-3);
-  right: var(--kol-spacing-3);
+  right: 0;
   z-index: 10;
 }
 

package/kol-components-chess.css

@@ -354,8 +354,15 @@
   text-transform: uppercase;
 }
 
+/* sans-narrow BY NAME, not --kol-font-family-heading
+ * (ChessHeadingFontVarUndefined, kol-chess 2026-09-01): `heading` is a
+ * framework-tier brand seam (kol-brand-color.css) the theme never ships, so
+ * an app-shell consumer resolved it to nothing and every hero metric, title
+ * and chart heading fell to the inherited body font. sans-narrow is what the
+ * brand seam bound it to — same face where it worked, fixed where it did not.
+ * This applies to all 10 heading rules in this pack. */
 .board-playback__title {
-  font-family: var(--kol-font-family-heading);
+  font-family: var(--kol-font-family-sans-narrow);
   font-size: 1.2rem;
   letter-spacing: 0.06em;
   margin: 6px 0 4px;
@@ -422,7 +429,7 @@
 }
 
 .board-playback__value {
-  font-family: var(--kol-font-family-heading);
+  font-family: var(--kol-font-family-sans-narrow);
   font-size: 1.1rem;
   letter-spacing: 0.04em;
 }
@@ -530,7 +537,7 @@
 }
 
 .board-playback__avatar-name {
-  font-family: var(--kol-font-family-heading);
+  font-family: var(--kol-font-family-sans-narrow);
   font-size: 0.9rem;
   letter-spacing: 0.06em;
 }
@@ -590,7 +597,7 @@
 }
 
 .analysis-table__result {
-  font-family: var(--kol-font-family-heading);
+  font-family: var(--kol-font-family-sans-narrow);
   font-size: 0.85rem;
   letter-spacing: 0.08em;
   text-transform: uppercase;
@@ -750,7 +757,7 @@
 }
 
 .chess-hero-metric__value {
-  font-family: var(--kol-font-family-heading);
+  font-family: var(--kol-font-family-sans-narrow);
   font-size: 2rem;
   font-weight: 600;
   letter-spacing: -0.02em;
@@ -810,7 +817,7 @@
 }
 
 .chess-hero__title {
-  font-family: var(--kol-font-family-heading);
+  font-family: var(--kol-font-family-sans-narrow);
   font-size: 1rem;
   letter-spacing: 0.08em;
   text-transform: uppercase;
@@ -825,7 +832,7 @@
 }
 
 .chess-hero__value {
-  font-family: var(--kol-font-family-heading);
+  font-family: var(--kol-font-family-sans-narrow);
   font-size: 2.25rem;
   font-weight: 600;
   letter-spacing: -0.02em;
@@ -939,7 +946,7 @@
 }
 
 .chess-hero__side-value {
-  font-family: var(--kol-font-family-heading);
+  font-family: var(--kol-font-family-sans-narrow);
   font-size: 1.75rem;
   font-weight: 600;
   letter-spacing: -0.02em;
@@ -1065,7 +1072,7 @@
 }
 
 .chess-donut-chart__title {
-  font-family: var(--kol-font-family-heading);
+  font-family: var(--kol-font-family-sans-narrow);
   font-size: 0.85rem;
   letter-spacing: 0.08em;
   text-transform: capitalize;
@@ -1199,7 +1206,7 @@
 }
 
 .chess-stacked-bar-chart__title {
-  font-family: var(--kol-font-family-heading);
+  font-family: var(--kol-font-family-sans-narrow);
   font-size: 1.5rem;
   font-weight: 600;
   letter-spacing: -0.02em;

package/kol-components-dashboards.css

@@ -158,6 +158,25 @@
   }
 }
 
+/* Card subtitles — the WRAPPING secondary line (DashDetailWrapsWithoutLeading,
+ * kol-chess 2026-09-01). `.dash-detail` is line-height 1 — single-line chrome
+ * by the type protocol's fault line — and CardHeader was handing it full
+ * sentences that wrapped to three leading-less lines at 390. Same ramp and
+ * step, real leading; footers and labels keep `.dash-detail`. */
+.dash-subtitle {
+  font-family: var(--kol-font-family-mono);
+  font-weight: 400;
+  font-size: 10px;
+  line-height: 1.5;
+  color: var(--kol-surface-on-primary);
+}
+
+@container (min-width: 768px) {
+  .dash-subtitle {
+    font-size: 12px;
+  }
+}
+
 /* Chart axes, compact items, legends — 8px → 11px, regular weight */
 .dash-caption {
   font-family: var(--kol-font-family-mono);

package/kol-components-shell.css

@@ -97,8 +97,11 @@
  * be a second source of truth for it. And no `!important`: the rail reads its
  * own `--kol-shell-drawer-width` in drawer mode instead of the live rail token,
  * so nothing here is fighting an inline style. */
+/* FROM THE RIGHT (ShellDrawerOnRight, kol-chess 2026-09-01, user ruling: the
+ * close must not land mid-screen). NavRail pins itself right-0 in drawer mode;
+ * off-canvas is +100%. */
 [data-rail-drawer] .kol-shell-rail {
-  transform: translateX(-100%);
+  transform: translateX(100%);
   transition: transform 220ms cubic-bezier(0.4, 0, 0.2, 1);
 }
 [data-rail-drawer="open"] .kol-shell-rail {
@@ -109,34 +112,17 @@
 }
 
 /* Above the rail, so it stays tappable with the drawer open. */
+/* TOP-RIGHT, both states (ShellDrawerOnRight): with the drawer on the right
+ * the trigger and the open X share one corner at the screen edge — where the
+ * thumb is — so the 2026-08-31 travel rule is gone; it was the cure for the
+ * left side and nothing needs to move any more. */
 .kol-shell-drawer-trigger {
   position: fixed;
   top: 12px;
-  left: 12px;
+  right: 12px;
   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.118.0",
+  "version": "0.120.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",