projecta-rrr 1.21.4 → 1.21.5

package/CHANGELOG.md

@@ -4,6 +4,35 @@ All notable changes to RRR will be documented in this file.
 
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
+## [1.21.5] - 2026-04-18
+
+**Stale-global-CLI detection + `/rrr:update` global-binary refresh.**
+
+### Fixed
+
+- **`/rrr:update` now refreshes the global `projecta-rrr` CLI binary.**
+  Previously, update ran `npx --yes projecta-rrr@latest --global` which
+  updates RRR runtime files in `~/.claude/rrr/` but does NOT touch the
+  `projecta-rrr` binary installed via `npm install -g`. Result: RRR
+  slash-commands worked at the latest version, but subcommands like
+  `projecta-rrr hosted-setup` (added in 1.21.4) failed because the
+  binary on PATH was still from an older version. The update workflow
+  now additionally runs `npm install -g projecta-rrr@latest` with
+  best-effort EACCES tolerance.
+
+- **`install.js` self-detects stale global CLI** at end of install.
+  If `command -v projecta-rrr` resolves to a package.json version older
+  than the currently-running install, prints a clear warning with the
+  two fixes: `npm install -g projecta-rrr@latest` OR use
+  `npx projecta-rrr@latest <subcommand>`.
+
+### Why this matters
+
+A user reported: after `/rrr:update` from 1.20.0 to 1.21.4, running
+`projecta-rrr hosted-setup` fell through to the default RRR install
+flow ("Global/Local?" prompt). Cause: the stale v1.19.1 binary on PATH
+didn't know about `hosted-setup`. Fix lands in 1.21.5.
+
 ## [1.21.4] - 2026-04-18
 
 **One-command adoption + slash-command integration.**

package/bin/install.js

@@ -2497,6 +2497,40 @@ ${optimizationNote}
 `);
     }
   } catch { /* never block install on nudge */ }
+
+  // v1.21.5+: detect stale global CLI. When user ran via `npx projecta-rrr@latest`,
+  // the RRR runtime at ~/.claude/rrr/ is up-to-date but an older
+  // `projecta-rrr` on PATH (from a previous `npm install -g`) may still exist.
+  // Surface the mismatch so users know to run `npm install -g projecta-rrr@latest`.
+  try {
+    const pkgVersion = require('../package.json').version;
+    let onPathVersion = null;
+    try {
+      const onPathBin = execSync('command -v projecta-rrr', { stdio: ['pipe', 'pipe', 'ignore'] }).toString().trim();
+      if (onPathBin) {
+        // Read the package.json of whatever bin is on PATH
+        const realPath = fs.realpathSync(onPathBin);
+        // The bin is bin/install.js inside its package; go up to package.json
+        const binDir = path.dirname(realPath);
+        let candidate = path.dirname(binDir); // .../projecta-rrr
+        const pkgJson = path.join(candidate, 'package.json');
+        if (fs.existsSync(pkgJson)) {
+          onPathVersion = require(pkgJson).version;
+        }
+      }
+    } catch { /* no bin on PATH → not stale, no warning needed */ }
+
+    if (onPathVersion && onPathVersion !== pkgVersion) {
+      console.log(`  ${orange}━━━ Stale global CLI detected ━━━${reset}
+  ${yellow}Your RRR runtime is ${pkgVersion} but the${reset} ${cyan}projecta-rrr${reset} ${yellow}binary on PATH is ${onPathVersion}.${reset}
+  ${dim}This means RRR slash-commands are current, but the${reset} ${cyan}projecta-rrr${reset} ${dim}CLI (e.g.,${reset} ${cyan}hosted-setup${reset}${dim}) is stale.${reset}
+
+  ${dim}Fix (one of):${reset}
+    ${green}npm install -g projecta-rrr@latest${reset}
+    ${green}npx projecta-rrr@latest <subcommand>${reset}   ${dim}(always latest, slower)${reset}
+`);
+    }
+  } catch { /* never block install on stale-check */ }
 }
 
 /**

package/commands/rrr/update.md

@@ -124,6 +124,33 @@ npx --yes projecta-rrr@latest --global
 2. Should show "Wrote INSTALL_INFO.json"
 3. Should show "Quarantined X legacy/duplicate root(s)" if any were found
 
+**Then refresh the global CLI binary** (v1.21.5+ fix). The `npx` line above
+updates RRR runtime files in `~/.claude/rrr/` but does NOT update the
+`projecta-rrr` binary on the user's PATH (via `~/.npm-global/bin/` or
+equivalent). Run this additional step — it's best-effort and tolerates
+EACCES silently:
+
+```bash
+# Best-effort global CLI refresh — does NOT block update if it fails.
+# On macOS with a prefix-configured npm (~/.npm-global or nvm), this works
+# without sudo. On a raw system install it may hit EACCES — that's fine,
+# user keeps working via npx for CLI invocations.
+npm install -g projecta-rrr@latest 2>&1 | tail -5 || echo "(global CLI refresh skipped — user's npm prefix not writable; use 'npx projecta-rrr' or fix with: npm config set prefix ~/.npm-global)"
+```
+
+**After this step, verify the CLI matches:**
+
+```bash
+projecta-rrr --version 2>&1 | head -1 || which projecta-rrr
+```
+
+If the version shown is older than what just installed, print a warning:
+```
+⚠ CLI binary stale (shows vX.Y.Z, expected vA.B.C).
+  Fix: `npm install -g projecta-rrr@latest` (may need sudo).
+  Workaround: use `npx projecta-rrr <subcommand>` until fixed.
+```
+
 **If install fails:**
 Show error and STOP. Do not proceed.
 </step>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projecta-rrr",
-  "version": "1.21.4",
+  "version": "1.21.5",
   "description": "A meta-prompting, context engineering and spec-driven development system for Claude Code by Projecta.ai",
   "bin": {
     "projecta-rrr": "bin/install.js",