@justai/cuts 0.33.0 → 0.35.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.33.0",
+  "version": "0.35.0",
   "description": "A persona's named parts \u2014 the page shell that holds them, and the cuts themselves.",
   "license": "UNLICENSED",
   "repository": {
@@ -31,7 +31,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@justai/core": "^0.5.0",
+    "@justai/core": "^0.7.0",
     "@justai/ui": "^0.3.0",
     "@justai/atrium": "^0.1.9"
   }

package/src/FilePicker.astro

@@ -93,6 +93,7 @@ const { id, title = "Choose a file", src = "/files" } = Astro.props;
   // two kernels at once would otherwise have both arrive calling themselves "files", and the second
   // would silently take the first one's place.
   import atrium from "@justai/atrium";
+  import { PRESENTATION_PARAM, PRESENTATION_EMBEDDED } from "@justai/core";
 
   interface Picked {
     path: string;
@@ -147,7 +148,15 @@ const { id, title = "Choose a file", src = "/files" } = Astro.props;
 
     async function pick(req: PickRequest = {}): Promise<Picked | null> {
       const bus = await router();
-      if (!frame.getAttribute("src")) frame.setAttribute("src", root.dataset.src!);
+      if (!frame.getAttribute("src")) {
+        // DECLARE THE PRESENTATION. A page opened by a person and a page opened by another persona
+        // are two different situations, and the same controls do not belong in both — standalone
+        // there is nothing to cancel. The frame is the slower truth (a handshake takes a beat), so
+        // the declaration rides in the URL and is available in the first paint. It is presentation
+        // only: nothing that must not be forged is decided by it.
+        const src = root.dataset.src!;
+        frame.setAttribute("src", src + (src.includes("?") ? "&" : "?") + PRESENTATION_PARAM + "=" + PRESENTATION_EMBEDDED);
+      }
       // ONE HEADING, and it is the sheet's. A per-call title retitles the sheet rather than being
       // forwarded into the frame: the kernel renders a heading of its own for callers that have no
       // sheet around them, and sending it one here printed "Upload logo" twice, one under the other.

package/src/Toolbar.astro

@@ -119,89 +119,19 @@ const { sectionsLabel, profileLabel, kernelLabel, postsLabel, home = true } = As
 </style>
 
 <script>
-  // Land on the Kernel cut; Profile is above (scroll up), Posts below (scroll down). This is also the
-  // page's reveal (body.ready) and its scroll-spy (nav highlight + title strip + hash sync).
-  (function () {
-    const below = document.getElementById("below");
-    const kernel = document.getElementById("kernel");
-    const toolbar = document.querySelector(".toolbar");
-    const navKernel = document.getElementById("navKernel");
-    const navPosts = document.getElementById("navPosts");
-    const navProfile = document.getElementById("navProfile");
-    const profile = document.getElementById("profile");
-    const posts = document.getElementById("posts");
-    if (!below || !kernel) return;
-    if ("scrollRestoration" in history) history.scrollRestoration = "manual";
-    // update only the fragment, never clobbering the path or query (?data=, ?city= must survive a scroll)
-    const setHash = (id: string) => history.replaceState(null, "", location.pathname + location.search + "#" + id);
-
-    // Land at the top of .below (toolbar + kernel) — skip the Profile, no flash.
-    const land = () => {
-      // presentation mode (a ?data= link with present:true) owns the viewport — no landing scroll
-      if (document.body.dataset.present) return;
-      // respect a section hash on load/refresh: #posts / #profile land there; otherwise (#kernel or
-      // none) land on the Kernel. behavior:instant overrides the CSS scroll-behavior:smooth.
-      const h = location.hash;
-      if (h === "#posts" && posts) posts.scrollIntoView({ behavior: "instant", block: "start" });
-      else if (h === "#profile" && profile) profile.scrollIntoView({ behavior: "instant", block: "start" });
-      else window.scrollTo({ top: below.getBoundingClientRect().top + window.scrollY, behavior: "instant" });
-    };
-    land();
-    window.addEventListener("load", land);
-    const reveal = () => document.body.classList.add("ready");
-    requestAnimationFrame(reveal);
-    setTimeout(reveal, 500);
-
-    // Toolbar hairline appears once content scrolls under it; the nav highlights whichever
-    // cut is currently at the top of the active region (the toolbar line) — Profile (the
-    // first cut when you scroll up), App or Posts.
-    const cuts = [[profile, navProfile], [kernel, navKernel], [posts, navPosts]].filter(([el, nav]) => el && nav) as [HTMLElement, HTMLElement][];
-    // scroll-reactive title strip: the cut at the toolbar line names itself. Profile stays collapsed
-    // (its big header is the title); Kernel → app name, Posts → @handle.
-    const tbTitle = document.getElementById("tbTitle");
-    const tbTitleText = document.getElementById("tbTitleText");
-    const pname = (document.querySelector(".pname")?.textContent || "").trim();
-    const handle = (document.querySelector(".handle")?.textContent || "").trim();
-    const titleFor = (c: [HTMLElement, HTMLElement]) => (c[0] === kernel ? pname : c[0] === posts ? handle : "");
-    let lastTitleCut: [HTMLElement, HTMLElement] | null = null, titleInit = true;
-    const onScroll = () => {
-      if (toolbar) toolbar.classList.toggle("stuck", window.scrollY >= below.offsetTop - 1);
-      const line = 84; // ≥ #kernel/#posts scroll-margin-top, so anchor clicks land at/above the line and are detected
-      let current = cuts[0];
-      for (const c of cuts) if (c[0].getBoundingClientRect().top <= line) current = c;
-      for (const c of cuts) c[1].classList.toggle("active", c === current);
-      if (current !== lastTitleCut) {
-        lastTitleCut = current;
-        // scroll-linked URL: reflect the current cut in the hash (replaceState = no jump, no history spam)
-        const cid = current[0].id;
-        if (cid && "#" + cid !== location.hash) setHash(cid);
-        const t = titleFor(current);
-        if (titleInit) {
-          // first paint: snap the strip into place — no "settling into the room" animation on load/refresh
-          titleInit = false;
-          if (tbTitle) { tbTitle.style.transition = "none"; tbTitle.classList.toggle("show", !!t); }
-          if (t && tbTitleText) tbTitleText.textContent = t;
-          if (tbTitle) { void tbTitle.offsetHeight; tbTitle.style.transition = ""; }
-        } else {
-          if (tbTitle) tbTitle.classList.toggle("show", !!t);
-          if (t && tbTitleText && tbTitleText.textContent !== t) {
-            tbTitleText.classList.add("fade");
-            setTimeout(() => { tbTitleText.textContent = t; tbTitleText.classList.remove("fade"); }, 150);
-          }
-        }
-      }
-    };
-    window.addEventListener("scroll", onScroll, { passive: true });
-    onScroll();
-    // nav clicks: scroll programmatically so the sticky toolbar always pins flush. The native anchor
-    // + scroll-margin left a gap above the bar when jumping to the Kernel from the Profile (the title
-    // strip is still collapsed there, so the bar is shorter than the margin). Kernel → land at .below
-    // top (bar pins at 0); Profile/Posts → scrollIntoView.
-    cuts.forEach(([el, nav]) => nav.addEventListener("click", (e) => {
-      e.preventDefault();
-      if (el === kernel) window.scrollTo({ top: below.getBoundingClientRect().top + window.scrollY, behavior: "smooth" });
-      else el.scrollIntoView({ behavior: "smooth", block: "start" });
-      setHash(el.id);
-    }));
-  })();
+  // queries: where does the toolbar's scroll behaviour live · land on the kernel · scroll spy ·
+  //          title strip · why is the scroll code not in this file any more
+  //
+  // The BEHAVIOUR moved to @justai/core (`personaScroll`); what stays here is the markup and the CSS.
+  //
+  // It moved because this cut can only serve pages that adopt its markup, and three surfaces cannot:
+  // `/me` and `/files` carry extra navigation of their own and the feed is a different build. All
+  // three hand-wrote the same eighty lines, and by the third copy they had drifted — `/files` opened
+  // on the profile with an empty title strip, and its hash writer clobbered the query string where
+  // this one preserved it. One implementation, four consumers.
+  //
+  // The defaults ARE this cut's contract — the three cut ids, `nav<Cut>`, `#tbTitle`/`#tbTitleText`,
+  // `.toolbar`, `#below` — so a persona using the shell passes nothing at all.
+  import { personaScroll } from "@justai/core";
+  personaScroll();
 </script>