unoverse 0.1.193 → 0.1.195

package/operator/ansible/playbooks/deploy-images.yml

@@ -76,17 +76,14 @@
       debug:
         msg: "{{ pull_result.stdout_lines[-8:] | default(['done']) }}"
 
-    # A DEPLOY TAKES THE NEWEST NODE RUNTIME. The entrypoint installs
-    # @unoverse-platform/base within the range the image declares, but it only goes to the
-    # registry when the volume is cold or the range moved — otherwise a restart would be a
-    # network call, and a restart must be instant and offline. A DEPLOY is the moment the
-    # operator asked for "make this current" (MARKETPLACE.md §5a), so it says so explicitly.
-    # Scoped to this one `up`, never written into .env: a later `docker restart` must not
-    # inherit it.
-    - name: "[3/4] Restart on the new images (and take the newest base in range)"
+    # THE NODE RUNTIME CAME WITH THE IMAGE. base is baked in, not installed
+    # (MARKETPLACE.md §5a, reversed 2026-09-03), so the pull above already moved it and
+    # this step has nothing extra to ask for. It used to run with `UNOVERSE_BASE_REFRESH=1`
+    # to mean "take the newest base in range"; there is no range and no install any more.
+    - name: "[3/4] Restart on the new images"
       shell: |
         cd {{ gravity_dir }}
-        UNOVERSE_BASE_REFRESH=1 docker compose up -d 2>&1 | tail -6
+        docker compose up -d 2>&1 | tail -6
       register: up_result
 
     # `up -d` RECREATES ON CONFIG CHANGE, NOT ON IMAGE CHANGE — not reliably, and not on

package/operator/docker-compose.yml

@@ -275,20 +275,12 @@ services:
       # copy carrying a built dist. Without this the runtime hits MODULE_NOT_FOUND and
       # the nodes show "Package not installed".
       - NODE_PATH=/app/host_node_modules:/app/plugins/node_modules
-      # PASSTHROUGH, not a setting. `unoverse deploy` runs `UNOVERSE_BASE_REFRESH=1 docker
-      # compose up -d` to mean "take the newest node runtime in range"; without this line
-      # that variable would reach the compose CLI and stop there, never the container.
-      # Defaults to 0, so an ordinary restart stays offline and instant.
-      - UNOVERSE_BASE_REFRESH=${UNOVERSE_BASE_REFRESH:-0}
     volumes:
       - unoverse_plugins:/app/plugins
-      # THE NODE RUNTIME, which this image does not carry (MARKETPLACE.md §5a). The
-      # entrypoint installs @unoverse-platform/base here at startup, within the range
-      # apps/unoverse/package.json declares, and symlinks it into
-      # /app/node_modules/@unoverse-platform/base. A volume rather than a layer so a plain
-      # restart is offline and instant: the fetch happens on a cold volume, or when the
-      # declared range changes, or when a deploy sets UNOVERSE_BASE_REFRESH=1.
-      - unoverse_base:/app/base
+      # THE NODE RUNTIME IS IN THE IMAGE (MARKETPLACE.md §5a, reversed 2026-09-03). There was
+      # a `unoverse_base:/app/base` volume here between 2026-08-30 and 2026-09-03, holding a
+      # base the entrypoint installed from npm at startup. Both are gone: base is compiled in
+      # from the workspace, so the image and its runtime cannot disagree.
       # ── Platform-dev mounts (monorepo only; sync-starter strips these three
       # lines from the starter's copy — a customer universe serves what the DB
       # says). Local edits are picked up on restart; design/prompts are data, no build.
@@ -407,4 +399,3 @@ services:
 volumes:
   umap_models:
   unoverse_plugins: # Marketplace-installed node packages (persisted across restarts)
-  unoverse_base: # @unoverse-platform/base, installed at startup (MARKETPLACE.md §5a)

package/operator/lib/check.sh

@@ -79,27 +79,18 @@ cmd_check() {
 
   # 1b. THE NODE RUNTIME THIS UNIVERSE IS ACTUALLY RUNNING.
   #
-  # base is installed at startup, not baked into the image (MARKETPLACE.md §5a), so a
-  # universe's platform version and its runtime version are two different numbers that move
-  # independently. Nobody updates what they cannot see: this is the line that turns "which
-  # base am I on?" into something answerable, and shows the gap when the registry has newer.
+  # base ships INSIDE the image (MARKETPLACE.md §5a, reversed 2026-09-03), so this number
+  # cannot disagree with the platform version above — and printing it is how you can tell.
+  # It used to be installed from npm at startup and compared against the registry here,
+  # because the two moved independently; they do not any more, and a line that still
+  # offered "npm has newer" would be advertising a lane that no longer exists.
   # Read out of the RUNNING container rather than off this machine's disk, because the
   # container is the only thing whose answer counts.
-  local base_installed base_range base_latest
+  local base_installed
   base_installed=$(docker compose -f "$ROOT/docker-compose.yml" exec -T unoverse \
     node -p "require('/app/node_modules/@unoverse-platform/base/package.json').version" 2>/dev/null | tr -d '\r')
   if [ -n "$base_installed" ]; then
-    base_range=$(docker compose -f "$ROOT/docker-compose.yml" exec -T unoverse \
-      node -p "require('/app/apps/unoverse/package.json').dependencies['@unoverse-platform/base']" 2>/dev/null | tr -d '\r')
-    base_latest=$(curl -s --max-time 5 "https://registry.npmjs.org/-/package/@unoverse-platform%2Fbase/dist-tags" 2>/dev/null \
-      | node -pe 'try{JSON.parse(require("fs").readFileSync(0,"utf8")).latest ?? ""}catch(e){""}' 2>/dev/null)
-    if [ -n "$base_latest" ] && [ "$base_latest" != "$base_installed" ]; then
-      # NOT a failure. A universe is entitled to sit on an older runtime; it is not entitled
-      # to be unable to find out. `deploy` and `update` are what take the newer one.
-      warn "node runtime ${BOLD}$base_installed${NC} ${DIM}(range $base_range · npm has $base_latest — 'unoverse deploy' takes it)${NC}"
-    else
-      ok "node runtime ${BOLD}$base_installed${NC} ${DIM}(range ${base_range:-unknown})${NC}"
-    fi
+    ok "node runtime ${BOLD}$base_installed${NC} ${DIM}(in the image)${NC}"
     echo ""
   fi
 

package/operator/operator.sh

@@ -155,12 +155,10 @@ case "${1:-}" in
         exit 1
       fi
       if [ -n "$(docker compose -f "$ROOT/docker-compose.yml" ps -q 2>/dev/null)" ]; then
-        # THE NODE RUNTIME UPDATES LIKE THE IMAGES DO. base is installed at startup, not
-        # baked (MARKETPLACE.md §5a), and the entrypoint only goes to the registry on a cold
-        # volume or a changed range — otherwise every restart would be a network call. An
-        # UPDATE is exactly the moment the operator asked for the newest of everything, so
-        # it says so. Scoped to this command; nothing is written to .env.
-        UNOVERSE_BASE_REFRESH=1 \
+        # THE NODE RUNTIME ARRIVES WITH THE IMAGE. base is baked in, not installed
+        # (MARKETPLACE.md §5a, reversed 2026-09-03), so pulling the image IS updating the
+        # runtime and there is nothing extra to ask for. `UNOVERSE_BASE_REFRESH=1` used to
+        # ride this line to mean "take the newest base in range"; the range is gone with it.
         docker compose -f "$ROOT/docker-compose.yml" --env-file "$ROOT/.env" up -d --remove-orphans >/dev/null 2>&1 \
           && ok "Running services moved to the new images"
         # MIGRATIONS RUN ON UPDATE, same as deploy and start. An update is exactly when a

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.193",
+  "version": "0.1.195",
   "description": "The Unoverse front door — create a Studio project, a universe, or a client app, and launch Studio.",
   "license": "SEE LICENSE IN README.md",
   "type": "module",