@justai/cuts 0.119.0 → 0.121.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.119.0",
+  "version": "0.121.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.26.0",
-    "@justai/ui": "^0.17.0",
+    "@justai/core": "^0.28.0",
+    "@justai/ui": "^0.19.0",
     "@justai/atrium": "^0.1.9"
   }
 }

package/src/Posts.astro

@@ -118,7 +118,7 @@ const vars = [
      connects every comment & reply (they're all replies to the post). ---- */
   /* the cut owns its own landing offset (was `#kernel, #posts { scroll-margin-top }` in each persona —
      which orphaned once #posts moved here and carried this component's scope cid instead of the persona's). */
-  .posts { border-block-start: 1px solid var(--border); scroll-margin-top: 82px; }
+  .posts { border-block-start: 1px solid var(--border); scroll-margin-top: 82px; scroll-margin-top: var(--shell-top, 82px); }
   /* A post is hoverable because it is a link to its own page, and the hover used to say so with a grey wash
      — `--text` at 3.5% — which reads as dimming rather than as lifting. It now uses the card material, so
      hovering a post looks like the same gesture as hovering a catalogue card.

package/src/Preroll.astro

@@ -209,9 +209,7 @@ const safeId = "game-" + (id.toLowerCase().replace(/[^a-z0-9]+/g, "-").replace(/
       radial-gradient(90cqw 52cqh at 8% -12%, color-mix(in srgb, var(--accent) 26%, transparent), transparent 62%),
       radial-gradient(76cqw 46cqh at 96% 4%, color-mix(in srgb, var(--accent) 12%, transparent), transparent 60%),
       radial-gradient(rgba(255, 255, 255, 0.055) 1px, transparent 1px) 0 0 / 24px 24px,
-      /* The room's floor and its walls are one colour: @justai/ui declares --game-ground and paints
-         the seam below the kernel with it, and a literal here would be a second black. */
-      var(--game-ground, #080b12);
+      #080b12;
     color: #f5f7fa;
   }
   .pr-door[hidden] { display: none; }

package/src/Toolbar.astro

@@ -82,8 +82,6 @@ interface Props {
   // half's default, which means copying core's `.pname` / `.handle` selectors into a second place
   // that nothing keeps in step. The strip is one line and its vocabulary should be one kind of
   // thing — names or sections, not one of each — so the API says so out loud.
-  kernelTitle?: string;
-  postsTitle?: string;
 
   // queries: toolbar shows a generic person icon · the profile icon is not my persona ·
   //          how do I put my own mark in the toolbar · avatar
@@ -155,7 +153,7 @@ interface Props {
 import BackToZone from "./BackToZone.astro";
 const {
   sectionsLabel, profileLabel, kernelLabel, postsLabel,
-  files = true, filesLabel = "Files", kernelTitle, postsTitle, avatar = "/icon.svg", parent,
+  files = true, filesLabel = "Files", avatar = "/icon.svg", parent,
 } = Astro.props;
 // A child's row answers UP to its parent, not out to the zone, and has no stream of its own — so
 // both default off the moment `parent` is given, rather than each consumer remembering to say so.
@@ -166,109 +164,108 @@ import AuthMount from "./AuthMount.astro";
 <!-- The two titles reach the script as data attributes rather than through `define:vars`, which would
      make this script inline and it has an import. Astro drops an attribute whose value is undefined,
      so a persona that passes neither leaves no trace in the markup at all. -->
-<header class="toolbar" data-kernel-title={kernelTitle} data-posts-title={postsTitle}>
-  <div class="tb-row">
-    <div class="tb-left">
-      {home && <BackToZone apex={apex} />}
-      <nav class="tb-nav-group" aria-label={sectionsLabel}>
-        {/* POSITION ONE OF A CHILD'S ROW: the persona this one is mounted inside. `/icon.svg` is the
-            parent's face here, because a child runs in the parent's origin — the same path, read from
-            a different address. `#kernel` rather than `/` so the way back lands on the parent's work
-            and not on its biography, which is where a person who came from there was standing. */}
-        {parent && (
-          <a class="tb-nav tb-mark" id="navParent" href={parent.href ?? "/#kernel"} aria-label={parent.label ?? "Home"} title={parent.label ?? "Home"}>
-            <img src={parent.icon ?? "/icon.svg"} alt="" width="20" height="20" loading="lazy" decoding="async" />
+<header class="toolbar">
+    <div class="tb-row">
+      <div class="tb-left">
+        {home && <BackToZone apex={apex} />}
+        <nav class="tb-nav-group" aria-label={sectionsLabel}>
+          {/* POSITION ONE OF A CHILD'S ROW: the persona this one is mounted inside. `/icon.svg` is the
+              parent's face here, because a child runs in the parent's origin — the same path, read from
+              a different address. `#kernel` rather than `/` so the way back lands on the parent's work
+              and not on its biography, which is where a person who came from there was standing. */}
+          {parent && (
+            <a class="tb-nav tb-mark" id="navParent" href={parent.href ?? "/#kernel"} aria-label={parent.label ?? "Home"} title={parent.label ?? "Home"}>
+              <img src={parent.icon ?? "/icon.svg"} alt="" width="20" height="20" loading="lazy" decoding="async" />
+            </a>
+          )}
+          {/* THE PROFILE ICON IS THE PERSONA'S OWN FACE. Always — the founder's rule, and app.zone and
+              qr had already settled it while thirteen siblings still showed a generic bust.
+  
+              The bust is gone rather than demoted. A fallback that renders something plausible is how a
+              persona ships wearing nobody's face for months: nothing is broken, nothing is red, and the
+              only reader who notices is somebody comparing two personas side by side. `/icon.svg` is
+              not a guess — it is the ecosystem's one-face rule, the same path `persona.yml` declares
+              and the registry stores.
+  
+              `tb-mark` is set whichever way the face arrives, because it is what the sizing rule looks
+              for: a mark runs to the edge of its viewBox and a glyph does not, so they need different
+              boxes to put the same ink on screen. */}
+          {/* `tb-mark` says "a solid MARK is in this box" — it is what the sizing rule looks for, and a
+              mark runs to the edge of its viewBox where a stroke glyph sits inside 75% of one. A
+              persona's face is always a mark, so a persona always carries the class.
+  
+              A CHILD IS THE OTHER CASE, and it was measured rather than assumed: files passes a stroke
+              folder, and with `tb-mark` on it, it rendered at 19px beside a 25.33px bolt — one size
+              smaller, which is exactly the defect the 25.33 rule exists to remove. So in child mode the
+              slotted icon takes the GLYPH box and the row reads level. A child that draws a solid mark
+              instead should say so in its own CSS; every child in the fleet draws a glyph today. */}
+          <a class:list={["tb-nav", { "tb-mark": !parent }]} id="navProfile" href="#profile" aria-label={profileLabel} title={profileLabel}>
+            {/* A CHILD MUST PASS ITS OWN MARK. The default `/icon.svg` is the face of whoever owns this
+                origin — right for a persona, and its PARENT for a child, which would put the same
+                picture in two places and say nothing in either. So when `parent` is given there is no
+                fallback: a child that passes nothing renders an empty box, which is a defect somebody
+                sees, rather than a duplicate face, which is a defect nobody reports. */}
+            {Astro.slots.has("profileIcon")
+              ? <slot name="profileIcon" />
+              : (!parent && <img src={avatar} alt="" width="20" height="20" loading="lazy" decoding="async" />)}
           </a>
-        )}
-        {/* THE PROFILE ICON IS THE PERSONA'S OWN FACE. Always — the founder's rule, and app.zone and
-            qr had already settled it while thirteen siblings still showed a generic bust.
-
-            The bust is gone rather than demoted. A fallback that renders something plausible is how a
-            persona ships wearing nobody's face for months: nothing is broken, nothing is red, and the
-            only reader who notices is somebody comparing two personas side by side. `/icon.svg` is
-            not a guess — it is the ecosystem's one-face rule, the same path `persona.yml` declares
-            and the registry stores.
-
-            `tb-mark` is set whichever way the face arrives, because it is what the sizing rule looks
-            for: a mark runs to the edge of its viewBox and a glyph does not, so they need different
-            boxes to put the same ink on screen. */}
-        {/* `tb-mark` says "a solid MARK is in this box" — it is what the sizing rule looks for, and a
-            mark runs to the edge of its viewBox where a stroke glyph sits inside 75% of one. A
-            persona's face is always a mark, so a persona always carries the class.
-
-            A CHILD IS THE OTHER CASE, and it was measured rather than assumed: files passes a stroke
-            folder, and with `tb-mark` on it, it rendered at 19px beside a 25.33px bolt — one size
-            smaller, which is exactly the defect the 25.33 rule exists to remove. So in child mode the
-            slotted icon takes the GLYPH box and the row reads level. A child that draws a solid mark
-            instead should say so in its own CSS; every child in the fleet draws a glyph today. */}
-        <a class:list={["tb-nav", { "tb-mark": !parent }]} id="navProfile" href="#profile" aria-label={profileLabel} title={profileLabel}>
-          {/* A CHILD MUST PASS ITS OWN MARK. The default `/icon.svg` is the face of whoever owns this
-              origin — right for a persona, and its PARENT for a child, which would put the same
-              picture in two places and say nothing in either. So when `parent` is given there is no
-              fallback: a child that passes nothing renders an empty box, which is a defect somebody
-              sees, rather than a duplicate face, which is a defect nobody reports. */}
-          {Astro.slots.has("profileIcon")
-            ? <slot name="profileIcon" />
-            : (!parent && <img src={avatar} alt="" width="20" height="20" loading="lazy" decoding="async" />)}
-        </a>
-        {/* THE KERNEL IS ALWAYS THE BOLT. The founder's rule, and it is the shell's to draw rather
-            than the persona's to remember.
-
-            It was a bare `<slot name="kernelIcon" />` with NO fallback, which is the worst shape a
-            slot can have: a persona that passed nothing shipped a live, invisible tap target where
-            every sibling showed a mark — no error, no warning, and visible only beside another
-            persona. Fourteen of fifteen passed their own drawing instead, so the row said something
-            different in every repo about the same thing.
-
-            The bolt says WHAT THE SECTION IS — the persona's one job, its live surface — and the
-            profile icon two places to the left already says WHO. An icon that repeats the identity
-            spends the row's only distinction on a thing the row has already said. */}
-        <a class="tb-nav" id="navKernel" href="#kernel" aria-label={kernelLabel} title={kernelLabel}>
-          <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12.9 3L5.7 13.35h5.4L10.2 21l8.1-10.8h-5.4l.9-7.2z"/></svg>
-        </a>
-        {posts && (
-          <a class="tb-nav" id="navPosts" href="#posts" aria-label={postsLabel} title={postsLabel}>
-            <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 11.5a8.4 8.4 0 0 1-9 8.3 9.6 9.6 0 0 1-4-.9L3 21l1.1-5A8.4 8.4 0 1 1 21 11.5z"/></svg>
+          {/* THE KERNEL IS ALWAYS THE BOLT. The founder's rule, and it is the shell's to draw rather
+              than the persona's to remember.
+  
+              It was a bare `<slot name="kernelIcon" />` with NO fallback, which is the worst shape a
+              slot can have: a persona that passed nothing shipped a live, invisible tap target where
+              every sibling showed a mark — no error, no warning, and visible only beside another
+              persona. Fourteen of fifteen passed their own drawing instead, so the row said something
+              different in every repo about the same thing.
+  
+              The bolt says WHAT THE SECTION IS — the persona's one job, its live surface — and the
+              profile icon two places to the left already says WHO. An icon that repeats the identity
+              spends the row's only distinction on a thing the row has already said. */}
+          <a class="tb-nav" id="navKernel" href="#kernel" aria-label={kernelLabel} title={kernelLabel}>
+            <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12.9 3L5.7 13.35h5.4L10.2 21l8.1-10.8h-5.4l.9-7.2z"/></svg>
+          </a>
+          {posts && (
+            <a class="tb-nav" id="navPosts" href="#posts" aria-label={postsLabel} title={postsLabel}>
+              <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M21 11.5a8.4 8.4 0 0 1-9 8.3 9.6 9.6 0 0 1-4-.9L3 21l1.1-5A8.4 8.4 0 1 1 21 11.5z"/></svg>
+            </a>
+          )}
+          <slot name="navExtra" />
+        </nav>
+        {files && (
+          // queries: files icon in the toolbar · how do I reach my files from a persona · the folder
+          //          in the toolbar · why is files not in the section nav
+          //
+          // THE PERSONA'S FILES, ONE TAP FROM ANYWHERE IN IT.
+          //
+          // Until this, the only way into `<persona>/files` was to be asked for a file — the room
+          // where your things live could be entered only by a persona's invitation, which is exactly
+          // backwards for a room that is yours.
+          //
+          // OUTSIDE the sections nav, and deliberately: profile, kernel and posts are parts of THIS
+          // page and their links are fragments. `/files` is a different document — a place, not a
+          // section — and putting a navigation to elsewhere inside `<nav aria-label="sections">`
+          // would tell a screen reader it is one of them. Same reasoning the `leftExtra` slot below
+          // already carries, which is why this sits beside it rather than in the group above.
+          //
+          // ON BY DEFAULT, because the edge mounts `/files` on EVERY persona host: a persona that had
+          // to opt in would be a persona whose files exist and cannot be found. One bump here reaches
+          // the whole fleet, which is the only shape that survives a thousand of them.
+          <a class="tb-nav tb-files" id="navFiles" href="/files" aria-label={filesLabel} title={filesLabel}>
+            <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M3 7.5A1.5 1.5 0 0 1 4.5 6h4L11 8.5h8.5A1.5 1.5 0 0 1 21 10v7a1.5 1.5 0 0 1-1.5 1.5h-15A1.5 1.5 0 0 1 3 17z"/></svg>
           </a>
         )}
-        <slot name="navExtra" />
-      </nav>
-      {files && (
-        // queries: files icon in the toolbar · how do I reach my files from a persona · the folder
-        //          in the toolbar · why is files not in the section nav
-        //
-        // THE PERSONA'S FILES, ONE TAP FROM ANYWHERE IN IT.
-        //
-        // Until this, the only way into `<persona>/files` was to be asked for a file — the room
-        // where your things live could be entered only by a persona's invitation, which is exactly
-        // backwards for a room that is yours.
-        //
-        // OUTSIDE the sections nav, and deliberately: profile, kernel and posts are parts of THIS
-        // page and their links are fragments. `/files` is a different document — a place, not a
-        // section — and putting a navigation to elsewhere inside `<nav aria-label="sections">`
-        // would tell a screen reader it is one of them. Same reasoning the `leftExtra` slot below
-        // already carries, which is why this sits beside it rather than in the group above.
-        //
-        // ON BY DEFAULT, because the edge mounts `/files` on EVERY persona host: a persona that had
-        // to opt in would be a persona whose files exist and cannot be found. One bump here reaches
-        // the whole fleet, which is the only shape that survives a thousand of them.
-        <a class="tb-nav tb-files" id="navFiles" href="/files" aria-label={filesLabel} title={filesLabel}>
-          <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M3 7.5A1.5 1.5 0 0 1 4.5 6h4L11 8.5h8.5A1.5 1.5 0 0 1 21 10v7a1.5 1.5 0 0 1-1.5 1.5h-15A1.5 1.5 0 0 1 3 17z"/></svg>
-        </a>
-      )}
-      <!-- beside the section nav, but deliberately OUTSIDE it: a link that is not a section of this
-           page (justai.pro carries app.zone's mark here). Keeping it out of <nav aria-label=sections>
-           is the a11y half of the reason it is its own slot. -->
-      <slot name="leftExtra" />
+        <!-- beside the section nav, but deliberately OUTSIDE it: a link that is not a section of this
+             page (justai.pro carries app.zone's mark here). Keeping it out of <nav aria-label=sections>
+             is the a11y half of the reason it is its own slot. -->
+        <slot name="leftExtra" />
+      </div>
+      <div class="tb-right">
+        <slot name="toolbarRight" />
+        <slot name="langPicker" />
+        <AuthMount />
+      </div>
     </div>
-    <div class="tb-right">
-      <slot name="toolbarRight" />
-      <slot name="langPicker" />
-      <AuthMount />
-    </div>
-  </div>
-  <div class="tb-title" id="tbTitle"><span class="tb-title-text" id="tbTitleText"></span></div>
-</header>
+  </header>
 
 <style>
   /* ---- app toolbar — sticky to the top of the active region (kernel + posts); it never
@@ -328,54 +325,23 @@ 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.
+  /* queries: where is the title strip · tb-title · the persona's name under the icons · tbTitle
    *
-   * 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.
+   * ── THERE IS NO SECONDARY STRIP, AND THAT IS A DECISION ──────────────────────────────────
    *
-   * 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.
+   * A second row under the icons carried the current cut's name and opened over 0.35s. It cost more
+   * than it said. `position: sticky` never leaves flow, so the row's LIVE height positioned every
+   * section beneath it — 52 shut, 78 open — while anything that measured the shell had to freeze one
+   * of those two numbers and was therefore wrong in the other state. That gap is a band of the next
+   * section above the fold; on a game persona, whose kernel is an EXACT height, it is on the glass.
+   * It also coupled the scroll spy to the layout: the spy decided which cut was current, that opened
+   * the strip, the strip moved the page, and the spy read the page it had just moved.
    *
-   * 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); }
-  /* 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; }
+   * The founder's ruling, 2026-08-06: *"secondary şeridi tamamen kaldır. net karar."* So the bar is
+   * one row and one height, always. Nothing above the kernel changes size, and every derivation that
+   * existed to survive that change is gone with it — `--tb-strip`, the slot that reserved a constant
+   * box, the painted band that filled the reserve, and the probe that measured the strip before it
+   * opened. The name is on the profile, which is where a name belongs. */
   /* nav lives on the left, beside the back affordance — the middle is intentionally empty */
   .tb-left { display: flex; align-items: center; gap: 2px; min-width: 0; }
   .tb-nav-group { display: flex; align-items: center; gap: 2px; }
@@ -542,15 +508,6 @@ import AuthMount from "./AuthMount.astro";
   const ownMark = document.querySelector("#navProfile img");
   if (ownMark) adoptMark({ id: "navProfile" });
 
-  // Both or neither — see the props above. When both are set the strip names the SECTIONS; core's
-  // default, which names the persona and its handle, is left entirely alone otherwise. Nothing here
-  // reproduces that default, which is the point: `.pname` and `.handle` stay core's business.
-  const bar = document.querySelector(".toolbar") as HTMLElement | null;
-  const kt = bar?.dataset.kernelTitle;
-  const pt = bar?.dataset.postsTitle;
-  personaScroll(
-    kt && pt
-      ? { titleFor: (id: string) => (id === "kernel" ? kt : id === "posts" ? pt : "") }
-      : undefined,
-  );
+  // No titleFor: the bar has one row and no strip to name anything in. See the note in the styles.
+  personaScroll();
 </script>