unoverse 0.1.143 → 0.1.144

package/operator/lib/deploy.sh

@@ -934,6 +934,25 @@ EOF
     if [ -n "$smoke_api" ]; then
       echo ""
       info "Smoke-testing the deployed stack ${DIM}($smoke_api)${NC}"
+      # WAIT FOR STEADY STATE FIRST. A restart is ~36s of boot plus however many
+      # health-check intervals the load balancer needs to re-admit the droplet, and
+      # during that window EVERY api-side probe answers 503. The smoke test measures
+      # the stack's steady state, not the race — so it starts at the first 200 from
+      # /health THROUGH the balancer (which proves both the app and re-admission), and
+      # only a stack that never gets there fails. Observed live 2026-08-16: a healthy
+      # v1.13.79 deploy reported four FAILs and "fix forward or roll back", all of it
+      # re-admission lag. A false stop after the irreversible half is the worst kind.
+      local smoke_wait=0
+      until [ "$(curl -s -m 5 -o /dev/null -w '%{http_code}' "$smoke_api/health")" = 200 ]; do
+        if [ "$smoke_wait" -ge 180 ]; then
+          echo -e "    ${RED}FAIL${NC} stack never became healthy (/health ≠ 200 after ${smoke_wait}s)"
+          smoke_fail=1
+          break
+        fi
+        [ "$smoke_wait" = 0 ] && echo -e "    ${DIM}waiting for /health through the balancer (boot + LB re-admission)...${NC}"
+        sleep 5; smoke_wait=$((smoke_wait + 5))
+      done
+      [ "$smoke_fail" = 0 ] && [ "$smoke_wait" -gt 0 ] && echo -e "    ${DIM}healthy after ${smoke_wait}s${NC}"
       _smoke() { # name, then the test itself as "$@"
         local name="$1"; shift
         if "$@" >/dev/null 2>&1; then echo -e "    ${GREEN}ok${NC} $name"

package/package.json

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