unoverse 0.1.20 → 0.1.22

package/bin/unoverse.mjs

@@ -48,6 +48,11 @@ const UNIVERSE = findUniverse();
 
 // Everything the operator half owns. Listed here so an unknown command can say so,
 // rather than the two CLIs disagreeing about what exists.
+// NOTE: `update` is deliberately ABSENT. It always updates this CLI, wherever you are.
+// It used to mean the universe when you happened to be standing in one, which is the
+// same word pointing at two different objects, decided by your working directory. You
+// type it to update the CLI far more often than to refresh a local universe's images,
+// and that refresh now belongs to `start --pull`.
 const OPERATOR_COMMANDS = new Set([
   "start", "stop", "check", "logs", "deploy",
   // kept working, not advertised
@@ -94,9 +99,6 @@ switch (cmd) {
     break;
 
   case "update": {
-    // In a universe, "update" means THAT UNIVERSE (pull images, restart), not this CLI.
-    // Same word, different object, decided by where you are standing.
-    if (UNIVERSE) operator(UNIVERSE, ["update", ...args]);
     const r = spawnSync("npm", ["install", "-g", "unoverse@latest"], { stdio: "inherit" });
     if (r.status === 0) {
       const v = spawnSync("unoverse", ["-v"], { encoding: "utf8" }).stdout?.trim();

package/operator/lib/start.sh

@@ -41,6 +41,15 @@ cmd_start() {
     echo "$docr_token" | docker login registry.digitalocean.com -u "$docr_token" --password-stdin >/dev/null 2>&1 || true
   fi
 
+  # `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.
+  if [ "${1:-}" = "--pull" ]; then
+    info "Pulling the latest images..."
+    docker compose -f "$ROOT/docker-compose.yml" pull || { fail "Image pull failed"; exit 1; }
+    echo ""
+  fi
+
   check_docker_file_sharing || exit 1
   check_first_run
   banner "Starting Unoverse Platform"

package/operator/lib/update.sh

@@ -7,6 +7,21 @@ cmd_update() {
   echo ""
   timer_start
 
+  # ── Refuse before doing half the job ───────────────────────────────────────────
+  # This used to run against an unconfigured folder with Docker down: compose warned
+  # about thirty blank variables, then failed on the daemon, after reporting that the
+  # code had updated. Ask first.
+  if [ ! -f "$ROOT/.env" ]; then
+    fail "This universe is not configured yet"
+    info "Run ${BOLD}unoverse init${NC} first"
+    exit 1
+  fi
+  if ! docker info >/dev/null 2>&1; then
+    fail "Docker is not running. Update pulls images, so it needs the daemon"
+    info "Start Docker Desktop, then run ${BOLD}unoverse update${NC} again"
+    exit 1
+  fi
+
   # ── Developer work is SAFE, by design ──────────────────────────────────────────
   # `update` refreshes the PLATFORM (its own tracked files) and NEVER touches a developer's
   # own work. Custom nodes live as UNTRACKED files (apps/unoverse/nodes/<yours>) — `git reset
@@ -27,7 +42,18 @@ cmd_update() {
     exit 1
   fi
 
-  # Step 1: Code — pull from customer's fork
+  # Step 1: Code — pull from customer's fork.
+  #
+  # NOT EVERY UNIVERSE IS A GIT CLONE. `unoverse create` extracts a tarball, so there is
+  # no remote to pull from and never was. That is not a failure: the images carry the
+  # platform, and the files here are yours. Skip the step and say which mode you are in,
+  # rather than running git commands that all fail and then reporting "Code updated".
+  if ! git -C "$ROOT" rev-parse --git-dir >/dev/null 2>&1; then
+    info "Not a git checkout, so there is no code to pull. Updating images only"
+    UNOVERSE_SKIP_GIT=1
+  fi
+
+  if [ "${UNOVERSE_SKIP_GIT:-}" != "1" ]; then
   printf "  ${DIM}●${NC} Pulling latest code..."
   local git_ok=true
   local git_log
@@ -89,6 +115,7 @@ cmd_update() {
       exit 1
     fi
   fi
+  fi   # UNOVERSE_SKIP_GIT
 
   # Step 2: Images — login to registry if DOCR_TOKEN is set
   local docr_token

package/operator/operator.sh

@@ -57,7 +57,7 @@ source "$GRAVITY_LIB/ground.sh"
 # operate a universe. Studio is a separate app; authoring happens there.)
 case "${1:-}" in
   init)      cmd_init ;;
-  start)     cmd_start ;;
+  start)     shift; cmd_start "$@" ;;
   stop)      cmd_stop ;;
   status)    cmd_check ;;   # alias — status merged into check 2026-07-28
   logs)      cmd_logs "${2:-}" ;;

package/package.json

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