@justai/cuts 0.27.2 → 0.28.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@justai/cuts",
-  "version": "0.27.2",
+  "version": "0.28.1",
   "description": "A persona's named parts \u2014 the page shell that holds them, and the cuts themselves.",
   "license": "UNLICENSED",
   "repository": {
@@ -30,6 +30,6 @@
     "access": "public"
   },
   "dependencies": {
-    "@justai/core": "^0.4.1"
+    "@justai/core": "^0.5.0"
   }
 }

package/src/ground.css

@@ -65,12 +65,20 @@
   }
 }
 
-/* The body's own ground — margin reset, the fleet's type baseline, the page colours. Zero
- * specificity again: any consumer body rule overrides. Without this, a blank page renders the
- * sheet over a white serif document — the Times lesson, carved as CSS. */
+/* The page's ground — margin reset, the fleet's type baseline, and the page colour ON :where(html),
+ * NEVER on body. Learned live, fleet-wide, within a day: personas paint their dot-grid on html and
+ * leave body's background UNDECLARED — relying on the web's default transparency structurally, not
+ * by declaration. Zero specificity beats a declaration that exists; it still fills one that never
+ * did. A body background from the ground, with the fleet's `body{height:100%}`, painted an opaque
+ * viewport-tall box over the top of every grid — dots gone at the top, reappearing where body ends.
+ * The founder saw it before any instrument did. The rule that survives: THE GROUND MAY ONLY SUPPLY
+ * WHAT A BARE PAGE LACKS ON ELEMENTS CONSUMERS DECLARE — html's background is declared by every
+ * persona (they win); body's transparency is load-bearing and stays untouched. */
+:where(html) {
+  background: var(--bg);
+}
 :where(body) {
   margin: 0;
-  background: var(--bg);
   color: var(--text);
   font: 1rem/1.5 var(--font);
 }