@techgoblin/gobstack 0.5.0-beta.6 → 0.5.0-beta.7

package/bin/goblin-init

@@ -752,7 +752,10 @@ elif [ "$DRYRUN" -eq 0 ]; then
   if [ "$VERIFY_RC" -eq 0 ]; then
     printf '  %s▙ the goblin sees you. keep the gate green.%s\n' "$C_ACCENT" "$C_RESET"
   else
-    printf '  %s▙ the goblin sees you. the gate is RED — start there.%s\n' "$C_RED" "$C_RESET"
+    # Red runs end on the concrete first command, not the mascot: the day-one verdict IS the
+    # FAIL list, and the first row's remedy line is the thing to act on (UX minor polish —
+    # the "the goblin sees you" sign-off stays a green-run line only).
+    printf '  %sstart with the first FAIL above — its remedy line says the fix.%s\n' "$C_RED" "$C_RESET"
   fi
 fi
 

package/bin/goblin-verify

@@ -268,7 +268,17 @@ if [ -n "$ONLY" ]; then
 fi
 
 if [ ! -f "$CONFIG" ]; then
-  g_err "not installed: $CONFIG is absent. Run: goblin-install --target $ROOT --class <software|service|game|research|fleet>"
+  # Not installed. When PWD is not the target's own project root, the FIRST suggestion is to
+  # go to the repo you meant, and the install command is named second WITH its target spelled
+  # out — an out-of-context `goblin-install --target $PWD` is how a scratch directory gets
+  # initialized by accident (review 2 §1.6). Exit stays 2.
+  if [ "$ROOT" != "$PWD" ]; then
+    g_err "not installed: $CONFIG is absent — and $PWD is not the installed repo ($ROOT)."
+    g_err "fix: cd to your project repo, then re-run gob verify."
+    g_err "    (installing here would initialize $PWD: goblin-install --target $PWD --class <software|service|game|research|fleet>)"
+  else
+    g_err "not installed: $CONFIG is absent. Run: goblin-install --target $ROOT --class <software|service|game|research|fleet>"
+  fi
   exit 2
 fi
 

package/docs/GUIDE.md

@@ -83,7 +83,8 @@ You need node ≥ 18 (for the npm shim only), beyond the row above.
     npm i -g @techgoblin/gobstack
 
 This puts **two** commands on your PATH — `gob` and `goblin`, both the same node shim over the
-bash engine. The docs say `gob` throughout; either works.
+bash engine. The docs say `gob` throughout; `goblin` remains as a legacy alias for existing
+scripts.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@techgoblin/gobstack",
-  "version": "0.5.0-beta.6",
+  "version": "0.5.0-beta.7",
   "description": "Agent-discipline toolkit: one verify command, an enforcement matrix, and LIMITS. bash engine, npm shim.",
   "bin": {
     "goblin": "bin/goblin.js",