v0.3.13

修复 #35：形式化验证门禁误触发。

• 单独读取 create/maintain 形式化验证技能不再触发门禁；需要本轮后续向当前工作区的 .pi/skills/** 或 .agents/skills/** 写入或编辑。
• 工作区中未提交的验证技能不再单独触发门禁，也不会在本轮未写入时升级 read 候选。
• 保留显式技能调用，并支持本轮直接写入或编辑包含 ## Run it 的技能文件。
• 当前工作区没有目标验证产物时，只提示一次并返回 continue: false；门禁提示明确限定工作区范围。

验证：npm test 36/36、check:generate、check:fidelity（94.01%）通过；形式化验证门禁测试 85/85 通过。npm 已发布 @jiangkoumo/pi-pstack@0.3.13。

安装：

pi install npm:@jiangkoumo/pi-pstack@0.3.13

关联 PR：#39

v0.3.12

• Fix #35: require explicit formal verification activation evidence. Help text, ordinary mentions, negations, recommendations and paths printed by tools no longer activate the completion gate. Keep real skill loads, read calls, explicit commands and changed workspace verification skills working, with the latest invocation determining create/maintain.
• Resolve #34: persistent mode uses /poteto on|off|status; /poteto alone shows status. /skill:poteto-mode stays unchanged and does not toggle persistent mode. Existing stored state needs no migration.
• Keep /poteto-mode as a deprecated alias through 0.3.x and 0.4.x; remove it in 0.5.0. Each invocation warns first. Pi 1.4.0 cannot hide individual commands through its public command API, so the alias remains visible with a [已弃用] description.

Both fixes include regression coverage and real Pi TUI validation. Formal verification trigger checks used an isolated configuration and a local SSE fixture; completion-list and alias checks used the production extension in a real terminal.