unoverse 0.1.95 → 0.1.96

package/operator/lib/common.sh

@@ -1,7 +1,20 @@
 #!/usr/bin/env bash
 # Shared colors, helpers, and constants
 
-GRAVITY_VERSION="1.0.0"
+# THE VERSION IS THE CLI'S, READ FROM IT. This was the literal "1.0.0", hardcoded when the
+# operator was a script in a repo and never touched again — so `unoverse help` announced
+# v1.0.0 while the published CLI was on 0.1.95, and the one number a developer uses to say
+# which version they are running was wrong by two hundred releases.
+#
+# THE MONOREPO PATH IS TRIED FIRST, and the order matters. Two levels up from scripts/lib
+# is the PLATFORM's package.json, which is genuinely 1.0.0 — so looking there first found a
+# real version that was not this CLI's, and reported it confidently. packages/cli exists
+# only in the monorepo; published, that path misses and the package's own is two levels up.
+GRAVITY_VERSION=$(
+  node -p "require('$GRAVITY_LIB/../../packages/cli/package.json').version" 2>/dev/null \
+  || node -p "require('$GRAVITY_LIB/../../package.json').version" 2>/dev/null \
+  || echo "unknown"
+)
 DOCR_REGISTRY="registry.digitalocean.com"
 
 # Colors

package/operator/lib/help.sh

@@ -25,8 +25,13 @@ cmd_help() {
   # THE ARGUMENT IS ON THE LINE, not in a footnote. It read as a special case for people
   # with two clouds; it is simply how the command is shaped. A cloud is optional when only
   # one ground exists and required when two do.
-  echo -e "    ${GREEN}deploy${NC}      Ship it to a server ${DIM}· aws or digitalocean${NC}"
-  echo -e "    ${GREEN}destroy${NC}     Take it down ${DIM}· aws or digitalocean, shows what goes and what stays${NC}"
+  # SHOW THE COMMAND, not a description of it. "aws or digitalocean" told a reader the
+  # clouds exist without telling them what to type, so the shape of the command still had
+  # to be guessed. Print the line they will actually run.
+  echo -e "    ${GREEN}deploy${NC}      Ship it to a server ${DIM}(first run asks which cloud)${NC}"
+  echo -e "                ${DIM}unoverse deploy aws   ·   unoverse deploy digitalocean${NC}"
+  echo -e "    ${GREEN}destroy${NC}     Take it down ${DIM}(shows what goes, and what stays)${NC}"
+  echo -e "                ${DIM}unoverse destroy aws   ·   unoverse destroy digitalocean${NC}"
   echo -e "    ${GREEN}db-allow${NC}    Let this machine reach the database ${DIM}(run it when you change network)${NC}"
   echo ""
   # Owner-only lane. Printed ONLY when publish.sh is present, so a starter kit never

package/package.json

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