@justai/cuts 0.70.0 → 0.72.0

package/package.json

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

package/src/ActionList.astro

@@ -45,7 +45,15 @@ const { title, note } = Astro.props;
 </div>
 
 <style>
+  /* queries: two action lists touching · no gap between groups · the second group sits on the first
+     THE BREAK IS THE GRAMMAR, so the component owns it.
+     A group carried its INTERNAL 7px and nothing between itself and the next one, which left the
+     break — the thing that separates "things you might do" from "the door with no way back" — to
+     whichever consumer remembered a wrapper. files did in one sheet and not in another, and the
+     second one read as one long list with a red row at the end.
+     `:last-child` so a lone group adds no trailing space it did not ask for. */
   .jal-group { display: flex; flex-direction: column; gap: 7px; }
+  .jal-group + .jal-group { margin-block-start: 22px; }
   /* Inset and grouped: the card is the group, and `overflow: hidden` is what lets a row's own
      background reach the rounded corner instead of squaring it off on press. */
   .jal {

package/src/Segmented.astro

@@ -126,8 +126,16 @@ const on = value && options.some((o) => o.value === value) ? value : options[0]?
        this is what makes it true for the eye. */
     isolation: isolate;
   }
+  /* queries: segmented control height · 44px touch target · the segments are too small
+     TWO SIZES, AND THE DIFFERENCE IS WHAT THE CONTROL IS.
+     `full` is a VIEW'S OWN SWITCH — a thumb's first target on the screen, so it meets the fleet's
+     44px like every row and every action does. `inline` is a TOOLBAR CHIP, sitting among other
+     chrome at chrome's size; forcing 44 there would make a toolbar taller than its content, which
+     is why iOS ships its own segmented controls shorter in exactly that position.
+     Found by a consumer's spec measuring 33px where its page promised 44 — a number the component
+     should have owned rather than each page discovering separately. */
   .jseg[data-width="full"] { display: flex; width: 100%; }
-  .jseg[data-width="full"] .jseg-item { flex: 1; }
+  .jseg[data-width="full"] .jseg-item { flex: 1; min-height: 44px; }
 
   .jseg-item {
     box-sizing: border-box;

package/src/Sheet.astro

@@ -186,6 +186,17 @@ const doneLabel = done === false ? null : (done ?? (detent === "large" ? "Done"
      Only one page is in the layout at a time, so the body's height is the CURRENT page's — which is
      what makes the sheet grow and shrink around the content the way a navigation stack does. The
      slide is 220ms and is skipped for reduced motion, where the pages simply swap. */
+  /* queries: the second sheet page appears BELOW the first · pushing shows both pages · the history
+     list is squeezed at the bottom · a page does not hide · consumer css beats the sheet
+     HIDING A PAGE IS A MECHANISM, NOT A SUGGESTION, so it is written where a class cannot outrank
+     it. `[data-sheet-page] { display: none }` is one attribute — specificity (0,1,0) — and any
+     consumer rule naming two classes beats it. files styles its detail page as `.pp .fd { display:
+     flex }`, which is ordinary and correct, and it meant the root page NEVER HID: pushing to the
+     versions drew them one under the other, so a person who tapped History got a cramped strip at
+     the bottom of a sheet still showing everything they had just left.
+     Qualified by the dialog it lives in, which raises this to (0,2,1) and keeps the rule honest —
+     a page outside a sheet is nobody's business here. */
+  :global(dialog [data-sheet-page]:not(.is-current):not(.is-popping)) { display: none; }
   :global([data-sheet-page]) { display: none; }
   :global([data-sheet-page].is-current) { display: block; animation: sheet-push 0.22s var(--ease-out) both; }
   :global([data-sheet-page].is-popping) { display: block; animation: sheet-pop 0.22s var(--ease-out) both; }