@justai/cuts 0.143.0 → 0.145.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.143.0",
+  "version": "0.145.0",
   "description": "A persona's named parts — the page shell that holds them, and the cuts themselves.",
   "license": "UNLICENSED",
   "repository": {
@@ -41,7 +41,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@justai/core": "^0.37.0",
+    "@justai/core": "^0.38.0",
     "@justai/ui": "^0.26.0",
     "@justai/atrium": "^0.1.9"
   },

package/src/ConfirmSheet.astro

@@ -16,6 +16,13 @@ import "./ground.css";
 //   something can end, the safe choice wears the most confident face. iOS system red for
 //   destruction. This is /me's "Erase everything?".
 //
+//   A THIRD CHOICE, when the safe answer is not "do nothing" (`safeActionLabel`) — Apple's own
+//   multi-action sheet. Some destructive questions have a way OUT of the loss rather than only a
+//   way around it: "your work isn't saved yet" is answered best by saving it, not by cancelling and
+//   then hunting for the Save button. That action joins the grouped card ABOVE the destructive one,
+//   because a sheet reads top to bottom and the preserving path is the one to meet first. Cancel
+//   stays detached and boldest — the anatomy does not change, it gains one row.
+//
 //   ASK (`ask` prop) — the alert/ATT genre, for INVITATIONS: both choices live INSIDE the grouped
 //   card, stacked; the action wears the preferred bold face (Apple's preferredAction) and takes
 //   the focus; the safe choice sits beneath it in calm regular weight — equal size, equal tap,
@@ -61,10 +68,19 @@ interface Props {
    *  remembered as a choice, so the chosen no is stored while a slip-away stores nothing and the
    *  ask returns next visit. */
   cancelValue?: string;
+  /** Optional THIRD choice: an action that PRESERVES rather than ends, placed above the main action
+   *  inside the grouped card and painted as the preferred path. Omit it and the sheet is exactly
+   *  what it always was — same DOM, same ids, same returnValues. */
+  safeActionLabel?: string;
+  /** What returnValue that third choice reports. Default "safe": three answers need three words. */
+  safeActionValue?: string;
   /** Anything else (data-* attributes, aria overrides) lands on the <dialog> itself. */
   [key: string]: unknown;
 }
-const { id, title, body, actionLabel, cancelLabel, destructive = false, ask = false, cancelValue = "", ...rest } = Astro.props;
+const {
+  id, title, body, actionLabel, cancelLabel, destructive = false, ask = false, cancelValue = "",
+  safeActionLabel, safeActionValue = "safe", ...rest
+} = Astro.props;
 ---
 
 <dialog class="confirm" id={id} aria-labelledby={title ? `${id}-t` : `${id}-b`} aria-describedby={`${id}-b`} {...rest}>
@@ -79,6 +95,9 @@ const { id, title, body, actionLabel, cancelLabel, destructive = false, ask = fa
            on a closed dialog, noise about a focus that was never going to happen. Focus is the
            OPENER's job now, at showModal time: ask → the invitation (CONSENT_JS does it),
            destructive → the cancel (the consumer does it). The genre decides, as before. */}
+      {safeActionLabel && (
+        <button class="confirm-act preferred" id={`${id}-safe`} value={safeActionValue}>{safeActionLabel}</button>
+      )}
       <button class:list={["confirm-act", { destructive, preferred: ask }]} id={`${id}-act`} value="confirm">{actionLabel}</button>
       {ask && <button class="confirm-act quiet" id={`${id}-cancel`} value={cancelValue} formnovalidate>{cancelLabel}</button>}
     </div>

package/src/Toolbar.astro

@@ -88,6 +88,17 @@ interface Props {
   // 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;
+  /**
+   * Which cut a visit with no hash opens on. Defaults to the kernel, which is right for every
+   * persona whose kernel is the thing it does.
+   *
+   * app.zone is the exception this exists for: its kernel is a catalogue of the OTHER personas, so
+   * landing there opens the house on a list of its rooms and scrolls the mark, the wordmark and the
+   * sentence that say what app.zone IS past before anyone reads them. Passed to `personaScroll`
+   * through a data attribute, the same way the two title strings already travel — this cut renders
+   * markup, and the behaviour reads the markup rather than being handed a closure.
+   */
+  landOn?: string;
   postsTitle?: string;
 
   // queries: toolbar shows a generic person icon · the profile icon is not my persona ·
@@ -160,7 +171,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", kernelTitle, postsTitle, landOn, 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.
@@ -172,7 +183,7 @@ import AuthMount from "./AuthMount.astro";
      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. -->
 <div class="tb-slot">
-  <header class="toolbar" data-kernel-title={kernelTitle} data-posts-title={postsTitle}>
+  <header class="toolbar" data-kernel-title={kernelTitle} data-posts-title={postsTitle} data-land-on={landOn}>
     <div class="tb-row">
       <div class="tb-left">
         {home && <BackToZone apex={apex} />}

package/src/behaviour/toolbar.ts

@@ -82,8 +82,13 @@ document.querySelector(".toolbar")?.addEventListener(
 const bar = document.querySelector(".toolbar") as HTMLElement | null;
 const kt = bar?.dataset.kernelTitle;
 const pt = bar?.dataset.postsTitle;
-personaScroll(
-  kt && pt
+// `landOn` travels as a data attribute for the same reason the two titles do: this file runs in a
+// page it did not render, so the markup is the interface. Undefined when the attribute is absent,
+// which is the option's default — the kernel.
+const landOn = bar?.dataset.landOn;
+personaScroll({
+  ...(kt && pt
     ? { titleFor: (id: string) => (id === "kernel" ? kt : id === "posts" ? pt : "") }
-    : undefined,
-);
+    : {}),
+  ...(landOn ? { landOn } : {}),
+});