@justai/cuts 0.67.0 → 0.68.0

package/package.json

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

package/src/Toolbar.astro

@@ -50,13 +50,33 @@ interface Props {
   // destination, and justai.pro is above it (sending the parent "home" to a child platform is
   // the wrong direction). Every other persona keeps it.
   home?: boolean;
+  // What the title strip says when the Kernel or the Posts cut is the one at the toolbar line.
+  //
+  // OMIT THEM AND NOTHING MOVES: the strip keeps naming the persona and its handle, which is right
+  // almost everywhere. On a leaf the kernel IS the persona — the strip reading "QR Code" while you
+  // use qr replaces the profile header that scrolled away, and "App" would be strictly less.
+  //
+  // app.zone is the exception the pair exists for, and the reason is structural rather than a matter
+  // of taste: it is the one persona whose kernel is NOT itself. Its kernel is a catalogue of the
+  // others, and its profile header — a few pixels above — already says app.zone. So the strip spends
+  // its only line repeating what the visitor can see. There it says "Apps" and "Posts" instead.
+  //
+  // BOTH OR NEITHER, deliberately. Half an override would need this file to reproduce the other
+  // half's default, which means copying core's `.pname` / `.handle` selectors into a second place
+  // 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;
+  postsTitle?: string;
 }
 import BackToZone from "./BackToZone.astro";
-const { sectionsLabel, profileLabel, kernelLabel, postsLabel, home = true, files = true, filesLabel = "Files" } = Astro.props;
+const { sectionsLabel, profileLabel, kernelLabel, postsLabel, home = true, files = true, filesLabel = "Files", kernelTitle, postsTitle } = Astro.props;
 import AuthMount from "./AuthMount.astro";
 ---
 
-<header class="toolbar">
+<!-- The two titles reach the script as data attributes rather than through `define:vars`, which would
+     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. -->
+<header class="toolbar" data-kernel-title={kernelTitle} data-posts-title={postsTitle}>
   <div class="tb-row">
     <div class="tb-left">
       {home && <BackToZone />}
@@ -216,5 +236,15 @@ import AuthMount from "./AuthMount.astro";
   // 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();
+  // 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.
+  const bar = document.querySelector(".toolbar") as HTMLElement | null;
+  const kt = bar?.dataset.kernelTitle;
+  const pt = bar?.dataset.postsTitle;
+  personaScroll(
+    kt && pt
+      ? { titleFor: (id: string) => (id === "kernel" ? kt : id === "posts" ? pt : "") }
+      : undefined,
+  );
 </script>