@justai/cuts 0.139.0 → 0.141.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.139.0",
+  "version": "0.141.0",
   "description": "A persona's named parts \u2014 the page shell that holds them, and the cuts themselves.",
   "license": "UNLICENSED",
   "repository": {
@@ -41,7 +41,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@justai/core": "^0.36.0",
+    "@justai/core": "^0.37.0",
     "@justai/ui": "^0.26.0",
     "@justai/atrium": "^0.1.9"
   },

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

@@ -116,7 +116,11 @@ const appName = (a: App): string => entries[a.id]?.name ?? a.name;
 // API is unreachable at build — the design never depends on the network.
 let catalogByHome: Record<string, string> = {};
 try {
-  const res = await fetch(`https://api.justai.pro/api/catalog?locale=${lang}&kind=${encodeURIComponent(kind)}`);
+  // Asked by HOUSEHOLD, matching the runtime append — see behaviour/catalogue.ts for why a third
+  // apex made `kind` the wrong question here. This lookup is keyed by home, so a wider answer would
+  // still have worked; it asks the same question as the runtime path so the two cannot drift into
+  // disagreeing about who lives here.
+  const res = await fetch(`https://api.justai.pro/api/catalog?locale=${lang}&apex=${encodeURIComponent(apexHost)}`);
   if (res.ok) {
     const data = await res.json();
     for (const p of data.personas ?? []) if (p.home && p.bio) catalogByHome[p.home] = p.bio;

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/catalogue.ts

@@ -27,13 +27,18 @@
   const locale = document.documentElement.lang || "en";
   const NEW_MS = 7 * 864e5; // a persona wears NEW only for its first week (honest — from its createdAt)
   const newLabel = grid.dataset.newLabel || "New";
-  // queries: which personas appear on this apex · runtime append kind · why is my game not listed
+  // queries: which personas appear on this apex · runtime append kind · why is my game not listed ·
+  //          a CiM persona is missing from its storefront · apex query parameter · mixed-kind apex
   //
   // WHICH CITIZENS THIS APEX LISTS — where the hostname test used to be. A bundled script cannot
-  // reach this component's props, so the two facts it needs ride the same data-attribute channel as
-  // newLabel and catMap. And `kind` is asked of the registry rather than inferred from a suffix: a
-  // persona's apex is a property of the persona, not a shape of its address.
-  const apexKind = grid.dataset.kind || "app";
+  // reach this component's props, so the fact it needs rides the same data-attribute channel as
+  // newLabel and catMap.
+  //
+  // IT ASKS THE REGISTRY BY HOUSEHOLD, NOT BY SPECIES, and the difference only became visible with a
+  // third apex. `kind` selects a SORT of persona; on app.zone and pin.games that happens to select
+  // the residents too, because every citizen of those two is the same sort. cityinmotion.nl is the
+  // household where they part — its citizens are sometimes games and sometimes apps — and asking it
+  // for one kind returns half a family and calls that the storefront.
   const apexHost = grid.dataset.apex || "app.zone";
   // The category label must be localized like the SSR path (catLabel), but the API returns the
   // category in English regardless of ?locale=. So carry this page's cat dictionary through a data
@@ -93,13 +98,16 @@
     return `<a class="card" href="${esc(url)}" data-name="${esc(name.toLowerCase())}" data-category="${esc(cat)}" data-id="${esc((a.handle || "").toLowerCase())}" data-added="${esc(a.createdAt || "")}">${icon}<div class="meta"><div class="top"><h2>${esc(name)}</h2>${badge}</div><p>${esc(tagMap[a.home] ?? a.bio ?? "")}</p></div><svg class="chev" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M9 18l6-6-6-6"/></svg></a>`;
   };
 
-  fetch(`https://api.justai.pro/api/catalog?locale=${encodeURIComponent(locale)}&kind=${encodeURIComponent(apexKind)}`)
+  fetch(`https://api.justai.pro/api/catalog?locale=${encodeURIComponent(locale)}&apex=${encodeURIComponent(apexHost)}`)
     .then((r) => (r.ok ? r.json() : null))
     .then((data) => {
       if (!data || !data.personas) return;
       const newcomers = (data.personas as Entry[]).filter(
-        // The registry already returned only this apex's kind, so all that is left to exclude is the
-          // apex itself — a household head does not stand on its own shelf.
+        // THE RESIDENCY TEST STAYS, AND IS NOW A REDUNDANCY ON PURPOSE. Asking by apex means the
+          // registry has already excluded the other households AND the platform furniture that stands
+          // on no shelf, so this filter should never remove anything. It is kept because a browser can
+          // be holding a cached response from before the question changed, and because a storefront
+          // listing somebody else's citizen is the one failure here that looks fine.
           //
           // queries: auth appeared on app.zone · a persona from another apex is listed · why both
           //          kind and home · residency