@justai/cuts 0.93.0 → 0.95.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.93.0",
+  "version": "0.95.0",
   "description": "A persona's named parts — the page shell that holds them, and the cuts themselves.",
   "license": "UNLICENSED",
   "repository": {
@@ -37,7 +37,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@justai/core": "^0.18.0",
+    "@justai/core": "^0.20.0",
     "@justai/ui": "^0",
     "@justai/atrium": "^0.1.9"
   }

package/src/Toolbar.astro

@@ -207,7 +207,7 @@ import AuthMount from "./AuthMount.astro";
               sees, rather than a duplicate face, which is a defect nobody reports. */}
           {Astro.slots.has("profileIcon")
             ? <slot name="profileIcon" />
-            : (!parent && <img src={avatar} alt="" width="19" height="19" loading="lazy" decoding="async" />)}
+            : (!parent && <img src={avatar} alt="" width="20" height="20" loading="lazy" decoding="async" />)}
         </a>
         {/* THE KERNEL IS ALWAYS THE BOLT. The founder's rule, and it is the shell's to draw rather
             than the persona's to remember.
@@ -346,16 +346,23 @@ import AuthMount from "./AuthMount.astro";
      misses. Same ink hook as everywhere the accent stops being paint. */
   .tb-nav.active { color: var(--accent-text, var(--accent)); }
 
-  /* 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. */
+  /* queries: should the persona mark be coloured · the mark is always accent · two icons look active
+     THE MARK IS A CUT ICON LIKE THE OTHER TWO — the founder's rule, 2026-08-03: the ACTIVE cut wears
+     the accent and no passive one does, the persona's own mark included.
+
+     This comment used to argue the opposite: *"the three stroke icons are generic glyphs whose colour
+     IS a UI state; a mark is an identity… a faded logo reads as disabled."* Kept, because it is a true
+     premise ageing into a wrong conclusion. It was true while the mark arrived as an `<img>`, which
+     cannot take `currentColor` — dimming was then the only way to say "not here", and a dimmed logo
+     does read as disabled. The premise expired when `toolbarMark` began deriving an inline SVG: an
+     inline mark can be INK, and ink is not dimming. `toolbarMark` neutralises its paint, so the two
+     rules below reach it exactly as they reach the bolt and the bubble.
+
+     A mark that keeps its colours while another cut is current is a second voice on the one channel
+     the accent has — measured, several passive marks were more coloured than the active icon. A
+     persona that wants its own gradient WHILE CURRENT re-points to it from its own CSS; the `<defs>`
+     survive the derivation for that. `.tb-mark` remains, because the sizing rule below still needs to
+     know a mark 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
@@ -472,6 +479,23 @@ import AuthMount from "./AuthMount.astro";
   // consumers each remembering a line is O(N), and the third one always forgets.
   if (document.getElementById("navParent")) adoptMark({ id: "navParent" });
 
+  // queries: the persona mark is an image · the golden rule does not apply · currentColor img ·
+  //          the mark keeps its colours when I did not pass profileIcon
+  //
+  // THE FALLBACK HAS TO OBEY THE RULE TOO. A persona that passes `profileIcon` hands over a mark
+  // derived at build time — ink, ground-less, sized. A persona that passes nothing gets the `<img>`
+  // above, and an image obeys nothing: it cannot take `currentColor`, so it wears its own colours
+  // while another cut is current, which is exactly what the accent must never do.
+  //
+  // It is the child persona's problem in a different costume — a mark known only as a URL — so it
+  // takes the child's answer: fetch it and derive it here. Same function, same three edits, and the
+  // row's own `.tb-nav` / `.tb-nav.active` rules reach it afterwards like any glyph.
+  //
+  // The build-time path stays the better one and stays the default advice: it costs no request and
+  // no frame of the wrong picture. This is the floor under a persona that has not got there yet.
+  const ownMark = document.querySelector("#navProfile img");
+  if (ownMark) adoptMark({ id: "navProfile" });
+
   // 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.