pan-wizard 3.31.0 → 3.32.0

package/pan-wizard-core/workflows/verify-phase.md

@@ -321,21 +321,11 @@ If human_needed: list items requiring human testing.
 
 Orchestrator routes: `passed` → update_roadmap | `gaps_found` → create/execute fixes, re-verify | `human_needed` → present to user.
 
-**Circular optimization — log verification outcome:**
+**Record the verification.** The record adds its findings to the ledger and logs the outcome to the trace (`verdict_passed`, `verdict_failed` or `verdict_needs_human`). A re-verification is the next attempt, and it closes the gaps it no longer reports:
 ```bash
-# Map status to impact and event type
-if [ "${STATUS}" = "passed" ]; then
-  node ~/.claude/pan-wizard-core/bin/pan-tools.cjs optimize trace log \
-    --type decision --category verification_passed \
-    --description "Phase ${PHASE_NUMBER} verification passed (score: ${SCORE})" \
-    --agent pan-verifier --impact minor 2>/dev/null || true
-elif [ "${STATUS}" = "gaps_found" ]; then
-  node ~/.claude/pan-wizard-core/bin/pan-tools.cjs optimize trace log \
-    --type error --category verification_gaps \
-    --description "Phase ${PHASE_NUMBER} verification found gaps (score: ${SCORE})" \
-    --agent pan-verifier --impact major 2>/dev/null || true
-fi
+node ~/.claude/pan-wizard-core/bin/pan-tools.cjs findings record --phase "${PHASE_NUMBER}" --file "$REPORT_PATH" 2>/dev/null || true
 ```
+Recording the same report twice is a no-op, so exec-phase recording it again after this workflow returns is safe.
 </step>
 
 </process>

package/pan-zcode/README.md

@@ -50,7 +50,7 @@ before ADR-0028.
   preserves the body; plus a command → skill wrapper.
 - **M4 — bundle + install.** `bin/install-zcode.js` — assembles `agents/` + `pan-mcp.json` +
   manifest + `INSTALL-ZCODE.md` into a `--target` dir; refuses to write inside the source repo;
-  drives ZCode's own Import to finish.
+  leaves the finish to the human in ZCode's own Settings and Import, following `INSTALL-ZCODE.md`.
 - **M5 — hardening + docs.** Full test matrix + [`KNOWN-BETA-RISKS.md`](KNOWN-BETA-RISKS.md)
   (the beta-churn ledger + the M0 go/no-go questions).
 
@@ -59,11 +59,11 @@ Tests: `tests/pan-zcode-mcp.test.cjs`, `tests/pan-zcode-orchestration.test.cjs`,
 
 ## Still pending — M0 (needs a real ZCode install)
 
-Two go/no-go facts can only be settled empirically: **can a subagent call MCP tools?** and **are
+Among the go/no-go facts only a real install can settle (the M0 table in `KNOWN-BETA-RISKS.md`) are **can a subagent call MCP tools?** and **are
 local stdio MCP calls metered?** Both have folded-in fallbacks (see `KNOWN-BETA-RISKS.md`), so the
 design holds either way — but confirm them before relying on the richer paths.
 
-A third M0 checkpoint (added 2026-08): **which protocol era does the real ZCode client speak?**
+Another M0 checkpoint (added 2026-08, not yet in `KNOWN-BETA-RISKS.md`): **which protocol era does the real ZCode client speak?**
 The bridge is now dual-era (ADR-0041), so it answers both a legacy `initialize` handshake and a
 modern `server/discover` probe. Confirm on a real install which path ZCode takes and that the
 version it declares is in our supported list; if ZCode ever declares a revision newer than

package/scripts/git-hooks/pre-commit

@@ -10,7 +10,8 @@
 # Or with a symlink (Unix / Git Bash):
 #   ln -sf ../../scripts/git-hooks/pre-commit .git/hooks/pre-commit
 #
-# Bypass for an emergency (creates a paper trail in the commit log):
+# Bypass for an emergency (the hook only prints that the scan was skipped;
+# nothing is recorded in the commit):
 #   SKIP_GITLEAKS=1 git commit -m "..."
 #
 # Exit codes: