unoverse 0.1.6 → 0.1.7

package/bin/unoverse.mjs

@@ -9,8 +9,45 @@
  */
 import { existsSync } from "node:fs";
 import { spawnSync } from "node:child_process";
+import { join, resolve } from "node:path";
 import { create } from "../lib/create.mjs";
 
+/**
+ * ONE BINARY. There is no `./unoverse` any more.
+ *
+ * A universe is a folder holding the operator lib. Walk up for it, the same way git finds
+ * a repo, so the commands work from anywhere inside your universe rather than only at its
+ * root. Found means the operator commands exist; not found means they simply are not
+ * offered, instead of being advertised and then refusing.
+ */
+function findUniverse() {
+  for (let dir = process.cwd(); ; ) {
+    if (existsSync(join(dir, "scripts/lib/common.sh"))) return dir;
+    const parent = resolve(dir, "..");
+    if (parent === dir) return null;
+    dir = parent;
+  }
+}
+
+/** Run an operator command in the universe we are standing in. */
+function operator(root, args) {
+  const r = spawnSync("bash", [join(root, "scripts/operator.sh"), ...args], {
+    stdio: "inherit",
+    cwd: root,
+  });
+  process.exit(r.status ?? 0);
+}
+
+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.
+const OPERATOR_COMMANDS = new Set([
+  "start", "stop", "check", "logs", "deploy",
+  // kept working, not advertised
+  "ground", "dev", "build", "publish", "init", "doctor", "db-setup", "db-verify", "open",
+]);
+
 const [, , cmd, ...args] = process.argv;
 
 const HELP = `
@@ -23,8 +60,7 @@ const HELP = `
   unoverse update          Update this CLI to the latest version
   unoverse help            This
 
-  Operating a running universe? That lives in your universe folder:
-    cd <your-universe> && ./unoverse
+  Standing in a universe folder adds: start · stop · check · logs · deploy
 `;
 
 switch (cmd) {
@@ -33,12 +69,9 @@ switch (cmd) {
     break;
 
   case "update": {
-    // The command people type when the CLI is stale. Inside a universe folder,
-    // update means the OPERATOR kit — defer to it. Otherwise update this package.
-    if (existsSync("./unoverse")) {
-      console.log(`\n  This folder is a universe — its own CLI owns updates:\n\n    ./unoverse update\n`);
-      process.exit(1);
-    }
+    // 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();
@@ -69,6 +102,8 @@ switch (cmd) {
   case "--help":
   case "-h":
   case undefined:
+    // In a universe, its own help prints — it knows whether this kit has the owner lane.
+    if (UNIVERSE) operator(UNIVERSE, ["help"]);
     console.log(HELP);
     break;
 
@@ -84,10 +119,10 @@ switch (cmd) {
   }
 
   default:
-    // A universe folder has its own operator CLI — point there rather than
-    // half-implementing its commands here (v0.2 absorbs them properly).
-    if (existsSync("./unoverse")) {
-      console.log(`\n  '${cmd}' is an operator command — run it in your universe:\n\n    ./unoverse ${cmd} ${args.join(" ")}\n`);
+    // The operator half, run right here. No second CLI to be sent to.
+    if (UNIVERSE && OPERATOR_COMMANDS.has(cmd)) operator(UNIVERSE, [cmd, ...args]);
+    if (OPERATOR_COMMANDS.has(cmd)) {
+      console.log(`\n  '${cmd}' operates a universe, and this folder is not one.\n  ${"cd into your universe, or run: unoverse create"}\n`);
     } else {
       console.log(`\n  Unknown command: ${cmd}\n${HELP}`);
     }

package/lib/create.mjs

@@ -133,11 +133,25 @@ export async function create(nameArg) {
       const name = resolveTarget(nameArg);
       download(name);
       ok(`universe scaffolded in ${label(name)}`);
+
+      // CREATE FINISHES THE JOB. It used to stop here and tell you to go and run
+      // `./unoverse init`, which asked for this same token a second time. The token is
+      // already in hand and already validated, so hand it over and configure now.
+      rl.close();
+      console.log("");
+      const r = spawnSync("bash", [`${name}/scripts/operator.sh`, "init"], {
+        stdio: "inherit",
+        cwd: name,
+        env: { ...process.env, UNOVERSE_DOCR_TOKEN: token },
+      });
+      if (r.status !== 0) {
+        fail("setup did not finish — run 'unoverse init' in that folder to pick it up");
+        process.exit(r.status ?? 1);
+      }
       console.log(`
   Next:${name === "." ? "" : `
     cd ${name}`}
-    ./unoverse init      ${dim("(setup wizard — have this token ready, it asks for it)")}
-    ./unoverse start
+    unoverse start
 
   ${cyan("Build with Claude:")} open the folder in Claude Code — it ships an
   authoring skill (components, nodes, agent skills) and a builder MCP that

package/package.json

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