@uniweb/runtime 0.18.1 → 0.19.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/runtime",
-  "version": "0.18.1",
+  "version": "0.19.0",
   "description": "Minimal runtime for loading Uniweb foundations",
   "type": "module",
   "exports": {
@@ -36,7 +36,7 @@
     "node": ">=20.19"
   },
   "dependencies": {
-    "@uniweb/core": "^0.24.0",
+    "@uniweb/core": "^0.24.1",
     "@uniweb/theming": "^0.1.15"
   },
   "devDependencies": {
@@ -44,7 +44,7 @@
     "esbuild": "^0.21.0 || ^0.23.0 || ^0.24.0 || ^0.25.0 || ^0.27.0",
     "vite": "^7.3.1",
     "vitest": "^4.1.7",
-    "@uniweb/build": "0.42.0"
+    "@uniweb/build": "0.42.1"
   },
   "peerDependencies": {
     "react": "^19.0.0",

package/src/isolate-api.js

@@ -41,7 +41,7 @@
  *
  * ⚠️ **The tempting fix is the dangerous one.** Stamping the current version
  * (`0.16.0`) would satisfy every check and be **false**: backend reads
- * `isolateApiFloor` from the channel index and refuses to serve a site below it,
+ * `minUsable` from the channel index and refuses to serve a site below it,
  * so a floor of 0.16.0 would promise an export that 0.16.0 does not contain —
  * and a host at the floor is entitled to skip feature detection. That is a
  * guarantee broken in the one direction the floor exists to prevent.
@@ -55,7 +55,7 @@
  *   1. land the export stamped `UNRELEASED` — the floor does not move;
  *   2. publish (Diego; agents never publish);
  *   3. replace `UNRELEASED` with the version that publish produced — the floor
- *      moves here, and the runtime channel's `isolateApiFloor` follows at the
+ *      moves here, and the runtime channel's `minUsable` follows at the
  *      next channel publish;
  *   4. tell backend, which holds the number and must ratchet it.
  *
@@ -110,10 +110,51 @@ export const ISOLATE_API = Object.freeze({
 })
 
 /**
- * The runtime version at or above which EVERY name in `ISOLATE_API` is exported —
- * the absolute floor a host may rely on with no feature detection.
  */
-export const ISOLATE_API_FLOOR = Object.values(ISOLATE_API)
+/**
+ * ⭐ A RUNTIME BELOW THIS CANNOT TALK TO THE CURRENT RECORDS SERVICE, whatever it
+ * exports — so it is a floor for a reason the API map cannot express.
+ *
+ * `0.18.0` is the first runtime that sends `whole`. Every earlier one sends
+ * `depth` on **every** records question, briefs included; `depth` is now an
+ * unknown field at the door, and an unknown field is a **protocol violation —
+ * a whole-request `400`**. ⇒ On a site pinned below this, **every** live-records
+ * fetch fails: the corpus walk a host makes AND the fetches a page render
+ * issues. Loud, per key, with a sentence — but total.
+ *
+ * ⛔ **Why this belongs in the same number rather than beside it.** The floor's
+ * job AT ITS CONSUMER is *"never publish a site below this"* — the publisher
+ * reads it and refuses a lower version. That behaviour does not care WHY a
+ * version is unusable, and a second number to read and compose would be one more
+ * thing to miss, failing silently when missed.
+ *
+ * ⚠️ **The name is now slightly narrow, and that is a deliberate trade.** What
+ * ships in the channel index is `isolateApiFloor`, which a consumer already polls
+ * and ratchets; renaming it is a cross-lane change for a word, while the contract
+ * it carries — the minimum a site may be published at — is unchanged and is what
+ * matters. Read it as *the absolute runtime floor*, of which the API map is one
+ * input.
+ *
+ * ⇒ **Raise this when a runtime change makes an older one unable to speak to a
+ * shipped peer.** Not for a feature, not for a fix — for an incompatibility.
+ */
+export const WIRE_FLOOR = '0.18.0'
+
+/**
+ * ⭐ **THE MINIMUM RUNTIME VERSION A SITE MAY BE PUBLISHED AT.** At or above it,
+ * every name in `ISOLATE_API` is exported AND the runtime can speak to the
+ * current records service; below it, a runtime **does not work** — not "is
+ * unsupported".
+ *
+ * ⛔ **Named `ISOLATE_API_FLOOR` until 2026-09-06, and the name was wrong twice
+ * over**: the API map is only one of its inputs, and "floor" said nothing about
+ * what falls below it. *[Diego: "I wasn't convinced by `isolateApiFloor` when it
+ * was introduced."]* ⭐ **`usable` is a claim of FACT, and it is chosen to resist
+ * a drift** — raise this for an incompatibility, never for a feature, a fix or a
+ * preference, and a name that says *usable* makes the wrong reason read wrong.
+ * On the wire it is `minUsable`.
+ */
+export const MIN_USABLE_RUNTIME = [WIRE_FLOOR, ...Object.values(ISOLATE_API)]
   .filter((v) => v !== UNRELEASED)
   .reduce((max, v) => (compareVersions(v, max) > 0 ? v : max), '0.0.0')