@justai/cuts 0.141.0 → 0.143.0

package/package.json

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

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/CatalogueCard.astro

@@ -90,7 +90,10 @@ const icon = `${app.url}/icon.svg`;
     width: 60px;
     height: 60px;
     border-radius: var(--radius-md);
-    object-fit: cover;
+    /* contain: this is a persona's mark, not a photograph. A square tile is unaffected — the two
+       declarations agree on square art — and a mark taller than its box keeps its ends instead of
+       having them cropped. See the note on .pa .mk in Posts.astro. */
+    object-fit: contain;
     box-shadow: 0 8px 20px -12px rgba(0, 0, 0, 0.35);
   }
 

package/src/ChildPersona.astro

@@ -269,8 +269,13 @@ const chrome = face === "page";
   .pp[data-face="sheet"] .app { max-width: none; margin-inline: 0; border: 0; background: none;
                                 backdrop-filter: none; -webkit-backdrop-filter: none; }
 
-  /* a mark fills its box; the picture inside it covers */
-  .pp .mk { display: block; width: 100%; height: 100%; object-fit: cover; }
+  /* A MARK FILLS ITS BOX AND LOSES NOTHING DOING IT. This said `cover`, which fills by scaling to the
+     larger ratio and cropping the overflow off both edges. Square art renders identically either way —
+     which is why it survived on every child page — but pin.games' mark is 700.19 x 767.26, so `cover`
+     took 4.8% off its top and 4.8% off its bottom, and those are the blue bracket and the red one.
+     Same change, same reason, as .pa .mk in Posts.astro. The feed service carries a fork of this
+     stylesheet and had lost the rule entirely; it is `contain` there now too. */
+  .pp .mk { display: block; width: 100%; height: 100%; object-fit: contain; }
 
   /* Motion is never forced on somebody who asked it not to be — and the biggest effects, the ones a
      surface is proudest of, are exactly what that setting exists to suppress. */

package/src/Posts.astro

@@ -268,7 +268,19 @@ const vars = [
   }
   .rav { flex: none; width: 30px; height: 30px; border-radius: var(--radius-sm); display: grid; place-items: center; font-size: 15px; background: var(--feed-av-bg, #fff); border: 1px solid var(--border); overflow: hidden; }
   .pa :global(svg), .rav :global(svg) { display: block; }
-  .pa .mk, .rav .mk { width: 100%; height: 100%; object-fit: cover; display: block; }
+  /* queries: the avatar is cropped · blue and red pieces cut off · pin.games mark clipped top and
+             bottom · a mark loses its tips in the feed · cover vs contain for a persona icon
+     CONTAIN, NOT COVER — THE SLOT IS FORGIVING, THE ASSET NEED NOT BE PERFECT. `cover` fills the box
+     by scaling to the LARGER ratio and cropping the overflow, split evenly between the two edges. For
+     a square drawing in a square slot the two are the same declaration, which is why this stood for
+     twenty-six personas without a complaint: every fleet icon.svg is square. pin.games' mark is not —
+     its box is 700.19 x 767.26, so `cover` scaled it by width, overflowed the height by 9.6%, and took
+     4.8% off the top and 4.8% off the bottom. What lives at the top and bottom of that drawing is the
+     blue bracket and the red one, which is exactly the pair the founder reported as cut. On a 76px
+     profile avatar that is 3.6px gone from each end.
+     Squaring the asset is the other half of this and is being done too, but it is not a substitute:
+     an asset can be redrawn wrong tomorrow, while a slot that never crops cannot crop anyone. */
+  .pa .mk, .rav .mk { width: 100%; height: 100%; object-fit: contain; display: block; }
   /* a dark tile must invert in light mode, not stay dark — personas whose avatar ground is a gradient
      pass avatarBgLight; the rest fall back to their single background. */
   @media (prefers-color-scheme: light) { :global(html:not([data-theme="dark"])) .pa, :global(html:not([data-theme="dark"])) .rav { background: var(--feed-av-bg-light, var(--feed-av-bg, #fff)); } }

package/src/Profile.astro

@@ -127,7 +127,10 @@ const vars = [
   @media (prefers-reduced-motion: reduce) { .avatar { transition: none; } }
   /* the avatar content is slotted (persona-owned) → style it globally */
   .avatar :global(svg) { width: 100%; height: 100%; display: block; }
-  .avatar :global(img) { width: 100%; height: 100%; display: block; object-fit: cover; }
+  /* contain, not cover — see the note on .pa .mk in Posts.astro. A square icon renders identically
+     under either; a mark whose box is taller than wide loses its top and its bottom under `cover`,
+     which is what cropped pin.games' blue and red brackets on this very avatar. */
+  .avatar :global(img) { width: 100%; height: 100%; display: block; object-fit: contain; }
   @media (prefers-color-scheme: light) {
     :global(html:not([data-theme="dark"])) .avatar { border-color: #fff; background: var(--avatar-bg-light, var(--avatar-bg, #fff)); }
   }

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;