@justai/cuts 0.129.5 → 0.129.7

package/package.json

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

package/src/Preroll.astro

@@ -369,12 +369,29 @@ const safeId = "game-" + (id.toLowerCase().replace(/[^a-z0-9]+/g, "-").replace(/
    * half a second to fade - and every pause put a brief wave of darkness across the game itself.
    * Static costs nothing (the room is transparent outside playing) and cannot mistime. */
   .cut.kernel:has(#pr) { position: relative; z-index: 35; }
+  /* ── THE ROOM IS DARK DOT PAPER, NOT A BLACK FILM ───────────────────────────────────────────
+   * queries: theater dim flat colour · the dots disappear in the dark · blender dark theme ·
+   *          dot paper grid in theater mode
+   *
+   * The founder, looking at the first dim: *"dot paper grid'de dot kendini belli etmeyince bu
+   * sefer duz bir renk gibi algilaniyor"* — and pointing at the fix: 3dviewer's player, whose
+   * stage is Blender's own Theme Space grey, read out of a running Blender. A flat translucent
+   * black erased the ground's identity; a dark room should still be THE SAME PAPER with the
+   * lights down, the way Blender's viewport keeps its grid in the dark.
+   *
+   * So the layer carries its own lattice — the door's 24px dot grid, light-on-dark — over a
+   * neutral Blender-family dark. The opacity is high on purpose: the dots belong to THIS layer,
+   * and a translucent lattice over a busy page is noise, while a nearly-opaque one is a surface.
+   * The chrome beneath (the toolbar steps under at z 20) stays legible as shapes in a dark room. */
   .pr-room {
     position: fixed; inset: 0; z-index: 30;
-    background: #05070d; opacity: 0; pointer-events: none;
+    background:
+      radial-gradient(rgba(255, 255, 255, 0.07) 1px, transparent 1px) 0 0 / 24px 24px,
+      #262626;
+    opacity: 0; pointer-events: none;
     transition: opacity 0.5s var(--ease-out, ease-out);
   }
-  html[data-stage="playing"] .pr-room { opacity: 0.55; }
+  html[data-stage="playing"] .pr-room { opacity: 0.86; }
 </style>
 
 <script>

package/src/Toolbar.astro

@@ -457,16 +457,21 @@ 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. */
-  /* 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.5;
-    transition: opacity 0.4s var(--ease-out);
-  }
+  /* ── IN THE DARK, NOT DISABLED — how this row goes quiet while a game plays ─────────────────
+   * queries: toolbar looks disabled · faded but clickable · toolbar during a game · theater
+   *
+   * Three versions of quieting, each struck by the founder. Fading the elements was the last one:
+   * *"neden disable mis gibi gozukuyor ama tiklanabiliyor? tiklanabiliyorsa disable gibi
+   * gozukmemeli."* Right - reduced opacity IS the visual language of disabled, and nothing
+   * clickable may speak it.
+   *
+   * The answer was in the theater metaphor the whole time: in a dark cinema the seats are not
+   * disabled, they are in the dark. So the elements keep their full strength and the ROW STEPS
+   * UNDER THE ROOM'S DIM - below the .pr-room layer the stage protocol hangs over the page - and
+   * darkens with everything else in one coherent light change. The dim takes no pointer events,
+   * so every control underneath works exactly as it looks like it should: like chrome in a dark
+   * room, waiting. */
+  :global(html[data-stage="playing"]) .tb-slot { z-index: 20; }
   /* icon-only section nav — current cut highlighted */
   .tb-nav {
     display: grid; place-items: center; width: 38px; height: 36px;