pan-wizard 2.9.0 → 2.9.1

package/commands/pan/resume.md

@@ -26,6 +26,66 @@ Routes to the resume-project workflow which handles:
 @~/.claude/pan-wizard-core/workflows/resume-project.md
 </execution_context>
 
+<handoff_consumption>
+When a `.continue-here.md` file exists, parse it as structured handoff data before presenting options.
+
+**Required extraction (in order):**
+1. `position.next_task` → This is the FIRST thing to tell the user
+2. `blockers` → If non-empty, surface BEFORE offering to continue
+3. `decisions` → Load into context so they are not re-debated
+4. `progress.test_baseline` + `progress.test_current` → Verify current test count matches `test_current` (detect drift since pause)
+5. `context.next_action` → Use as the default suggested action
+
+**Resume validation:**
+- If `test_current` at resume time differs from stored value → warn user: "Test count changed since pause ({stored} → {current}). Someone else may have committed."
+- If `position.next_task` references a task not in the plan → warn: plan may have been revised since pause
+- If `blockers` exist → present them and ask if resolved before continuing
+
+**Anti-pattern:**
+```
+BAD:  Resume reads .continue-here.md, ignores position, re-reads entire plan from scratch
+      → Wastes context on already-completed work, may re-implement done tasks
+GOOD: Resume extracts position.next_task, skips completed tasks, starts exactly where paused
+```
+</handoff_consumption>
+
+<routing_decision_tree>
+Use this decision tree to select the correct resumption path. Evaluate top-to-bottom; take the FIRST match.
+
+```
+IF .planning/ does not exist:
+  → "No project found. Run /pan:new-project to get started."
+  → STOP
+
+ELSE IF .continue-here.md exists:
+  → PARSE handoff file using <handoff_consumption> protocol
+  → PRESENT: position, blockers, next action
+  → ROUTE to the command that was paused (exec-phase, plan-phase, etc.)
+
+ELSE IF state.md exists AND has status "in_progress":
+  → FIND incomplete work: plans without summaries, phases mid-execution
+  → IF incomplete phase found:
+    → PRESENT phase status + what remains
+    → OFFER: continue execution (/pan:exec-phase) or verify (/pan:verify-phase)
+  → IF no incomplete work but active milestone:
+    → PRESENT milestone progress
+    → OFFER: next unplanned phase (/pan:plan-phase) or audit (/pan:milestone-audit)
+
+ELSE IF state.md exists AND has status "blocked":
+  → PRESENT blockers from state.md
+  → OFFER: debug (/pan:debug) or unblock manually
+
+ELSE IF state.md exists AND has status "completed":
+  → "Current milestone is complete. Run /pan:milestone-done or /pan:milestone-new."
+  → STOP
+
+ELSE (state.md missing or unreadable):
+  → ATTEMPT reconstruction from .planning/ artifacts
+  → IF reconstruction succeeds: re-enter tree above
+  → IF reconstruction fails: "State is corrupted. Run /pan:new-project or restore from git."
+```
+</routing_decision_tree>
+
 <process>
 **Follow the resume-project workflow** from `@~/.claude/pan-wizard-core/workflows/resume-project.md`.
 
@@ -33,9 +93,9 @@ The workflow handles all resumption logic including:
 
 1. Project existence verification
 2. state.md loading or reconstruction
-3. Checkpoint and incomplete work detection
+3. Checkpoint and incomplete work detection — **parse using `<handoff_consumption>` protocol**
 4. Visual status presentation
 5. Context-aware option offering (checks context.md before suggesting plan vs discuss)
-6. Routing to appropriate next command
+6. Routing to appropriate next command — **following `<routing_decision_tree>`**
 7. Session continuity updates
    </process>

package/commands/pan/verify-phase.md

@@ -33,6 +33,48 @@ Phase: $ARGUMENTS (optional)
 Context files are resolved inside the workflow (`init verify-work`) and delegated via `<files_to_read>` blocks.
 </context>
 
+<investigate_before_judging>
+Never claim a feature works or doesn't work without reading the implementation first.
+Before each verification judgment:
+1. Read the source file(s) that implement the feature
+2. Read the test file(s) that cover it
+3. Run the tests
+4. Only then state your assessment with file:line evidence
+Do not speculate about code you have not opened.
+</investigate_before_judging>
+
+<citation_requirement>
+Every verdict (PASS, PARTIAL, FAIL) MUST include at least one file:line citation as evidence.
+
+**Before writing any judgment, scan your draft for unsourced claims.** If you find an assertion without evidence, stop and gather it before continuing.
+
+Format: `verdict: PASS — feature works as specified (src/billing.ts:42, tests/billing.test.ts:18-35)`
+
+**Grounding rules:**
+- PASS requires: file:line where the feature is implemented + test file:line where it's verified
+- PARTIAL requires: file:line showing what works + description of what's missing with expected location
+- FAIL requires: file:line showing the defect OR absence (grep result showing the expected function/export doesn't exist)
+- "I checked and it's not there" is NOT evidence — show the grep command and its empty result
+
+**Anti-pattern:**
+```
+BAD:  "FAIL — the retry logic doesn't handle timeouts"
+      → No evidence. Maybe it does handle timeouts and you didn't read far enough.
+GOOD: "FAIL — retry logic at api/client.ts:67-89 catches ConnectionError but not TimeoutError.
+       Grep for 'TimeoutError' in api/: 0 matches. tests/client.test.ts has no timeout test cases."
+```
+</citation_requirement>
+
+<reflexion_loop>
+After initial verification of each requirement:
+1. Score each requirement: PASS / PARTIAL / FAIL
+2. For PARTIAL or FAIL: state specifically what is missing or broken
+3. Re-read the requirement text and the implementation — did you miss anything?
+4. Revise the score if the re-read reveals evidence you overlooked
+5. Report only final scores after this review cycle
+This prevents premature FAIL verdicts from incomplete investigation.
+</reflexion_loop>
+
 <process>
 Execute the verify-work workflow from @~/.claude/pan-wizard-core/workflows/verify-phase.md end-to-end.
 Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pan-wizard",
-  "version": "2.9.0",
+  "version": "2.9.1",
   "description": "A lightweight workflow automation and context engineering system for Claude Code, OpenCode, Gemini CLI, Codex, and Copilot CLI.",
   "bin": {
     "pan-wizard": "bin/install.js"

package/pan-wizard-core/bin/lib/constants.cjs

@@ -123,7 +123,7 @@ const FOCUS_DIR = 'focus';
 const AUTO_RUN_FILE = 'auto-run.json';
 
 /** Focus auto-runner categories */
-const FOCUS_CATEGORIES = ['cleanup', 'tests', 'stability', 'features', 'docs', 'optimize'];
+const FOCUS_CATEGORIES = ['cleanup', 'tests', 'stability', 'features', 'docs', 'optimize', 'prompts'];
 
 /** Category → priority index range (indices into PRIORITY_LEVELS) */
 const CATEGORY_PRIORITY_RANGE = {
@@ -133,6 +133,7 @@ const CATEGORY_PRIORITY_RANGE = {
   features:  { min: 3, max: 5 },  // P3-P5
   docs:      { min: 5, max: 6 },  // P5-P6
   optimize:  { min: 1, max: 4 },  // P1-P4
+  prompts:   { min: 0, max: 6 },  // P0-P6 (all priorities — prompt order is authoritative)
 };
 
 /** Category → default mode + budget */
@@ -143,6 +144,7 @@ const CATEGORY_DEFAULTS = {
   features:  { mode: 'features', budget: 50 },
   docs:      { mode: 'balanced', budget: 30 },
   optimize:  { mode: 'balanced', budget: 50 },
+  prompts:   { mode: 'balanced', budget: 100 },
 };
 
 /** Doc files to scan for staleness (focus sync) */

package/pan-wizard-core/bin/lib/focus.cjs

@@ -783,6 +783,11 @@ function determineStopReason(cycle, run) {
   if (run.totals.cycles_completed >= run.max_cycles) return 'max_cycles';
   if (cycle.items_completed === 0) return 'zero_completed';
 
+  // Prompts category: stop when all prompts are completed
+  if (run.category === 'prompts' && cycle.prompts_remaining === 0) {
+    return 'prompts_complete';
+  }
+
   // Optimize category: stop when efficiency drops below threshold of previous cycle
   if (run.category === 'optimize' && run.cycles.length >= 2) {
     const prev = run.cycles[run.cycles.length - 2];