claude-plan-review 0.3.0 → 0.3.2

package/README.md

@@ -60,15 +60,6 @@ npx  claude-plan-review init --published     # if you have Node
 `--published` makes the hook run via the package runner (`bunx`/`npx`), so it works on
 any machine — nothing to keep in your repo but the one settings entry.
 
-### Option B — from a local clone (for hacking on it)
-
-```bash
-git clone https://github.com/pavlo-petrychenko/claude-plan-review
-cd claude-plan-review
-bun install                                  # or: npm install
-bun  src/cli.js init /path/to/your/project   # …or…
-node src/cli.js init /path/to/your/project   # writes an absolute-path hook command
-```
 
 ### All projects at once (global)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-plan-review",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "Review, comment on, and approve/reject Claude Code plans in a local GitHub-style web UI — with persistent comments, version history, and diffs.",
   "type": "module",
   "bin": {

package/src/channels/gh.js

@@ -73,11 +73,13 @@ export function api(method, path, body) {
     }
   }
   const errText = `${r.stderr}${r.stdout}`.trim();
-  // gh surfaces a "(HTTP 404)"/"(HTTP 403)" + scope hint when the token can't touch gists
-  const needsGistScope =
-    /gist/i.test(errText) && /(scope|HTTP 40[34]|Not Found|requires)/i.test(errText);
+  const httpStatus = Number(errText.match(/HTTP (\d{3})/)?.[1]) || null;
+  // A genuine missing-scope error names the scope explicitly ("requires the
+  // 'gist' scope"). A bare 404 just means the gist is gone — don't conflate them.
+  const needsGistScope = /gist/i.test(errText) && /scope|requires/i.test(errText);
   return {
     ok: false,
+    httpStatus,
     error: errText || (r.spawnError ? String(r.spawnError.message || r.spawnError) : "gh failed"),
     needsGistScope,
   };

package/src/channels/gist.js

@@ -47,12 +47,15 @@ export function available() {
 }
 
 function ghError(res) {
+  // Only blame the scope when the token actually lacks it — otherwise surface
+  // gh's real error so a deleted gist / network failure isn't misdiagnosed.
+  const missingScope = res.needsGistScope && !gh.status().scopes.includes("gist");
   const e = new Error(
-    res.needsGistScope
-      ? `GitHub rejected the gist write — your gh token likely lacks the 'gist' scope. Run: ${REFRESH_CMD}`
+    missingScope
+      ? `GitHub rejected the gist write — your gh token lacks the 'gist' scope. Run: ${REFRESH_CMD}`
       : res.error || "gh request failed",
   );
-  e.fixCommand = res.needsGistScope ? REFRESH_CMD : null;
+  e.fixCommand = missingScope ? REFRESH_CMD : null;
   return e;
 }
 
@@ -87,6 +90,10 @@ export function update({ id: gistId, markdown, description, filename, oldFilenam
     description: description ?? "",
     files: { [fileKey]: filePatch },
   });
+  // The bound gist was deleted on GitHub — recreate one and re-bind instead of failing.
+  if (!res.ok && res.httpStatus === 404) {
+    return create({ markdown, description, filename: newName });
+  }
   if (!res.ok) throw ghError(res);
   return {
     id: res.data.id,

package/src/cli.js

@@ -35,12 +35,13 @@ function chooseRuntime(args) {
 
 function hookCommand(args) {
   const runtime = chooseRuntime(args);
-  // global install → use the bare `claude-plan-review` command (resolved via PATH at hook time).
-  // We intentionally do NOT hardcode an absolute path: version managers like fnm/nvm expose
-  // bins via per-shell paths that don't persist across sessions.
+  // global install → always route through the package runner (npx/bunx), never the bare
+  // `claude-plan-review` command. Version managers like fnm/nvm expose global bins only via a
+  // per-shell PATH set up by interactive shell init. `canRun` succeeds here (init runs in an
+  // interactive shell) but Claude Code fires hooks in a NON-interactive shell where that PATH
+  // is absent, so the bare command resolves at init time yet fails — silently — at hook time.
+  // `npx`/`bunx` are inherited reliably from Claude Code's launching env, so they work either way.
   if (args.includes("--global")) {
-    if (canRun("claude-plan-review")) return "claude-plan-review hook";
-    // not on PATH → fall back to the package runner
     return runtime === "node" ? "npx claude-plan-review hook" : "bunx claude-plan-review hook";
   }
   if (args.includes("--published") || args.includes("--bunx")) {