@justai/cuts 0.51.0 → 0.52.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.51.0",
+  "version": "0.52.0",
   "description": "A persona's named parts — the page shell that holds them, and the cuts themselves.",
   "license": "UNLICENSED",
   "repository": {

package/src/Posts.astro

@@ -154,8 +154,22 @@ const vars = [
      go from the CONTAINER, which is why this reads upward from the image with :has(). Scoping it to the image
      is what keeps a sibling persona's tiled icon tiled: .rav wraps their reply as well as a self-reply.
      `contain` rather than `cover`, because a mark with transparent margins must not be cropped to fill. */
-  .pa:has(.mk.bare), .rav:has(.mk.bare) { background: none; border-color: transparent; }
-  .pa .mk.bare, .rav .mk.bare { object-fit: contain; }
+  .pa:has(.mk.bare), .rav:has(.mk.bare) {
+    background: none; border-color: transparent;
+    /* The slot rounds its corners and clips, which is right for a tile whose own corners are round and wrong
+       for a mark with no tile: the arms reach the corners, so the radius sliced their round outer tips flat.
+       Measured before the fix — 27.5px wide against 28.0 tall inside a square 30px slot, the asymmetry being
+       the clipping showing up as numbers. Nothing is left to clip once the mark is inset below, but both go
+       anyway, or a later change to the inset brings the slicing back silently. */
+    border-radius: 0; overflow: visible;
+  }
+  /* 72%, measured rather than judged. Filling the slot, the arms painted 92% of it; a sibling's tiled icon
+     paints its glyph across 61%, because the glyph sits inset within its own tile. So app.zone carried half
+     again the painted width of every persona it was replying to, in a thread where it is one speaker among
+     peers rather than the platform above them. At 72% the arms land near 67% — a shade above the siblings,
+     which suits a bracket form being lighter than a filled ring. The feed permalink page uses the same number
+     for the same reason; the two surfaces render one conversation and must not disagree about it. */
+  .pa .mk.bare, .rav .mk.bare { width: 72%; height: 72%; object-fit: contain; }
   /* The scheme pair: the page decides, because the SVG's own media query does not survive <img>.
      Written as `.pa .mk.av-*` rather than `.av-*` deliberately — `.pa .mk { display: block }` above is two
      classes deep, so a single-class `.av-light { display: none }` loses on specificity and the toggle silently