🗑️ remove(progress): drop workflow state tracking

Use plan-status as the only machine state source for plan queueing, claiming, and finishing.

Route record-plan through queue insertion and update templates/prompts to match the single-state model.

BREAKING CHANGE: playbook.py -record-spec and main_loop.py record are removed.

templates/memory-bank/progress.template.md

@@ -6,8 +6,7 @@
 - 上半部分是短期状态快照，不是 changelog
 - `Recent Changes` 只保留最近 3-5 条对恢复上下文有价值的变化
 - 更新摘要时整理/替换旧摘要，不做无限追加
-- 中间的 workflow-state 块记录当前阶段、spec、plan 与执行约束
-- 下半部分的 plan-status 块由 main_loop.py 维护，是唯一权威状态源
+- 下半部分的 plan-status 块由 main_loop.py 维护，是唯一机器状态源
 -->
 
 ## Current Focus
@@ -31,26 +30,14 @@
 以下示例仅用于说明结构，真实状态由 `main_loop.py` 维护：
 
 ```text
-## Workflow State
-<!-- workflow-state:start -->
-phase: planning
-spec: docs/superpowers/specs/2026-05-18-demo-design.md
-plan: docs/superpowers/plans/2026-05-18-demo.md
-executor: executing-plans
-constraints: karpathy-guidelines,.agents,AGENT_RULES
-<!-- workflow-state:end -->
-
 ## Plan Status
 <!-- plan-status:start -->
 - [ ] `2026-05-18-demo.md` pending
+- [ ] `2026-05-19-next.md` in-progress: claimed_by: codex; claimed_at: 2026-05-19T08:00:00Z
+- [x] `2026-05-20-done.md` done: verified: python -m unittest
 <!-- plan-status:end -->
 ```
 
-## Workflow State
-
-<!-- workflow-state:start -->
-<!-- workflow-state:end -->
-
 ## Plan Status
 
 <!-- plan-status:start -->