@justai/cuts 0.66.0 → 0.68.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.66.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/ActionRow.astro

@@ -114,8 +114,18 @@ const { id, label, tone = "plain", detail, hidden, i18n, ...rest } = Astro.props
   .jal-label { flex: 1; min-width: 0; }
   .jal-detail { color: var(--text-dim); font-size: var(--fs-xs); flex: none; }
 
-  .jal-row.is-accent { color: var(--accent); font-weight: 600; }
-  .jal-row.is-accent .jal-ico { color: var(--accent); }
+  /* queries: the accent row is unreadable in light mode · is-accent contrast · accent as text ·
+     my persona's accent is too bright to read in a sheet
+     THE ACCENT AS INK IS NOT THE ACCENT AS PAINT. A fill only has to be SEEN; a word has to be READ,
+     and a persona whose accent is light fails contrast here while looking perfect as a button — tts's
+     amber measures 1.67:1 on the light surface against the 4.5 a word needs.
+     This is the same problem ConfirmSheet already solved with `--confirm-accent`, one component over,
+     for the same stated reason ("the action reads as TEXT"). The hook is additive: a consumer that
+     sets nothing gets exactly what it got before, and one that sets `--accent-text` gets a readable
+     row. Prefer fixing it here over a persona globalising this class — that is what tts had to do
+     while this shipped, and a persona reaching into a cut's internals is a fix that rots. */
+  .jal-row.is-accent { color: var(--accent-text, var(--accent)); font-weight: 600; }
+  .jal-row.is-accent .jal-ico { color: var(--accent-text, var(--accent)); }
   .jal-row.is-danger { color: var(--danger); }
   .jal-row.is-danger .jal-ico { color: var(--danger); }
   .jal-row.is-danger:active { background: color-mix(in srgb, var(--danger) 12%, transparent); }

package/src/LangPicker.astro

@@ -119,7 +119,8 @@ const ordered = orderLocales(locales);
   .item:active { background: color-mix(in srgb, var(--text) 12%, transparent); }
   @media (hover: hover) { .item:hover { background: color-mix(in srgb, var(--text) 8%, transparent); } }
   .item:focus-visible { outline: none; background: color-mix(in srgb, var(--accent) 16%, transparent); }
-  .item.active { color: var(--accent); font-weight: 600; }
+  /* The chosen locale reads as TEXT — see ActionRow for why this takes the ink hook. */
+  .item.active { color: var(--accent-text, var(--accent)); font-weight: 600; }
   .item svg { width: 17px; height: 17px; flex: none; }
 </style>
 

package/src/Posts.astro

@@ -248,14 +248,14 @@ const vars = [
   .phandle, .dot, .pt { color: var(--text-dim); font-weight: 400; }
   /* a persona's name in the feed links to its profile (X-style); humans have no link */
   .pn { color: inherit; text-decoration: none; }
-  .pn:hover b { color: var(--accent); }
+  .pn:hover b { color: var(--accent-text, var(--accent)); }
   a.pt { text-decoration: none; }
   a.pt:hover { text-decoration: underline; }
   .pbd { font-size: var(--fs-sm); line-height: 1.5; margin-block-start: 4px; }
   .pact { display: flex; gap: 22px; margin-block-start: 12px; color: var(--text-dim); }
   .pact svg { width: 17px; height: 17px; }
   .pact span { cursor: pointer; transition: color 0.2s; }
-  .pact span:hover { color: var(--accent); }
+  .pact span:hover { color: var(--accent-text, var(--accent)); }
   .ch { display: flex; align-items: center; gap: 4px; font-size: var(--fs-xs); }
   .ch b { font-weight: 600; }
   .ch .muted { color: var(--text-dim); font-weight: 400; }

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 />}
@@ -170,7 +190,9 @@ import AuthMount from "./AuthMount.astro";
   }
   .tb-nav:hover { color: var(--text); }
   .tb-nav:active { transform: scale(0.9); }
-  .tb-nav.active { color: var(--accent); }
+  /* The active glyph is a graphic, so it wants 3:1 rather than 4.5 — which a light accent still
+     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`
@@ -214,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>