unoverse 0.1.84 → 0.1.85

package/operator/ansible/playbooks/db-setup.yml

@@ -127,9 +127,33 @@
       register: migrate_result
       ignore_errors: yes
 
+    # THE WHOLE FILE IS NOT THE ANSWER TO "DID IT WORK". This printed every line of the
+    # baseline — several hundred lines of CREATE TABLE nobody asked to read, burying the one
+    # line that says whether anything ran. Keep the names and the verdict.
     - name: "[4/5] Migration output"
       debug:
-        msg: "{{ migrate_result.stdout_lines | default(['No output']) }}"
+        msg: >-
+          {{ (migrate_result.stdout_lines | default([]) | select('match', '^> - ') | list)
+             + (migrate_result.stdout_lines | default([]) | select('search', 'Migrations complete|No migrations') | list)
+             | default(['No output'], true) }}
+
+    # SERVICES BOOTED BEFORE THIS SCHEMA EXISTED. install.yml has to start the containers
+    # first — migrations run THROUGH the unoverse container, so there is nothing to run them
+    # in until it is up. The cost is that every service that touches the database at boot
+    # does so against an empty one: memory logged "permission denied for schema public" and
+    # then 'relation "memories" does not exist', and stayed in that state until something
+    # restarted it. Restarting here is the missing half of that ordering, and it only ever
+    # happens on a first setup.
+    - name: "[4b/5] Restart services against the migrated schema"
+      command: docker compose restart
+      args:
+        chdir: /opt/gravity
+      when: migrate_result.rc | default(1) == 0
+
+    - name: "[4b/5] Settle"
+      pause:
+        seconds: 15
+      when: migrate_result.rc | default(1) == 0
 
     - name: "[5/5] Verify database connectivity"
       uri:

package/operator/ansible/playbooks/test-connectivity.yml

@@ -134,36 +134,38 @@
       register: api_write_check
       ignore_errors: yes
 
-    - name: "[10/14] Check unoverse node catalog loaded"
+    # AN EMPTY CATALOGUE IS NOT A BROKEN ONE. Nodes arrive as rows — installed from the
+    # marketplace or published from Studio — so a universe on its first day has none, and
+    # that is the correct state, not a fault. This used to fail outright on zero and advise
+    # "run deploy.sh rebuild", a command that does not exist, which turned every first
+    # deploy into a red line pointing at nothing.
+    #
+    # What IS worth failing on is the runtime not answering at all: that means the catalogue
+    # could not be read, which is a different fact from it being empty.
+    - name: "[10/13] Check the node catalogue is readable"
       shell: |
         cd /opt/gravity
         # The internal :4106 runtime is Docker-network-only (never published), and the
         # public :4105 routes are JWT-gated — so read the catalog from INSIDE the
         # container. node:20-slim has no curl; use node fetch.
         NODE_COUNT=$(docker compose exec -T unoverse node -e \
-          "fetch('http://127.0.0.1:4106/nodes').then(r=>r.json()).then(d=>console.log((d.nodes||[]).length)).catch(()=>console.log(0))" 2>/dev/null | tr -d ' \r')
+          "fetch('http://127.0.0.1:4106/nodes').then(r=>r.json()).then(d=>console.log((d.nodes||[]).length)).catch(()=>console.log('unreachable'))" 2>/dev/null | tr -d ' \r')
+        if [ "$NODE_COUNT" = "unreachable" ]; then
+          echo "nodes=unreachable"
+          echo "The runtime did not answer on :4106 — the catalogue could not be read"
+          exit 1
+        fi
         echo "nodes=${NODE_COUNT}"
         if [ "${NODE_COUNT:-0}" -eq 0 ] 2>/dev/null; then
-          echo "WARNING: No nodes loaded — run deploy.sh rebuild or unoverse update"
-          exit 1
+          echo "(none installed yet — install from the marketplace or publish from Studio)"
         fi
       register: plugin_check
       ignore_errors: yes
 
-    - name: "[11/14] Check packages directory mounted"
-      shell: |
-        cd /opt/gravity
-        if docker compose exec -T unoverse ls /app/host_packages 2>/dev/null | head -5; then
-          PKG_COUNT=$(docker compose exec -T unoverse ls /app/host_packages 2>/dev/null | wc -l | tr -d ' ')
-          echo "packages_mounted=${PKG_COUNT}"
-          [ "$PKG_COUNT" -gt 0 ]
-        else
-          echo "packages_mounted=0"
-          echo "WARNING: No packages directory — run deploy.sh or unoverse update"
-          exit 1
-        fi
-      register: packages_check
-      ignore_errors: yes
+    # NO PACKAGES CHECK. It looked for /app/host_packages, a bind mount that was retired
+    # when nodes moved to npm at runtime plus the marketplace. Nothing declares
+    # PACKAGES_PATH any more and docker-compose.yml has no such volume, so the check could
+    # only ever report 0 and tell the operator to run a command that would not fix it.
 
     - name: "[12/14] Check for errors in service logs"
       shell: |
@@ -245,11 +247,9 @@
           ── Prompt Blocks (internal :4106) ──
             {{ prompt_blocks_check.stdout_lines[0] | default('(skipped)') }}
 
-          ── Plugins & Packages ──
-          Unoverse: {{ plugin_check.stdout_lines[0] | default('(skipped)') }}
+          ── Node catalogue ──
+          {{ plugin_check.stdout_lines[0] | default('(skipped)') }}
           {{ plugin_check.stdout_lines[1] | default('') }}
-          Packages: {{ packages_check.stdout_lines[0] | default('(skipped)') }}
-          {{ packages_check.stdout_lines[1] | default('') }}
 
           ── Recent Errors in Logs ──
           {{ log_errors.stdout | default('(skipped)') }}

package/package.json

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