unoverse 0.1.114 → 0.1.116

package/operator/docker-compose.yml

@@ -153,7 +153,15 @@ services:
       # health checks) still reaches it via 127.0.0.1. Never widen to "4101:4101".
       - "127.0.0.1:4101:4101" # workflow surface (engine in-process)
     environment:
-      - NODE_ENV=production
+      # PRODUCTION UNLESS THE DEVELOPER SAYS OTHERWISE. This was fixed at "production", and
+      # auth-off refuses to boot in production — correctly — so a LOCAL universe running these
+      # images could never turn auth off at all: AUTH_ENABLED=false and NODE_ENV=production
+      # are a permanent contradiction, and the platform was right to refuse both ways round.
+      #
+      # The guard is not weakened: unset still means production, and terraform's rendered env
+      # never sets this, so a deployed universe cannot drift. Turning it off is a deliberate
+      # line in a developer's own .env.
+      - NODE_ENV=${NODE_ENV:-production}
       # Studio is a separate app, launched by the CLI from source. It is not in this image
       # and has no switch here: the Docker runtime serves MCP + API only.
       - UNOVERSE_PORT=4105
@@ -169,6 +177,12 @@ services:
       # containers connect to the container IP); the loopback-only port mappings above and
       # the Docker network are the boundary here.
       - UNOVERSE_INTERNAL_BIND=0.0.0.0
+      # THE FLAG TRAVELS WITH THE ISSUER. .env could say AUTH_ENABLED=false and no
+      # container ever saw it: compose forwarded the issuer and audience and not the flag,
+      # so the server defaulted to enabled — correctly — and refused to boot on a local
+      # universe with no OIDC. The developer's own setting was invisible to the thing it
+      # configures.
+      - AUTH_ENABLED=${AUTH_ENABLED:-}
       - AUTH_ISSUER=${AUTH_ISSUER:-}
       - AUTH_AUDIENCE=${AUTH_AUDIENCE:-}
       # WHERE THE MARKETPLACE IS. The catalogue this universe can install from, served as
@@ -267,7 +281,15 @@ services:
     ports:
       - "4104:4104"
     environment:
-      - NODE_ENV=production
+      # PRODUCTION UNLESS THE DEVELOPER SAYS OTHERWISE. This was fixed at "production", and
+      # auth-off refuses to boot in production — correctly — so a LOCAL universe running these
+      # images could never turn auth off at all: AUTH_ENABLED=false and NODE_ENV=production
+      # are a permanent contradiction, and the platform was right to refuse both ways round.
+      #
+      # The guard is not weakened: unset still means production, and terraform's rendered env
+      # never sets this, so a deployed universe cannot drift. Turning it off is a deliberate
+      # line in a developer's own .env.
+      - NODE_ENV=${NODE_ENV:-production}
       - PORT=4104
       - DATABASE_URL=${DATABASE_URL:-}
       # Connection budget (INFRASTRUCTURE.md) — Terraform-rendered per size.
@@ -277,6 +299,12 @@ services:
       - REDIS_PASSWORD=${REDIS_PASSWORD:-}
       - REDIS_TLS=${REDIS_TLS:-}
       - REDIS_NAMESPACE=${REDIS_NAMESPACE:-}
+      # THE FLAG TRAVELS WITH THE ISSUER. .env could say AUTH_ENABLED=false and no
+      # container ever saw it: compose forwarded the issuer and audience and not the flag,
+      # so the server defaulted to enabled — correctly — and refused to boot on a local
+      # universe with no OIDC. The developer's own setting was invisible to the thing it
+      # configures.
+      - AUTH_ENABLED=${AUTH_ENABLED:-}
       - AUTH_ISSUER=${AUTH_ISSUER:-}
       - AUTH_AUDIENCE=${AUTH_AUDIENCE:-}
       - OPENAI_API_KEY=${OPENAI_API_KEY:-}

package/operator/lib/start.sh

@@ -151,10 +151,19 @@ cmd_start() {
   local running=0
   local total=0
   i=0
+  # A RESTARTING CONTAINER IS NOT A RUNNING ONE. `--filter status=running` counts a container
+  # that is crash-looping, because between crashes it genuinely is running — so `start`
+  # announced "All 5 services running" while unoverse and memory were dying on boot every few
+  # seconds, and the developer went looking at their browser instead of the logs.
+  #
+  # Counting restarts as failures also means the loop keeps waiting instead of breaking early
+  # on a lie, which gives a slow-but-healthy boot the time it needs.
+  local restarting=0
   while [ $attempts -lt 15 ]; do
     running=$(docker compose -f "$ROOT/docker-compose.yml" ps --format "{{.Name}}" --filter "status=running" 2>/dev/null | wc -l | tr -d ' ')
+    restarting=$(docker compose -f "$ROOT/docker-compose.yml" ps -a --format "{{.Status}}" 2>/dev/null | grep -ci "restarting" | tr -d ' ')
     total=$(docker compose -f "$ROOT/docker-compose.yml" ps --format "{{.Name}}" 2>/dev/null | wc -l | tr -d ' ')
-    if [ "$running" -eq "$total" ] && [ "$total" -gt 0 ]; then
+    if [ "$running" -eq "$total" ] && [ "$total" -gt 0 ] && [ "$restarting" -eq 0 ]; then
       break
     fi
     local c="${spin:i%${#spin}:1}"
@@ -165,6 +174,29 @@ cmd_start() {
   done
 
   echo ""
+  # NAME WHAT IS CRASHING, AND WHY. A restart loop is the one failure whose cause is always
+  # in the logs and never on screen, so print the last line of each one rather than leaving
+  # the developer to find `docker compose logs` themselves.
+  if [ "${restarting:-0}" -gt 0 ]; then
+    printf "\r  ${RED}✗${NC} $restarting service(s) crashing on boot       \n"
+    echo ""
+    # ASK COMPOSE FOR THE SERVICE NAME. `${svc##*-}` on a container called
+    # unoversedevtest-unoverse-1 yields "1", so the log lookup asked for a service that does
+    # not exist and printed nothing — the crash was named and its cause silently dropped.
+    # `ps --format {{.Service}}` gives compose's own name for it.
+    docker compose -f "$ROOT/docker-compose.yml" ps -a --format "{{.Service}}\t{{.Status}}" 2>/dev/null \
+      | grep -i restarting | awk -F'\t' '{print $1}' | while read -r svc; do
+        reason=$(docker compose -f "$ROOT/docker-compose.yml" logs --tail=60 "$svc" 2>/dev/null \
+          | grep -iE "error" | grep -viE "at [A-Za-z_]+ \(|node:internal" | tail -1 \
+          | sed -E 's/^[^|]*\| *//')
+        echo -e "  ${RED}•${NC} ${BOLD}$svc${NC}"
+        [ -n "$reason" ] && echo -e "    ${DIM}${reason}${NC}"
+      done
+    echo ""
+    info "Full output: ${BOLD}unoverse logs <service>${NC}"
+    echo ""
+    return 1
+  fi
   if [ "$running" -eq "$total" ] && [ "$total" -gt 0 ]; then
     printf "\r  ${GREEN}✓${NC} ${DIM}Health checks passed${NC}       \n"
     echo ""

package/package.json

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