unoverse 0.1.32 → 0.1.33

package/bin/unoverse.mjs

@@ -103,26 +103,36 @@ switch (cmd) {
     break;
 
   case "update": {
-    // Refresh the repo-local authoring skill alongside the CLI, when we are in a
-    // universe. It is a copy by necessity (Claude Code discovers .claude/skills off
-    // disk), so the CLI's own update is what keeps it current.
+    // ONE update: the CLI from npm, then everything the CLI is responsible for keeping
+    // current — the repo-local authoring skill and, in a universe, the platform images.
+    // Those two steps run via `_postupdate` in the NEWLY installed binary, not this
+    // process: this file is being replaced mid-command, and copying the skill from the
+    // old install would pin it one release behind forever.
+    const r = spawnSync("npm", ["install", "-g", "unoverse@latest"], { stdio: "inherit" });
+    if (r.status === 0) {
+      const v = spawnSync("unoverse", ["-v"], { encoding: "utf8" }).stdout?.trim();
+      console.log(`\n  ✓ unoverse is now ${v || "up to date"}`);
+      spawnSync("unoverse", ["_postupdate"], { stdio: "inherit" });
+    } else {
+      console.log(`\n  ✗ global install failed (permissions?). Try:\n\n    sudo npm install -g unoverse@latest\n    npx unoverse@latest    # or skip the global install entirely\n`);
+    }
+    process.exit(r.status ?? 0);
+  }
+
+  case "_postupdate": {
+    // Runs AS the new version, in the developer's cwd. Outside a universe there is
+    // nothing to refresh, and silence is the right answer.
     if (UNIVERSE) {
       const skillSrc = join(dirname(fileURLToPath(import.meta.url)), "../operator/skills/unoverse-create");
       if (existsSync(skillSrc)) {
         const { cpSync, mkdirSync } = await import("node:fs");
         mkdirSync(join(UNIVERSE.root, ".claude/skills"), { recursive: true });
         cpSync(skillSrc, join(UNIVERSE.root, ".claude/skills/unoverse-create"), { recursive: true });
-        console.log("  ✓ authoring skill refreshed (.claude/skills/unoverse-create)");
+        console.log("  ✓ authoring skill refreshed");
       }
+      operator(UNIVERSE, ["refresh-images"]);
     }
-    const r = spawnSync("npm", ["install", "-g", "unoverse@latest"], { stdio: "inherit" });
-    if (r.status === 0) {
-      const v = spawnSync("unoverse", ["-v"], { encoding: "utf8" }).stdout?.trim();
-      console.log(`\n  ✓ unoverse is now ${v || "up to date"}\n`);
-    } else {
-      console.log(`\n  ✗ global install failed (permissions?). Try:\n\n    sudo npm install -g unoverse@latest\n    npx unoverse@latest    # or skip the global install entirely\n`);
-    }
-    process.exit(r.status ?? 0);
+    process.exit(0);
   }
 
   // `urls` stays as an alias: it shipped in 0.1.4/0.1.5 and is in people's fingers.

package/operator/lib/init.sh

@@ -308,7 +308,7 @@ ENVEOF
       fail "DOCR login failed. Check your token"
       exit 1
     fi
-    cmd_pull
+    pull_missing_images
   else
     echo ""
     info "Skipped the registry login and image pull. ${BOLD}unoverse start${NC} does both once Docker is up"

package/operator/lib/start.sh

@@ -33,6 +33,24 @@ check_docker_file_sharing() {
   return 0
 }
 
+# Pull whatever images are missing, VISIBLY. docker's own per-layer progress bars are the
+# loading indication — a developer staring at a silent screen while gigabytes download
+# assumes the tool is hung. Exists because init used to call cmd_pull (deleted with
+# update.sh), so nothing pulled and nothing printed, and start buried compose's pull
+# inside a log file.
+pull_missing_images() {
+  local img missing=""
+  for img in $(docker compose -f "$ROOT/docker-compose.yml" config --images 2>/dev/null | sort -u); do
+    docker image inspect "$img" >/dev/null 2>&1 || missing="$missing $img"
+  done
+  [ -n "$missing" ] || return 0
+  echo ""
+  info "Pulling platform images (first run — a few minutes, progress below)..."
+  echo ""
+  docker compose -f "$ROOT/docker-compose.yml" --env-file "$ROOT/.env" pull     || { fail "Image pull failed. Check the registry token (re-run unoverse create to change it)"; exit 1; }
+  echo ""
+}
+
 cmd_start() {
   # Login to registry if DOCR_TOKEN is set
   local docr_token
@@ -44,6 +62,8 @@ cmd_start() {
   # `start --pull` refreshes the images first. This is where refreshing a LOCAL universe
   # lives now: `update` is the CLI's word and means only the CLI, wherever you type it.
   # A server is refreshed by `unoverse deploy` from your machine, not on the box.
+  pull_missing_images
+
   if [ "${1:-}" = "--pull" ]; then
     info "Pulling the latest images..."
     docker compose -f "$ROOT/docker-compose.yml" pull || { fail "Image pull failed"; exit 1; }

package/operator/operator.sh

@@ -64,6 +64,22 @@ case "${1:-}" in
   check)     cmd_check && cmd_db_verify && cmd_doctor ;;
   dev)       cmd_dev ;;
   ground)    shift; cmd_ground "$@" ;;
+  refresh-images)
+    # internal: `unoverse update` runs this after updating the CLI. Pull newer images
+    # if the registry has them, and recreate only what is already running — an update
+    # never boots a stopped universe.
+    if [ ! -f "$ROOT/.env" ]; then
+      : # unconfigured: nothing to refresh
+    elif ! docker info >/dev/null 2>&1; then
+      info "Docker is not running. Images refresh on the next unoverse start"
+    else
+      info "Checking for newer platform images..."
+      docker compose -f "$ROOT/docker-compose.yml" --env-file "$ROOT/.env" pull || warn "image check failed (network/registry?)"
+      if [ -n "$(docker compose -f "$ROOT/docker-compose.yml" ps -q 2>/dev/null)" ]; then
+        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"
+      fi
+    fi ;;
   deploy)
     # `deploy marketplace` is PLATFORM-OWNER only: it publishes the marketplace package
     # to npm, which a starter developer never does (they INSTALL from the marketplace).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.32",
+  "version": "0.1.33",
   "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",