pan-wizard 3.29.0 → 3.31.0

package/pan-wizard-core/workflows/settings.md

@@ -31,7 +31,7 @@ Parse current values (default to `true` if not present):
 - `workflow.nyquist_validation` — validation architecture research during plan-phase
 - `model_profile` — which model each agent uses (default: `balanced`)
 - `routing.strategy` — how model tiers are adjusted at runtime (default: `static`)
-- `git.branching_strategy` — branching approach (default: `"none"`)
+- `branching_strategy` — branching approach (default: `"none"`; a top-level key — a nested `git.branching_strategy` is ignored when the top-level key exists, as it does in every config `config-ensure-section` creates — write the top-level key)
 </step>
 
 <step name="present_settings">
@@ -131,9 +131,7 @@ Merge new settings into existing config.json:
     "auto_advance": true/false,
     "nyquist_validation": true/false
   },
-  "git": {
-    "branching_strategy": "none" | "phase" | "milestone"
-  },
+  "branching_strategy": "none" | "phase" | "milestone",
   "routing": {
     "strategy": "static" | "complexity"
   }

package/pan-wizard-core/workflows/todo-add.md

@@ -19,7 +19,7 @@ Extract from init JSON: `commit_docs`, `date`, `timestamp`, `todo_count`, `todos
 
 Ensure directories exist:
 ```bash
-mkdir -p .planning/todos/pending .planning/todos/done
+mkdir -p .planning/todos/pending .planning/todos/completed
 ```
 
 Note existing areas from the todos array for consistency in infer_area step.

package/pan-wizard-core/workflows/todo-check.md

@@ -105,7 +105,7 @@ Use AskUserQuestion:
 - header: "Action"
 - question: "This todo relates to Phase [N]: [name]. What would you like to do?"
 - options:
-  - "Work on it now" — move to done, start working
+  - "Work on it now" — mark it completed, start working
   - "Add to phase plan" — include when planning Phase [N]
   - "Brainstorm approach" — think through before deciding
   - "Put it back" — return to list
@@ -116,7 +116,7 @@ Use AskUserQuestion:
 - header: "Action"
 - question: "What would you like to do with this todo?"
 - options:
-  - "Work on it now" — move to done, start working
+  - "Work on it now" — mark it completed, start working
   - "Create a phase" — /pan:add-phase with this scope
   - "Brainstorm approach" — think through before deciding
   - "Put it back" — return to list
@@ -125,8 +125,9 @@ Use AskUserQuestion:
 <step name="execute_action">
 **Work on it now:**
 ```bash
-mv ".planning/todos/pending/[filename]" ".planning/todos/done/"
+node ~/.claude/pan-wizard-core/bin/pan-tools.cjs todo complete "[filename]"
 ```
+This moves it to `.planning/todos/completed/` with a `completed:` date — the directory `init todos` and `/pan:progress` count.
 Update state.md todo count. Present problem/solution context. Begin work or ask how to proceed.
 
 **Add to phase plan:**
@@ -150,11 +151,11 @@ Re-run `init todos` to get updated count, then update state.md "### Pending Todo
 </step>
 
 <step name="git_commit">
-If todo was moved to done/, commit the change:
+If the todo was completed, commit the change:
 
 ```bash
 git rm --cached .planning/todos/pending/[filename] 2>/dev/null || true
-node ~/.claude/pan-wizard-core/bin/pan-tools.cjs commit "docs: start work on todo - [title]" --files .planning/todos/done/[filename] .planning/state.md
+node ~/.claude/pan-wizard-core/bin/pan-tools.cjs commit "docs: start work on todo - [title]" --files .planning/todos/completed/[filename] .planning/state.md
 ```
 
 Tool respects `commit_docs` config and gitignore automatically.
@@ -172,5 +173,5 @@ Confirm: "Committed: docs: start work on todo - [title]"
 - [ ] Appropriate actions offered
 - [ ] Selected action executed
 - [ ] state.md updated if todo count changed
-- [ ] Changes committed to git (if todo moved to done/)
+- [ ] Changes committed to git (if the todo was completed)
 </success_criteria>

package/scripts/build-agent-plugin.js

@@ -150,6 +150,8 @@ function hookCommands(rootVar) {
     contextMonitorCommand: cmd('pan-context-monitor.js'),
     costLoggerCommand: cmd('pan-cost-logger.js'),
     traceLoggerCommand: cmd('pan-trace-logger.js'),
+    stopGuardCommand: cmd('pan-stop-guard.js'),
+    stateReinjectCommand: cmd('pan-state-reinject.js'),
   };
 }
 
@@ -166,6 +168,8 @@ function emitCopilotNamespace(agentsSrc, nsDir) {
     content = lib.rewriteAgentReferenceCopy(content, TOKEN_PREFIX);
     content = lib.stripThinkingFrontmatter(content, 'copilot');
     content = lib.convertClaudeToCopilotAgent(content);
+    // The agent carries the root token, so it carries what the token means.
+    if (content.includes(TOKEN_PREFIX)) content = content.replace(/\s*$/, '\n\n' + lib.agentPluginSkillAdapterNote('agent') + '\n');
     fs.writeFileSync(path.join(agentsDest, f.replace(/\.md$/, '.agent.md')), content);
     agents++;
   }

package/scripts/build-hooks.js

@@ -22,7 +22,8 @@ const HOOKS_TO_COPY = [
   'pan-statusline.js',
   'pan-cost-logger.js',
   'pan-trace-logger.js',
-  'pan-stop-guard.js'
+  'pan-stop-guard.js',
+  'pan-state-reinject.js'
 ];
 
 function build() {

package/scripts/build-plugin.js

@@ -169,6 +169,15 @@ function main() {
     );
   }
 
+  // 7. Eval suite (market-ideas M4). `claude plugin eval` reads `evals/` at the
+  // plugin root; the cases live in harness/plugin-evals/ beside the harness
+  // scenarios they come from. harness/ is not in the npm package, so a build from
+  // an installed copy has no suite to copy and the plugin ships without one.
+  const evalsSrc = path.join(ROOT, 'harness', 'plugin-evals');
+  if (fs.existsSync(evalsSrc)) {
+    fs.cpSync(evalsSrc, path.join(OUT, 'evals'), { recursive: true });
+  }
+
   // Sanity report
   const count = (p) => { try { return fs.readdirSync(p).length; } catch { return 0; } };
   console.log('PAN plugin built at', path.relative(ROOT, OUT));
@@ -176,6 +185,7 @@ function main() {
   console.log('  agents:', count(path.join(OUT, 'agents')));
   console.log('  hooks:', count(path.join(OUT, 'hooks')));
   console.log('  workflows:', workflowScripts.length);
+  console.log('  eval cases:', count(path.join(OUT, 'evals')) ? fs.readdirSync(path.join(OUT, 'evals'), { withFileTypes: true }).filter(e => e.isDirectory()).length : 0);
   console.log('  version:', pkg.version);
 }
 

package/scripts/npm-dist-tag.js

@@ -0,0 +1,47 @@
+#!/usr/bin/env node
+/**
+ * Print the npm dist-tag a version publishes under: `next` for a prerelease
+ * (`3.31.0-rc.1`), `latest` otherwise.
+ *
+ * WHY. The release workflow ran `npm publish` with no `--tag`, and npm's default
+ * tag is `latest` — so a release candidate would have become what
+ * `npm install pan-wizard` resolves to for every user (market-ideas queue M1,
+ * 2026-09-21). Publishing a candidate under `next` keeps it installable by name
+ * (`pan-wizard@next`, `pan-wizard@3.31.0-rc.1`) without moving anyone onto it.
+ *
+ * A version that is not `major.minor.patch[-prerelease]` exits 1 rather than
+ * guessing a tag: publishing junk under `latest` is the failure this prevents.
+ *
+ * Usage:
+ *   node scripts/npm-dist-tag.js            # the tag for package.json's version
+ *   node scripts/npm-dist-tag.js 3.31.0-rc.1
+ */
+
+'use strict';
+
+const path = require('path');
+const { parse } = require('./deprecate-old-versions.js');
+
+/**
+ * @param {string} version
+ * @returns {'latest'|'next'|null} null when the version does not parse
+ */
+function distTagFor(version) {
+  const v = parse(version);
+  if (!v) return null;
+  return v.pre === null ? 'latest' : 'next';
+}
+
+function main() {
+  const version = process.argv[2] || require(path.join(__dirname, '..', 'package.json')).version;
+  const tag = distTagFor(version);
+  if (!tag) {
+    process.stderr.write(`npm-dist-tag: '${version}' is not a semver version — refusing to pick a tag\n`);
+    process.exit(1);
+  }
+  process.stdout.write(tag + '\n');
+}
+
+module.exports = { distTagFor };
+
+if (require.main === module) main();

package/scripts/plugin-path.js

@@ -49,8 +49,13 @@ function fail(message) {
 function build() {
   try {
     // Relay the builder's stdout to stderr so stdout stays single-line.
+    // PAN_PLUGIN_OUT redirects the builder; this script prints PLUGIN_DIR, so a value
+    // inherited from the caller's environment would build one place and point the
+    // marketplace at another (3.28.0 review, LOW). Build where the path says.
+    const env = { ...process.env };
+    delete env.PAN_PLUGIN_OUT;
     const out = execFileSync(process.execPath, [path.join(ROOT, 'scripts', 'build-plugin.js')], {
-      cwd: ROOT, encoding: 'utf8', stdio: ['ignore', 'pipe', 'pipe'],
+      cwd: ROOT, encoding: 'utf8', stdio: ['ignore', 'pipe', 'pipe'], env,
     });
     if (out) process.stderr.write(out);
   } catch (err) {

package/scripts/test-surface.cjs

@@ -49,24 +49,26 @@ const CONTENT_DIRS = Object.freeze({
   'pan-wizard-core/workflows': /\.(md|js)$/,
 });
 
-// Hooks the installer wires outside HOOK_EVENT_MAP (bin/install.js: the Stop guard
-// on the two runtimes with a Stop event, the statusline on Claude Code only).
+// Registrations the installer wires outside HOOK_EVENT_MAP: the statuslines. (The
+// stop guard moved INTO the table on 2026-09-23 as its `stop` slot, so its Gemini
+// row follows Gemini's vocabulary — AfterAgent — instead of a hand-written `Stop`
+// that Gemini never read.)
 const EXTRA_HOOK_ROWS = Object.freeze([
-  { runtime: 'claude', hook: 'pan-stop-guard.js', event: 'Stop', surface: 'settings.json' },
-  { runtime: 'gemini', hook: 'pan-stop-guard.js', event: 'Stop', surface: 'settings.json' },
   { runtime: 'claude', hook: 'pan-statusline.js', event: 'statusLine', surface: 'settings.json' },
-  // Gemini and Copilot register a statusline too. Both were missing here until a real
-  // install was read back (2026-09-17) — the registry's whole purpose is that a shipped
-  // registration cannot sit outside it, so a hand-maintained list is the weak point and
-  // these rows are the evidence for why it must be checked against an install.
-  { runtime: 'gemini', hook: 'pan-statusline.js', event: 'statusLine', surface: 'settings.json' },
+  // Copilot registers a statusline too; it was missing here until a real install was
+  // read back (2026-09-17) — the registry's whole purpose is that a shipped
+  // registration cannot sit outside it, so a hand-maintained list is the weak point.
   // Copilot keeps its hooks in hooks/pan.json but its statusline in copilot/settings.json.
+  // Gemini's row is gone: Gemini CLI has no statusline command, so PAN stopped
+  // writing one there (R29).
   { runtime: 'copilot', hook: 'pan-statusline.js', event: 'statusLine', surface: 'copilot/settings.json' },
 ]);
 const EVENT_HOOKS = Object.freeze({
   sessionStart: ['pan-check-update.js'],
   postToolUse: ['pan-context-monitor.js'],
   subagentStop: ['pan-cost-logger.js', 'pan-trace-logger.js'],
+  stop: ['pan-stop-guard.js'],
+  compact: ['pan-state-reinject.js'],
 });
 
 // ─── Parsers (pure) ─────────────────────────────────────────────────────────