@justai/cuts 0.140.0 → 0.142.0

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@justai/cuts",
-  "version": "0.140.0",
-  "description": "A persona's named parts \u2014 the page shell that holds them, and the cuts themselves.",
+  "version": "0.142.0",
+  "description": "A persona's named parts — the page shell that holds them, and the cuts themselves.",
   "license": "UNLICENSED",
   "repository": {
     "type": "git",

package/src/BackToZone.astro

@@ -43,12 +43,41 @@
 // geometry here is a second copy of the one in that file, which is authored by hand and generated by
 // nothing — a redraw has to be carried across to this component as well.
 interface Props {
-  /** Which storefront "home" means here. Defaults to app.zone — the fleet as it stood. */
-  apex?: "app.zone" | "pin.games";
+  /**
+   * Which storefront "home" means here. Defaults to app.zone — the fleet as it stood.
+   *
+   * A STRING, NOT A UNION OF THE TWO APEXES WE HAPPENED TO HAVE. The union was a fourth copy of the
+   * apex table (the others: edge-router's `apexes`, core's `STREAMS`, the generator's `APEXES`), and
+   * it is the copy that fails LOUDEST — a third household could not type-check, which is how it was
+   * found. Loud is the good outcome; the quiet one is below.
+   */
+  apex?: string;
 }
 const { apex = "app.zone" } = Astro.props;
 const href = `https://${apex}`;
 
+/**
+ * queries: the home mark is app.zone's on another apex · no home button on a new apex · a household
+ *          with no mark · why does my persona have no home affordance · BackToZone renders nothing
+ *
+ * AN APEX WE CANNOT DRAW GETS NO CONTROL AT ALL — and that is the honest outcome, not a gap.
+ *
+ * This was `apex === "pin.games" ? pinMark : appzoneMark`, a ternary whose ELSE branch quietly meant
+ * "app.zone". Point a third household at it and the control renders app.zone's four-arm mark, labelled
+ * with the other domain, linking to a front door that may not even be served yet: a wrong brand, on
+ * somebody else's name, as a dead link. Nothing errors. Nothing looks broken.
+ *
+ * So the marks are a TABLE and the fallback is nothing. Law 1 says a component brings its own ground;
+ * a component that cannot represent a household must decline rather than borrow another's face. The
+ * toolbar already survives this — `BackToZone` sizes and pulls itself, and the row is written for its
+ * absence — so the whole degradation is one missing control.
+ *
+ * It self-corrects: the day a household has a mark here, every persona under it grows the affordance
+ * on its next build, with no persona-level change anywhere.
+ */
+const MARKS = ["app.zone", "pin.games"];
+const drawable = MARKS.includes(apex);
+
 // queries: the home mark is missing arms · the mark is the wrong size · 36px · scoped styles do
 //          not apply · set:html · data-astro-cid
 //
@@ -67,6 +96,7 @@ const href = `https://${apex}`;
 // Elements again. The ternary was never the problem.
 ---
 
+{drawable && (
 <a class="home" href={href} data-home aria-label={apex} title={apex}>
   {apex === "pin.games" ? (
 <svg class="pgmark" viewBox="287 266 482 491" aria-hidden="true">
@@ -90,6 +120,7 @@ const href = `https://${apex}`;
   </svg>
   )}
 </a>
+)}
 
 <style>
   /* icon-only, flat — flush to the left edge of the (full-bleed) toolbar */

package/src/Catalogue.astro

@@ -43,7 +43,24 @@ interface Props {
   /** BCP-47 code of the page — the language the registry is asked for. */
   lang: string;
   /** Which citizens this apex lists. The whole difference between two storefronts. */
-  kind: string;
+  /**
+   * queries: Catalogue kind prop · data-kind on the grid · what kind does a mixed household pass ·
+   *          vestigial prop · why is kind optional now
+   *
+   * VESTIGIAL, AND KEPT ONLY SO THE TWO EXISTING APEXES STILL COMPILE.
+   *
+   * It fed one thing: `data-kind` on the grid, which the runtime append read to ask the registry
+   * `?kind=`. That question moved to `?apex=` when a household arrived whose citizens are not all one
+   * species, and the attribute lost its last reader in the same change. (`data-kind` on `<html>` is a
+   * DIFFERENT attribute, written by Base and read by @justai/ui for a game kernel's geometry — that
+   * one is alive.)
+   *
+   * Optional rather than deleted because `app.zone` and `pin.games` still pass it, and a required prop
+   * removed is a build error in two repos for no gain. It goes when they next build. A mixed household
+   * has no answer to it at all, which is the clearest possible statement that it was the wrong
+   * question here.
+   */
+  kind?: string;
   /** The apex's own host, used for the referral parameter on every card. */
   apexHost: string;
   /** Layer one. Empty is valid and correct for an apex with nothing seeded yet. */
@@ -85,7 +102,7 @@ interface Props {
   };
 }
 const {
-  lang, kind, apexHost,
+  lang, apexHost,
   seed = [], order = [], taglines = {}, catLabels = {}, entries = {},
   locales, strings,
 } = Astro.props;
@@ -211,7 +228,7 @@ const isNew = (added: string): boolean => { const t0 = Date.parse(added || "");
       {/* taglines ride the same channel as newLabel and catMap: a data attribute on the grid. The
           runtime append builds its cards in plain strings and cannot reach this component's scope, so
           anything it needs has to arrive this way. Keyed by host, which is what the API calls `home`. */}
-      <section class="grid" id="grid" data-kind={kind} data-apex={apexHost} data-new-label={strings.new} data-cat-map={JSON.stringify(catLabels)} data-order={JSON.stringify(order)} data-taglines={JSON.stringify(taglines)}>
+      <section class="grid" id="grid" data-apex={apexHost} data-new-label={strings.new} data-cat-map={JSON.stringify(catLabels)} data-order={JSON.stringify(order)} data-taglines={JSON.stringify(taglines)}>
         {seed.map((app) => <CatalogueCard app={app} name={appName(app)} desc={appDesc(app)} isNew={isNew(app.added)} newLabel={strings.new} />)}
       </section>
       {/* queries: runtime cards are unstyled · the card has no CSS · an apex with no seed · scope cid ·

package/src/Toolbar.astro

@@ -61,8 +61,13 @@ 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;
-  /** Which storefront the home affordance points at. Defaults to app.zone — see BackToZone. */
-  apex?: "app.zone" | "pin.games";
+  /**
+   * Which storefront the home affordance points at. Defaults to app.zone — see BackToZone, which owns
+   * the marks and DECLINES to draw a household it has no mark for rather than borrowing app.zone's.
+   * A string, not a union: the ecosystem grows households, and a type that lists two of them is a
+   * fourth copy of the apex table.
+   */
+  apex?: string;
 
   // Posts is required only where there IS a stream (doctrine 02 — an empty cut shipped to look
   // complete is the buffet). A child persona has none, so `parent` turns this off by default.

package/src/behaviour/posts.ts

@@ -144,6 +144,33 @@
   // So there is no fallback now. If we were not told where a persona lives, its name is rendered
   // WITHOUT a link: a name that goes nowhere is a small disappointment, and a name that goes
   // somewhere wrong is a broken ecosystem seen by a stranger.
+  // queries: apex logo has a tile in the feed · app.zone tiled on justai's page · which personas sign
+  //          bare · is this persona an apex · favicon.svg vs icon.svg for a commenter
+  //
+  // AN APEX SIGNS BARE; EVERYONE ELSE WEARS THEIR TILE. A persona signing its OWN posts already gets
+  // this through `avatarSrc`/`avatarBare`, which is how each apex hands itself the bare pair. Another
+  // persona replying did not: it was drawn from the registry's `avatar` — /icon.svg, the tile — so on
+  // an apex's own page the two sibling apexes appeared in tiles among that page's children, which is
+  // exactly the sibling claim the bare mark exists to deny (app-zone/.justai/expert/how-an-app-zone-
+  // icon-is-lit.md: the platform mark is inset where app marks are raised).
+  //
+  // APEX-NESS IS READ, NEVER DECLARED. A persona is an apex when its home is a BARE registrable domain
+  // — app.zone, pin.games, justai.pro — and a child's home always carries a label in front of it:
+  // qr.app.zone, sudoku.pin.games. One dot versus two. The same test the icon builder applies
+  // (builder/icon/build.py, apex_handles) and the feed service applies (feed Feed.astro, isApex), on
+  // purpose: three places may not disagree about who is an apex. Read from `home` and not from
+  // `personaKind`, because `platform` answers a different question — auth is a platform persona and is
+  // not an apex.
+  //
+  // /favicon.svg and /mark.svg are the platform standard, generated from the same /icon.svg by
+  // @justai/astro-config/mark, so an apex has this pair by construction and no name is hardcoded here.
+  // The registered avatar stays /icon.svg for everyone: the tile IS right in the catalogue, and only a
+  // feed asks an apex for its bare mark.
+  const apexHome = (url: string | null | undefined): string | null => {
+    if (!url) return null;
+    const h = String(url).replace(/^https?:\/\//, "").replace(/\/.*$/, "");
+    return (h.match(/\./g) || []).length === 1 ? h : null;
+  };
   const comment = (c: C, last: boolean): string => {
     const ln = last ? "" : `<span class="ln"></span>`;
     if (c.isPersona) {
@@ -151,11 +178,15 @@
       // face and name; ANOTHER persona wears ITS canonical icon (glyph fallback), its own name, its
       // @handle, and its name links to its own profile. The verified check stays for both.
       const own = c.authorHandle === PERSONA;
+      // A replying apex signs bare from ITS OWN home, in the scheme pair, exactly as it does on its page.
+      const apex = own ? null : apexHome(c.personaUrl);
       const av = own
         ? AV
-        : c.authorAvatar
-          ? `<img class="mk" src="${esc(c.authorAvatar)}" alt="">`
-          : `<span style="font-size:16px">${esc(c.authorGlyph || "✦")}</span>`;
+        : apex
+          ? `<img class="mk bare av-light" src="https://${esc(apex)}/favicon.svg" alt=""><img class="mk bare av-dark" src="https://${esc(apex)}/mark.svg" alt="">`
+          : c.authorAvatar
+            ? `<img class="mk" src="${esc(c.authorAvatar)}" alt="">`
+            : `<span style="font-size:16px">${esc(c.authorGlyph || "✦")}</span>`;
       const nm = own ? NAME : esc(c.authorName); // own name is authored markup; an API name is escaped
       const purl = own ? "#profile" : c.personaUrl ? `${c.personaUrl}/#profile` : null;
       const at = own ? PERSONA : c.authorHandle;