unoverse 0.1.133 → 0.1.135

package/lib/create/index.mjs

@@ -42,8 +42,9 @@ export async function create(nameArg) {
         console.log(`\n  ${dim(`${target === "." ? "This folder" : `./${target}`} is already a universe. Picking setup back up.`)}\n`);
         rl.close();
         const here2 = dirname(fileURLToPath(import.meta.url));
-        const vend = resolve(here2, "../operator/operator.sh");
-        const op = existsSync(vend) ? vend : resolve(here2, "../../../scripts/operator.sh");
+        // Depths are from lib/create/, NOT lib/ — see the note at the second copy below.
+        const repo2 = resolve(here2, "../../../../scripts/operator.sh");
+        const op = existsSync(repo2) ? repo2 : resolve(here2, "../../operator/operator.sh");
         const r2 = spawnSync("bash", [op, "init"], { stdio: "inherit", cwd: target });
         process.exit(r2.status ?? 0);
       }
@@ -91,11 +92,21 @@ export async function create(nameArg) {
       rl.close();
       console.log("");
       // This package's own operator, run against the folder just scaffolded.
+      // COUNT FROM lib/create/, not lib/. These four segments moved down a directory in
+      // the create.mjs split and kept the depths they had at lib/, so the vendored copy
+      // was looked for at lib/operator/ (never there) and the fallback landed on
+      // <node_modules>/scripts/operator.sh. Every universe scaffolded, then died on
+      // "setup did not finish" at the last step.
+      //
+      // IN-REPO WINS, as in bin/unoverse.mjs: the vendored copy is a prepack artifact, so
+      // preferring it makes every edit to scripts/lib invisible while developing here. A
+      // published package has no ../../../../scripts, so there the vendored copy is the
+      // only one and still wins.
       const here = dirname(fileURLToPath(import.meta.url));
-      const vendored = resolve(here, "../operator/operator.sh");
-      const operatorScript = existsSync(vendored)
-        ? vendored
-        : resolve(here, "../../../scripts/operator.sh");
+      const inRepo = resolve(here, "../../../../scripts/operator.sh");
+      const operatorScript = existsSync(inRepo)
+        ? inRepo
+        : resolve(here, "../../operator/operator.sh");
       // NO authoring skill here, deliberately. Building components, nodes and agent
       // skills is STUDIO work and its skill ships with Studio projects. What a universe
       // offers Claude Code is the canvas MCP (.mcp.json in the scaffold): building and

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

@@ -177,8 +177,14 @@
     # had already been fixed two minutes earlier by this very playbook.
     #
     # The question is "is anything wrong NOW", so the window starts when the services did.
+    # `{% raw %}` because DOCKER'S TEMPLATE LANGUAGE AND JINJA SHARE A SYNTAX. `-f
+    # '{{.State.StartedAt}}'` is a Go template for docker and a Jinja expression for
+    # Ansible, which parses it first and dies on `unexpected '.'` — the whole task fails
+    # before the shell ever runs. This block uses no Ansible variables, so the honest fix is
+    # to hand it over untouched rather than escape the braces one at a time.
     - name: "[12/14] Check for errors in service logs"
       shell: |
+        {% raw %}
         cd /opt/gravity
         # Newest container start: everything before it belongs to a previous run.
         SINCE=$(docker compose ps -q 2>/dev/null | xargs -r docker inspect -f '{{.State.StartedAt}}' 2>/dev/null | sort | tail -1)
@@ -190,6 +196,7 @@
         else
           echo "No errors since the services started"
         fi
+        {% endraw %}
       register: log_errors
       ignore_errors: yes
 

package/package.json

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