@justai/cuts 0.113.0 → 0.115.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.113.0",
+  "version": "0.115.0",
   "description": "A persona's named parts \u2014 the page shell that holds them, and the cuts themselves.",
   "license": "UNLICENSED",
   "repository": {
@@ -41,8 +41,8 @@
     "access": "public"
   },
   "dependencies": {
-    "@justai/core": "^0.23.0",
-    "@justai/ui": "^0",
+    "@justai/core": "^0.25.0",
+    "@justai/ui": "^0.15.0",
     "@justai/atrium": "^0.1.9"
   }
 }

package/src/Toolbar.astro

@@ -328,8 +328,52 @@ import AuthMount from "./AuthMount.astro";
   @media (min-width: 640px) { .toolbar { margin-inline: -28px; padding-inline: 28px; } }
   /* icons row + the scroll-reactive title strip below it */
   .tb-row { display: flex; align-items: center; justify-content: space-between; gap: 8px; }
+  /* queries: --tb-strip · the title strip's height · the toolbar changes height · 26px ·
+   *          the kernel is 26px short · the game frame does not reach the fold
+   *
+   * ── THE ONE NUMBER THAT MAKES THIS ROW'S HEIGHT A MOVING TARGET, DECLARED SO IT CAN BE READ ──
+   *
+   * The strip opens and closes over 0.35s, so `.toolbar`'s height is anywhere in a 26px range at any
+   * given moment — and anything that measures the row and feeds a LAYOUT with it is sampling an
+   * animation. `--shell-top` did exactly that and the kernel's height came out 26px short whenever
+   * the page happened to be measured with the strip open, which is to say whenever somebody opened
+   * the persona at #kernel. It reads as a strip of the next section showing above the fold.
+   *
+   * So the number is a custom property rather than a literal: this rule uses it, and @justai/core's
+   * `personaScroll` reads it to compute the row's EXPANDED height without waiting for or racing the
+   * transition — `toolbar - strip` is the row, and the row plus this is what the bar will be. One
+   * declaration, two readers, and nothing samples a moving value. */
+  .toolbar { --tb-strip: 26px; }
+  /* queries: the bar grows after load · why does the strip animate on arrival · data-motion ·
+   *          first paint animation · can this transition wait for the first interaction
+   *
+   * ── THE TRANSITION IS ALSO A DAMPER, WHICH IS WHY IT CANNOT SIMPLY WAIT ─────────────────────
+   *
+   * The founder asked the obvious and right question: *"şu geçiş süresi güzel — ama neden bu özellik
+   * kullanıcının ilk interaction'ından sonra aktif edilmiyor?"* A persona lands on its kernel, so the
+   * strip's correct state on the first frame is open; animating into it grows the bar 26px just after
+   * the page appears, which is a glitch nobody asked for.
+   *
+   * IT WAS TRIED, AND IT BREAKS SOMETHING ELSE. Gated behind a `data-motion` flag set on the first
+   * pointer/key/wheel, the strip snaps open during the landing — and that 26px arrives in a SINGLE
+   * frame, inside `#below`, while the scroll spy is deciding which cut is active. That is the
+   * bistable oscillator `personaScroll` documents at length: the spy measures a page its own output
+   * moved. Measured: with the gate in place, `#navProfile` no longer navigates — the page re-asserts
+   * the kernel and stays. The 0.35s is not only easing; it is what keeps that step out of one frame.
+   *
+   * SO THE HEIGHT IS NEVER READ INSTEAD. `--shell-top` is computed as `row + --tb-strip` — the row
+   * being the bar minus whatever the strip currently is, which is the same number at every frame of
+   * the transition. Nothing samples the animation, so nothing depends on when it was sampled.
+   *
+   * The real fix for the founder's question is a toolbar whose height does not change at all: reserve
+   * the strip's space always and fade only its content. That removes the feedback at the source and
+   * makes the gate free — and it is a fleet-wide design decision about how the bar looks at the
+   * profile, so it is his to take rather than one to slip in. */
   .tb-title { display: flex; align-items: center; height: 0; overflow: hidden; opacity: 0; transition: height 0.35s var(--ease-out), opacity 0.25s var(--ease-out); }
-  .tb-title.show { height: 26px; opacity: 1; }
+  /* The fallback is not decoration: the token is declared on `.toolbar` and consumed here, which is
+     a different selector — so the framework's own token spec reads it as ungrounded and is right to.
+     A rule that silently collapses to `height: 0` would close the strip and say nothing. */
+  .tb-title.show { height: 26px; height: var(--tb-strip, 26px); opacity: 1; }
   .tb-title-text { font-size: var(--fs-sm); font-weight: 600; letter-spacing: -0.01em; color: var(--text); white-space: nowrap; overflow: hidden; text-overflow: ellipsis; transition: opacity 0.16s var(--ease-out); }
   .tb-title-text.fade { opacity: 0; }
   /* nav lives on the left, beside the back affordance — the middle is intentionally empty */