@justai/cuts 0.129.3 → 0.129.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.129.3",
+  "version": "0.129.5",
   "description": "A persona's named parts \u2014 the page shell that holds them, and the cuts themselves.",
   "license": "UNLICENSED",
   "repository": {

package/src/Preroll.astro

@@ -505,6 +505,15 @@ const safeId = "game-" + (id.toLowerCase().replace(/[^a-z0-9]+/g, "-").replace(/
           }
           // The page is locked, so make sure what it is locked ON is the stage.
           if (playing) stage.scrollIntoView({ block: "nearest" });
+          // queries: space does nothing · keyboard not reaching the game · input bind · focus
+          //
+          // AND THE KEYBOARD GOES WITH THE STAGE. The play press happened in THIS document, so this
+          // document holds the focus — and every key the player presses lands in the shell while
+          // the game hears nothing. The founder, on the space bar: *"bu haldeyken klavyeden space
+          // tusunu bile almiyor. tum input game frame'e bind olmali."* Granting the stage IS the
+          // input handover, so the frame is focused with it — and again on pause's reversal, so a
+          // resumed game does not come back deaf.
+          if (playing) frame.focus();
           // The toolbar swaps its icons for the handle on this event — it owns its own row.
           document.dispatchEvent(new CustomEvent("justai:stage", { detail: { mode } }));
         };

package/src/Toolbar.astro

@@ -156,8 +156,6 @@ import BackToZone from "./BackToZone.astro";
 const {
   sectionsLabel, profileLabel, kernelLabel, postsLabel,
   files = true, filesLabel = "Files", kernelTitle, postsTitle, avatar = "/icon.svg", parent,
-  pauseLabel = "Pause",
-  fullscreenLabel = "Fullscreen",
 } = 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.
@@ -263,29 +261,19 @@ import AuthMount from "./AuthMount.astro";
              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" />
-        <!-- ── THE HANDLE — the stage protocol's one promise about this row ─────────────────────
-             queries: pause button in the toolbar · the way back while playing · stage controls ·
-                      fullscreen button · oyun icinde geri donus
+        <!-- queries: where did the pause button go · toolbar controls while playing · tb-stage
+             THE ROW CARRIES NO GAME CONTROLS, and it did for one version. Pause and fullscreen were
+             drawn HERE first — the "withdraw to a single handle" design — and the founder struck it:
+             *"pause ve fullscreen ux bilesenleri oyun icerisinde olmali degil mi? bizim game persona
+             toolbari ile de isimiz yok ki."* He is right twice. The player's eyes and thumbs are in
+             the frame, and a control in chrome faded to 16% is a control where nobody is looking; and
+             while a game plays, this row is furniture — furniture does not sprout transport controls.
 
-             THE SHELL DOES NOT DISAPPEAR. IT WITHDRAWS TO A SINGLE HANDLE, AND THAT HANDLE IS THE
-             WAY BACK. While a game is playing the section nav fades and goes inert, and these two
-             controls appear in the same row, in the same place — so the way back is where the way
-             around used to be. Hiding everything is a trap; hiding everything except the way out is
-             a stage.
-
-             The buttons only DISPATCH. The Preroll owns the bus, so it listens and asks the game;
-             the chrome is restored when the GAME announces paused, never optimistically — state has
-             one source and it is the game. Fullscreen is feature-detected in the script below:
-             absent rather than dead where the platform does not implement it, which is every
-             iPhone. -->
-        <span class="tb-stage" id="tbStage">
-          <button class="tb-nav tb-pausebtn" id="tbPause" type="button" aria-label={pauseLabel} title={pauseLabel}>
-            <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round"><path d="M9 3v18M15 3v18"/></svg>
-          </button>
-          <button class="tb-nav tb-fsbtn" id="tbFullscreen" type="button" aria-label={fullscreenLabel} title={fullscreenLabel} hidden>
-            <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M8 3H5a2 2 0 0 0-2 2v3M16 3h3a2 2 0 0 1 2 2v3M8 21H5a2 2 0 0 1-2-2v-3M16 21h3a2 2 0 0 0 2-2v-3"/></svg>
-          </button>
-        </span>
+             So the GAME draws pause and fullscreen in its own HUD language, and announces state over
+             the protocol. The escape from a broken game is not a shell button either: the shell asks
+             the game to pause whenever the tab hides, so leaving and returning restores the chrome —
+             the browser's own gesture, which no game can fail to have. The row's whole part while
+             playing is to fade, go inert, and come back when the game says paused. -->
       </div>
       <div class="tb-right">
         <slot name="toolbarRight" />
@@ -469,12 +457,14 @@ import AuthMount from "./AuthMount.astro";
    * Opacity and pointer-events here; the INERT that takes them out of the tab order is set in the
    * script, because CSS cannot. The transition matters more than it looks: chrome that snaps away
    * reads as breaking, chrome that withdraws reads as dimming the house lights. */
-  .tb-stage { display: none; align-items: center; gap: 2px; }
-  :global(html[data-stage="playing"]) .tb-stage { display: flex; }
+  /* QUIET, NOT DEAD. The first version faded the row to 16% and made it inert - a locked door.
+   * The founder's better idea: leave everything enabled, and USING any of it pauses the game -
+   * *"gitti chats'e tikladi. game state playing ise otomatik oyunu pause eder. daha smooth bir
+   * deneyim."* One tap instead of pause-then-tap, and the whole row becomes the way back. */
   :global(html[data-stage="playing"]) .tb-nav-group,
   :global(html[data-stage="playing"]) .tb-right,
   :global(html[data-stage="playing"]) .tb-title {
-    opacity: 0.16; pointer-events: none;
+    opacity: 0.5;
     transition: opacity 0.4s var(--ease-out);
   }
   /* icon-only section nav — current cut highlighted */
@@ -642,26 +632,29 @@ import AuthMount from "./AuthMount.astro";
   // 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.
-  // ── the stage handle — see the markup's comment for the design ────────────────────────────
-  // queries: pause button does nothing · fullscreen hidden on iphone · toolbar during a game
-  const tbStage = document.getElementById("tbStage");
-  if (tbStage) {
-    const fsBtn = document.getElementById("tbFullscreen") as HTMLButtonElement | null;
-    // Feature-detected, absent rather than dead: Element.requestFullscreen does not exist in
-    // Safari on iPhone (iPad has it), and a button that throws is worse than no button.
-    if (fsBtn && "requestFullscreen" in document.documentElement) fsBtn.hidden = false;
-    document.getElementById("tbPause")?.addEventListener("click", () =>
-      document.dispatchEvent(new CustomEvent("justai:pause-request")));
-    fsBtn?.addEventListener("click", () =>
-      document.dispatchEvent(new CustomEvent("justai:fullscreen-request")));
-    // The nav fades by CSS; inert is what CSS cannot do — out of the tab order and the
-    // accessibility tree, so a keyboard or a screen reader is not walking chrome the player left.
-    document.addEventListener("justai:stage", (e: any) => {
-      const playing = e?.detail?.mode === "playing";
-      document.querySelector(".tb-nav-group")?.toggleAttribute("inert", playing);
-      document.querySelector(".tb-right")?.toggleAttribute("inert", playing);
-    });
-  }
+  // ── the stage: the row stays LIVE, and using it pauses the game ───────────────────────────
+  // queries: toolbar during a game · tapping posts while playing · auto pause · data-stage-silent
+  //
+  // The row went inert for one version and the founder unlocked it: every control stays enabled,
+  // and touching ANY of them while a game is playing asks the game to pause first — so a player who
+  // reaches for the posts mid-flight gets a paused gull and the feed, in one tap. The event is not
+  // blocked: the action proceeds naturally while the pause lands beside it (a locked page still
+  // scrolls programmatically, so even the hash navigation works before the unlock).
+  //
+  // Declarative seam, as asked: an element that must NOT pause the game opts out by carrying
+  // `data-stage-silent` — on itself or any ancestor. Everything else pauses by default, because a
+  // rule with a default and an opt-out survives a fleet; a per-element opt-in is the third copy
+  // that forgets.
+  document.querySelector(".toolbar")?.addEventListener(
+    "click",
+    (e) => {
+      if (document.documentElement.dataset.stage !== "playing") return;
+      const hit = (e.target as Element | null)?.closest?.("a, button, select, [role=button]");
+      if (!hit || hit.closest("[data-stage-silent]")) return;
+      document.dispatchEvent(new CustomEvent("justai:pause-request"));
+    },
+    true,
+  );
 
   const bar = document.querySelector(".toolbar") as HTMLElement | null;
   const kt = bar?.dataset.kernelTitle;