@kolkrabbi/kol-shell 0.18.0 → 0.19.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kolkrabbi/kol-shell",
-  "version": "0.18.0",
+  "version": "0.19.1",
   "private": false,
   "description": "KOL application shell — fixed 48px NavRail + AppShell layout root, PageShell/PageHeader scaffolds, ContentFilters catalog organism, GridCard, SettingsScaffold, WalkthroughPanel, ShortcutsOverlay. App chrome (kol-framework owns site chrome). Nav items, content, shortcuts and settings are consumer-injected. Sits above @kolkrabbi/kol-{theme,component,framework}.",
   "license": "MIT",
@@ -22,8 +22,8 @@
   "devDependencies": {
     "@kolkrabbi/kol-component": "^0.128.0",
     "@kolkrabbi/kol-framework": "^0.35.0",
-    "@kolkrabbi/kol-icons": "^0.24.0",
-    "@kolkrabbi/kol-theme": "^0.89.0"
+    "@kolkrabbi/kol-icons": "^0.25.0",
+    "@kolkrabbi/kol-theme": "^0.94.0"
   },
   "files": [
     "src",

package/src/AppShell.jsx

@@ -45,7 +45,9 @@ import TouchDeviceOverlay, { useTouchPrimary } from './TouchDeviceOverlay.jsx'
  *                                        localStorage `kol-desktop` is '1' (fxr's gate); `overlay` keeps the shell and
  *                                        mounts TouchDeviceOverlay once (monitor's)
  * @param {string}  props.appName       TouchDeviceOverlay's subject
- * @param {boolean} props.navKeys       Option+1…9 navigates to `items[n-1].path` through `onNavigate` — the
+ * @param {boolean} props.navKeys       Option+1…9 navigates to the rail's nth ROW through `onNavigate` — with a
+ *                                        `logomark` that is the mark ('/') then the items, which is the order on
+ *                                        screen (AppShellNavKeysHomeFirst, 2026-08-28); without one, `items[n-1]`. The
  *                                        rail-order counterpart of `railToggleKey` (AppShellNavKeys, kol-monitor
  *                                        2026-08-28 — user: "make command or alt 1234 go from home 1 2 3 4 in the
  *                                        sidenav without clicking"). Option, not Command: ⌘1–9 is the browser's
@@ -95,7 +97,21 @@ export default function AppShell({
     return () => window.removeEventListener('keydown', onKey)
   }, [railToggleKey])
 
-  /* Option+digit → the rail item in that position (never while typing) */
+  /* Option+digit → the rail ROW in that position (never while typing).
+   *
+   * THE MARK IS ROW 1 (AppShellNavKeysHomeFirst, kol-monitor 2026-08-28 — user:
+   * "alt 1 skips home and goes straight to 2"). 0.12.0 navigated to
+   * `items[n - 1]`, but the rail's first row is the LOGOMARK, which `NavRail`
+   * renders above the items and wires to '/'. So ⌥1 landed on the second rung
+   * and every key after it was off by one, with Home having no key at all —
+   * against the sentence that asked for the feature, quoted in the prop's own
+   * docblock above: "make command or alt 1234 go from HOME 1 2 3 4". Home was
+   * position 1 in the ask; the implementation counted a list it was never in.
+   *
+   * With a `logomark`, the order is the order you see: the mark, then the items.
+   * Without one, `items[n - 1]` exactly as before, so an app that renders no
+   * mark is untouched. */
+  const navPaths = (logomark ? ['/'] : []).concat((items ?? []).map((i) => i?.path)).filter(Boolean)
   useEffect(() => {
     if (!navKeys) return undefined
     const onKey = (e) => {
@@ -103,14 +119,14 @@ export default function AppShell({
       if (!m || !e.altKey || e.metaKey || e.ctrlKey) return
       const t = e.target
       if (t?.isContentEditable || /^(INPUT|TEXTAREA|SELECT)$/.test(t?.tagName)) return
-      const item = items?.[Number(m[1]) - 1]
-      if (!item?.path) return
+      const path = navPaths[Number(m[1]) - 1]
+      if (!path) return
       e.preventDefault()
-      onNavigate?.(item.path)
+      onNavigate?.(path)
     }
     window.addEventListener('keydown', onKey)
     return () => window.removeEventListener('keydown', onKey)
-  }, [navKeys, items, onNavigate])
+  }, [navKeys, navPaths.join('\u0000'), onNavigate]) // eslint-disable-line react-hooks/exhaustive-deps
 
   let wantsDesktop = false
   try { wantsDesktop = typeof localStorage !== 'undefined' && localStorage.getItem('kol-desktop') === '1' } catch { /* storage blocked */ }

package/src/PageHeader.jsx

@@ -49,10 +49,25 @@ export default function PageHeader({ eyebrow, title, subtitle, actions, subtitle
   const roles = TITLE[voice] ?? TITLE.sans
   const h1 = <h1 className={`text-fg-96 ${titleClass ?? roles[size] ?? roles.md}`}>{title}</h1>
   const lede = subtitle && <p className="text-oq-64 kol-mono-14 min-w-0" style={{ marginTop: actions ? undefined : 12, maxWidth: subtitleMaxWidth }}>{subtitle}</p>
-  /* the cluster shares a baseline row with the lede (or the title): flexbox
-     exposes a flex item's FIRST baseline, so putting them in one row is the
-     one way to land on the subtitle's line rather than the h1's */
-  const cluster = actions && <div className="flex items-center gap-4 shrink-0">{actions}</div>
+  /* The cluster shares a baseline row with the lede (or the title): flexbox
+     exposes a flex item's FIRST baseline, so putting them in one row is the one
+     way to land on the subtitle's line rather than the h1's.
+     
+     AND IT CONTRIBUTES NO HEIGHT (PageHeaderActionsGrowsBlock, kol-fxr
+     2026-08-28). A flex row takes its tallest child, so a cluster of `sm`
+     controls (28px since kol-theme 0.90.0) against a one-line `kol-mono-14`
+     lede (18px) made the masthead 10px taller — measured, monitor's `/` at 65.2
+     against fxr's `/settings` at 75.2 with identical titles. The masthead is the
+     one block every page of an app shares, so a page with a control cluster sat
+     10px lower than every page without one, with no way to opt out.
+     
+     `h-0` + `self-center` is the fix and it is not a magic number: a zero-height
+     box centred on the row makes the children overflow it symmetrically, so the
+     row's height is the TEXT's and the cluster is free at any rung (the gap is
+     10px at `sm`, 14 at `md` — a constant would have been wrong). Horizontal
+     layout is untouched: the box still takes its width, so `justify-between`
+     holds and a long lede cannot run under the controls. */
+  const cluster = actions && <div className="flex items-center gap-4 shrink-0 h-0 self-center">{actions}</div>
   return (
     /* the block owns its own rhythm — margins inline, never in a shared type
        class, which leaks estate-wide (ShellHeaderFilterRefinements, 2026-08-15) */