@theglitchking/persistent-planning 3.4.1 → 3.4.2

package/.claude-plugin/marketplace.json

@@ -6,13 +6,13 @@
   },
   "metadata": {
     "description": "Official marketplace for persistent-planning - Persistent markdown-based planning for Claude Code. Context engineering pattern with task directories, progress tracking, and working memory that persists across sessions.",
-    "version": "3.4.1"
+    "version": "3.4.2"
   },
   "plugins": [
     {
       "name": "persistent-planning",
       "description": "Persistent markdown-based planning for Claude Code. Uses on-disk markdown files as working memory for planning, progress tracking, and knowledge storage. Plans persist across sessions and support multiple concurrent tasks.",
-      "version": "3.4.1",
+      "version": "3.4.2",
       "author": {
         "name": "TheGlitchKing"
       },

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "persistent-planning",
-  "version": "3.4.1",
+  "version": "3.4.2",
   "description": "Persistent markdown-based planning with task directories, progress tracking, and context engineering for multi-step Claude Code workflows",
   "author": {
     "name": "TheGlitchKing"

package/CHANGELOG.md

@@ -2,6 +2,39 @@
 
 All notable changes to this project will be documented in this file.
 
+## [3.4.2] - 2026-09-05
+
+### Changed — the local `update` guard moves upstream into the runtime
+
+3.4.0 added a `preAction` guard in `bin/persistent-planning.js` because the
+runtime's `update` resolved installation state from `<cwd>/node_modules` and
+`CLAUDE_PLUGIN_ROOT` only, found neither in a marketplace-only install, and
+exited 0 after an `npm update` that touched nothing. The guard worked, but it
+was a workaround living in one plugin while every sibling stayed broken —
+babel-fish#17 was the same defect reported against babel-fish.
+
+Fixed properly in `@theglitchking/claude-plugin-runtime` 0.1.1, which this
+release requires. `resolveInstall()` there probes npm dep → `CLAUDE_PLUGIN_ROOT`
+→ the marketplace record in `~/.claude/plugins/installed_plugins.json`, so the
+26-line guard is deleted rather than reimplemented.
+
+The result is strictly better than the guard it replaces. Previously a
+marketplace install satisfied the guard and fell through to a no-op `npm update`
+that exited 0; now it is recognised, named by path, and refused with a pointer
+at `/plugin` — the only thing that can actually update a plugin-cache copy.
+
+The dependency floor is `^0.1.1`, not `^0.1.0`: the shared plugin dep tree at
+`~/.claude/plugins/npm-cache` pins the runtime at 0.1.0 in its lockfile, and
+0.1.0 still satisfies `^0.1.0`, so the broken copy would have survived.
+
+### Fixed — the CLI test depended on the developer's own machine
+
+`tests/run.sh` ran `update` in a temp workspace but inherited the real `$HOME`,
+so once the runtime learned to read `~/.claude/plugins/installed_plugins.json`
+the assertion passed or failed depending on whether the person running it
+happened to have the plugin installed. `HOME` is now overridden, and the
+marketplace branch is asserted against a fixture rather than a machine.
+
 ## [3.4.1] - 2026-09-04
 
 ### Fixed — the SessionStart hook could not survive a missing runtime (#18)

package/bin/persistent-planning.js

@@ -55,32 +55,6 @@ program
   .description("Persistent markdown-based planning for Claude Code.")
   .version(version);
 
-// The runtime's `update` resolves the installed version, finds none in a
-// marketplace-only install, prints "Current: (not installed) / Now: (not installed)"
-// and exits 0 -- a clean success for a no-op. Fail before it gets that far, and say
-// where we looked. Same defect as runRelink's missing third probe (issue #10, fix #4).
-// Deliberately NOT including the package this CLI runs from: under
-// `npx --no @theglitchking/persistent-planning update` that copy always exists, which
-// is what let the original bug report see a clean exit 0 for a no-op. Only a *managed*
-// install -- a project dependency or a marketplace plugin root -- is updatable.
-function installCandidates(cwd) {
-  const out = [join(cwd, "node_modules", "@theglitchking", "persistent-planning", "package.json")];
-  if (process.env.CLAUDE_PLUGIN_ROOT) out.push(join(process.env.CLAUDE_PLUGIN_ROOT, "package.json"));
-  return out;
-}
-
-program.hook("preAction", (_thisCmd, actionCmd) => {
-  if (actionCmd.name() !== "update") return;
-  const candidates = installCandidates(process.cwd());
-  if (candidates.some((p) => existsSync(p))) return;
-  console.error("update failed: no managed install of @theglitchking/persistent-planning found.");
-  console.error("Looked in:");
-  for (const p of candidates) console.error(`  ${p}`);
-  console.error("\nInstall it with `npm i -D @theglitchking/persistent-planning`,");
-  console.error("or update the marketplace plugin with `/plugin` inside Claude Code.");
-  process.exit(1);
-});
-
 registerUpdateCommands(program, {
   packageName: PKG,
   pluginName: "persistent-planning",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theglitchking/persistent-planning",
-  "version": "3.4.1",
+  "version": "3.4.2",
   "description": "Persistent markdown-based planning with task directories, progress tracking, and context engineering for multi-step Claude Code workflows",
   "type": "module",
   "bin": {
@@ -55,7 +55,7 @@
   },
   "homepage": "https://github.com/TheGlitchKing/persistent-planning#readme",
   "dependencies": {
-    "@theglitchking/claude-plugin-runtime": "^0.1.0",
+    "@theglitchking/claude-plugin-runtime": "^0.1.1",
     "commander": "^14.0.0"
   },
   "devDependencies": {