@justai/cuts 0.62.0 → 0.64.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.62.0",
+  "version": "0.64.0",
   "description": "A persona's named parts \u2014 the page shell that holds them, and the cuts themselves.",
   "license": "UNLICENSED",
   "repository": {
@@ -25,7 +25,8 @@
     "./FilePicker.astro": "./src/FilePicker.astro",
     "./ActionList.astro": "./src/ActionList.astro",
     "./ActionRow.astro": "./src/ActionRow.astro",
-    "./Files.astro": "./src/FilePicker.astro"
+    "./Files.astro": "./src/FilePicker.astro",
+    "./AuthMount.astro": "./src/AuthMount.astro"
   },
   "peerDependencies": {
     "astro": ">=5"

package/src/AuthMount.astro

@@ -0,0 +1,35 @@
+---
+// ░░ AUTH MOUNT — the sign-in avatar, and the script that fills it, as ONE thing ░░
+//
+// queries: no avatar in the toolbar · sign in missing on files · the auth avatar never appears ·
+//          data-justai-auth is empty · how does a persona get sign-in · where does sdk.js come from ·
+//          why is the auth mount a component instead of two lines
+//
+// THE TWO HALVES CANNOT BE SEPARATED, WHICH IS WHY THIS IS A COMPONENT AND NOT A SNIPPET.
+//
+// Sign-in on a persona page is a mount point plus the SDK that fills it. Both are trivial, and that is
+// exactly the problem: a surface hand-writing its own toolbar copies them BY HAND, and half a copy
+// fails silently. `files` carried `<div data-justai-auth>` in precisely the right place and never
+// loaded the script — so the div sat there, empty, for as long as anybody looked at it. Nothing
+// errored. There is no avatar and no error to explain its absence, which is the worst shape a defect
+// can take.
+//
+// Found 2026-07-31 by the founder noticing the avatar was simply not there. Measured across the
+// ecosystem at that moment: the cut had both halves, `files` had one, `me` had neither, and `feed`
+// had its own copy of both — four surfaces, three different answers to one question.
+//
+// So the pair ships as a unit. A surface either has sign-in or does not; it can no longer have half.
+//
+// WHY THE THREE SURFACES CANNOT JUST USE `Toolbar`: `/me`, `/files` and the feed carry navigation of
+// their own — a vault link, a host link, a back-to-persona mark — so they hand-write the toolbar
+// markup and always will. That is the same reason `personaScroll` moved down into @justai/core. What
+// cannot be shared is the markup; what CAN be shared is every load-bearing piece inside it, and this
+// is one of them.
+//
+// The origin is deliberately absolute. This is inherited from auth.justai.pro — one Google client for
+// the whole ecosystem, sign in once and you are you on every persona — so the src is that host and
+// never a local path, on every domain that mounts it.
+---
+
+<div data-justai-auth></div>
+<script is:inline defer src="https://auth.justai.pro/sdk.js"></script>

package/src/Toolbar.astro

@@ -22,7 +22,9 @@
 //     persona's, so it comes from the persona. Omit it and the bust stays — adopting this is each
 //     persona's own decision, taken when its mark exists, and nothing moves in the fleet without it.
 //     Note what a mark cannot do: an <img> ignores `currentColor`, so `.active`'s accent never reaches
-//     it. Slot presence adds `.tb-mark`, which carries "you are here" as opacity instead.
+//     it. It is not replaced with anything: the title strip already closes on this cut and opens off
+//     it, and a mark is an identity rather than a UI state. Slot presence adds `.tb-mark`, which the
+//     sizing rule uses.
 //   • langPicker — needs the persona's own locale data (the list must NOT live in the shared package —
 //     it bit us twice; see @justai/ui/locale) → a slot the persona fills with its <LangPicker/>.
 //   • navExtra — optional extra nav item after Posts (e.g. the timers' fullscreen button) → slot.
@@ -51,6 +53,7 @@ interface Props {
 }
 import BackToZone from "./BackToZone.astro";
 const { sectionsLabel, profileLabel, kernelLabel, postsLabel, home = true, files = true, filesLabel = "Files" } = Astro.props;
+import AuthMount from "./AuthMount.astro";
 ---
 
 <header class="toolbar">
@@ -67,8 +70,7 @@ const { sectionsLabel, profileLabel, kernelLabel, postsLabel, home = true, files
             in the fleet moves on the day this ships.
 
             `tb-mark` is set from slot PRESENCE, not from a prop somebody could forget to keep in step. It
-            exists because a mark cannot take `currentColor`: an <img> ignores it, so the accent that says
-            "you are here" would never reach it. The class moves that signal to opacity instead. */}
+            exists so the sizing rule can find the image; it deliberately does NOT restyle the mark. */}
         <a
           class:list={["tb-nav", { "tb-mark": Astro.slots.has("profileIcon") }]}
           id="navProfile"
@@ -121,13 +123,11 @@ const { sectionsLabel, profileLabel, kernelLabel, postsLabel, home = true, files
     <div class="tb-right">
       <slot name="toolbarRight" />
       <slot name="langPicker" />
-      <div data-justai-auth></div>
+      <AuthMount />
     </div>
   </div>
   <div class="tb-title" id="tbTitle"><span class="tb-title-text" id="tbTitleText"></span></div>
 </header>
-<!-- justai auth — sign-in avatar menu, inherited from auth.justai.pro (the developer writes only the kernel) -->
-<script is:inline defer src="https://auth.justai.pro/sdk.js"></script>
 
 <style>
   /* ---- app toolbar — sticky to the top of the active region (kernel + posts); it never
@@ -172,15 +172,16 @@ const { sectionsLabel, profileLabel, kernelLabel, postsLabel, home = true, files
   .tb-nav:active { transform: scale(0.9); }
   .tb-nav.active { color: var(--accent); }
 
-  /* A MARK SAYS "YOU ARE HERE" WITH OPACITY, BECAUSE IT CANNOT SAY IT WITH COLOUR.
-     The three stroke icons are painted by `currentColor`, so `.active` turning them accent is enough. An
-     <img> mark ignores `currentColor` entirely — it carries its own paint — so on the mark that rule is a
-     declaration with no effect, and the one icon a person is looking at would be the one that never lit.
-     Opacity is the same answer BackToZone reached when it took the mark: dimmed at rest, whole when
-     current. `!important`-free, because these are more specific than the colour rules above. */
-  .tb-nav.tb-mark { opacity: 0.72; transition: opacity 0.25s var(--ease-out); }
-  .tb-nav.tb-mark:hover,
-  .tb-nav.tb-mark.active { opacity: 1; }
+  /* A MARK IS NOT DIMMED, AND THE PROFILE CUT DOES NOT NEED IT TO BE.
+     It shipped dimmed at rest for one version, on the reasoning that a mark cannot take `currentColor`
+     and so needed opacity to say "you are here". Both halves of that were true and the conclusion was
+     still wrong, because the state was already being said, louder: `titleFor` in @justai/core returns an
+     empty string for `profile`, so the title strip CLOSES on this cut and opens — 26px of layout, naming
+     where you are — the moment you leave it. Against that, tinting an icon adds nothing.
+     And the two are not the same kind of thing. The three stroke icons are generic glyphs whose colour IS
+     a UI state; a mark is an identity. A faded logo does not read as "not current", it reads as disabled.
+     So the mark stays itself. Press feedback is not lost: `.tb-nav:active`'s scale applies to it like any
+     other item. `.tb-mark` remains, because the sizing rule below still needs to know an image is here. */
   /* The shell sizes the mark and says NOTHING about `display`, deliberately. Two files arrive for the two
      themes — an SVG's internal `prefers-color-scheme` does not survive <img>, measured — and the persona
      hides one with a media query. A `display: block` here would be two classes deep against the persona's