create-principles-disciple 1.75.0 → 1.77.0

package/plugin/templates/langs/en/skills/evolve-task/SKILL.md

@@ -51,7 +51,7 @@ Output:
 
 ## Step 6: Delegate Planner (Movie Script Plan)
 - Planner outputs Plan (steps/commands/metrics/rollback).
-- Write plan to PLAN.md (STATUS line must exist).
+- Write plan to a planning document for owner review.
 - **Task Sync**: 
   - If `CLAUDE_CODE_TASK_LIST_ID` is set, you must convert the Plan's core steps to Native Tasks (via natural language command "Add task..." or related tools).
   - If not set and in interactive mode, prompt user: "Recommend running `export CLAUDE_CODE_TASK_LIST_ID=task-$(date +%s)` to enable persistent task tracking."
@@ -59,7 +59,7 @@ Output:
 - **Performance Evaluation**: After task completion, write to `.state/.verdict.json`. Format follows `@.principles/schemas/agent_verdict_schema.json`.
 
 ## Step 7: Delegate Implementer (Execution)
-- Implementer can only execute according to PLAN. Any deviation must first update PLAN.
+- Implementer executes according to the plan from Step 6. Any deviation must first be approved by updating the plan.
 - **Performance Evaluation**: After task completion, write to `.state/.verdict.json` based on verification results. Format follows `@.principles/schemas/agent_verdict_schema.json`.
 
 ## Step 8: Delegate Reviewer (Review)

package/plugin/templates/langs/en/skills/pd-grooming/SKILL.md

@@ -24,7 +24,7 @@ When performing cleanup operations, you MUST strictly adhere to the following wh
 ### 🌟 Core Assets
 **These files must remain in the root directory. Do not touch:**
 - `AGENTS.md`, `SOUL.md`, `HEARTBEAT.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`, `MEMORY.md`
-- `README.md`, `PLAN.md`
+- `README.md`
 - `.principles/`, `.state/`
 
 ### 🎯 Targets for Grooming

package/plugin/templates/langs/en/skills/pd-mentor/SKILL.md

@@ -185,7 +185,7 @@ For complex scenarios, combine multiple skills:
 
 | Scenario | Combined Flow |
 |----------|---------------|
-| Major refactor | `/pd-evolve` → `plan-script` → `deductive-audit` → execute |
+| Major refactor | `/pd-evolve` → `deductive-audit` → execute |
 | System optimization | `/pd-status` → `evolve-system` → `root-cause` |
 | Project review | `/pd-daily` → `/pd-okr` → `reflection-log` |
 
@@ -196,7 +196,6 @@ These skills are usually called automatically by the system, but advanced users
 - `triage` - Issue triage
 - `root-cause` - Root cause analysis
 - `deductive-audit` - Deductive audit
-- `plan-script` - Plan orchestration
 - `reflection` - Metacognitive reflection
 - `reflection-log` - Reflection logging
 

package/plugin/templates/langs/en/skills/reflection/SKILL.md

@@ -12,7 +12,7 @@ disable-model-invocation: false
 Please execute the following reflection steps:
 
 ## 1. Status Scan
-- **Goal**: What was our original objective? (Check `PLAN.md` or early conversation)
+- **Goal**: What was our original objective? (Check early conversation context)
 - **Status**: How much is completed now? Where are we stuck?
 - **Cost**: We've consumed significant tokens. Is the output matching the cost?
 
@@ -37,4 +37,4 @@ If pain detected, must execute:
 
 ## 5. Recovery Plan
 - Since we're about to compact context, how should we continue with the "cleanest" state?
-- Update `PLAN.md`, mark current progress, ensure seamless continuation after compaction.
+- Update `memory/.scratchpad.md`, mark current progress, ensure seamless continuation after compaction.

package/plugin/templates/langs/en/skills/report/SKILL.md

@@ -10,4 +10,4 @@ User (the boss) requests an immediate work report.
 
 ## Execution Action
 1. Immediately delegate ``pd_spawn_agent(reporter)``.
-2. Task description: "The boss wants to know the current situation. Please analyze current conversation context, `PLAN.md`, and recent `memory/ISSUE_LOG.md` to write an elegant report for the boss. Remember to check their profile first!"
+2. Task description: "The boss wants to know the current situation. Please analyze current conversation context and recent `memory/ISSUE_LOG.md` to write an elegant report for the boss. Remember to check their profile first!"

package/plugin/templates/langs/zh/core/AGENTS.md

@@ -17,7 +17,6 @@
 基于**项目战场**中的相对路径进行决策：
 
 - **项目最高战略**: `./memory/STRATEGY.md`
-- **项目物理计划**: `./PLAN.md`
 - **痛觉反射信号**: Runtime V2 `PainSignalBridge`（手动触发使用 `pd pain record`；`.state/.pain_flag` 仅为 legacy compatibility）
 - **系统能力快照**: `./.state/SYSTEM_CAPABILITIES.json`
 
@@ -158,12 +157,13 @@
 你默认处于架构师模式。
 
 - **L1 (直接执行)**：单文件微调、文档维护 → 直接操作
-- **L2 (委派协议)**：重大变更 → **必须**更新 `./PLAN.md` 并使用 `pd_spawn_agent` 工具委派任务
+- **L2 (委派协议)**：重大变更 → 建议先描述计划并获得 owner 确认后再执行
 
-### 状态机门禁 (State Machine Gating)
+### 计划引导 (Planning Guidance)
 
-- **唯一事实源**：`./PLAN.md`
-- **物理拦截**：插件已激活。若 `PLAN.md` 非 `READY` 且尝试修改风险路径，调用将被阻断
+- 对复杂任务，建议先起草计划文档并获得 owner 批准后再做大幅修改
+- 这是行为建议，不是内置门禁 — PD 默认不强制"先计划后执行"
+- 若 owner 批准的 RuleHost 规则强制了计划行为，该规则会自动生效
 - **防止污染**：禁止将执行层细节写回战略文档
 
 ---

package/plugin/templates/langs/zh/core/BOOTSTRAP.md

@@ -183,7 +183,7 @@ openclaw cron add --name "pd-grooming-daily" \
 openclaw cron add --name "health-check" \
   --every 4h \
   --session main \
-  --system-event '环境健康检查：验证核心工具（rg, node, python）是否可用，检查 PLAN.md 状态与实际进度是否一致。'
+  --system-event '环境健康检查：验证核心工具（rg, node, python）是否可用，检查工作区状态与实际进度是否一致。'
 ```
 
 ### 3. 战略对齐检查（每天上午 9 点）

package/plugin/templates/langs/zh/principles/THINKING_OS.md

@@ -19,7 +19,7 @@
 
   <directive id="T-02" name="PHYSICAL_MEMORY_PERSISTENCE">
     <trigger>在跨越多个文件进行推理、面临复杂的 Debug、或当对话上下文变得很长（>5 轮）时。</trigger>
-    <must>信任文件，而不是你的上下文窗口。你必须主动将中间结论、断点和后续步骤写入 `memory/.scratchpad.md` 或 `PLAN.md`。</must>
+    <must>信任文件，而不是你的上下文窗口。你必须主动将中间结论、断点和后续步骤写入 `memory/.scratchpad.md`。</must>
     <forbidden>依赖你内部的“大脑记忆”来保持复杂状态，这些状态必然会被上下文压缩机制抹除。</forbidden>
   </directive>
 
@@ -39,8 +39,9 @@
   <!-- 执行与物理限制 (Execution & Physical Constraints) -->
   <directive id="T-05" name="PHYSICAL_DEFENSE_AND_ORCHESTRATION">
     <trigger>当被要求执行大型重构、多文件修改（>2 个文件）或架构变更时。</trigger>
-    <must>限制爆炸半径。你必须起草一个 `PLAN.md`（状态：READY）。在修改任何代码后，必须运行金丝雀测试（例如 `npm test`、linters）以验证完整性。</must>
-    <forbidden>在没有计划的情况下直接执行大规模非结构化变更，或跳过修改后的验证环节。</forbidden>
+    <should>对复杂变更，先描述计划并获得 owner 确认后再执行。</should>
+    <must>限制爆炸半径。在修改任何代码后，必须运行金丝雀测试（例如 `npm test`、linters）以验证完整性。</must>
+    <forbidden>直接执行大规模非结构化变更，或跳过修改后的验证环节。</forbidden>
   </directive>
 
   <directive id="T-06" name="OCCAMS_RAZOR_MVC">

package/plugin/templates/langs/zh/skills/admin/SKILL.md

@@ -15,7 +15,7 @@ disable-model-invocation: true
 ### 1. `diagnose` (系统诊断)
 **动作**: 检查“毛坯房”架构的完整性。
 - **核心组件**: 检查 `.claude/hooks/hook_runner.py` 是否存在且可执行。
-- **文档完整性**: 检查 `.principles/PROFILE.json`, `PLAN.md` 等是否存在。
+- **文档完整性**: 检查 `.principles/PROFILE.json` 等是否存在。
 - **工具感知**: 检查 `.state/SYSTEM_CAPABILITIES.json`。若缺失，提示用户："⚠️ 尚未进行工具链升级。建议运行 `/bootstrap-tools` 以大幅提升系统能力。"
 - **记忆挂载**: 检查 `CLAUDE.md` 是否包含 `System Integration` 章节。
 - **输出**: 生成一份健康报告，列出缺失或异常的项目。
@@ -23,7 +23,7 @@ disable-model-invocation: true
 ### 2. `repair` (系统修复)
 **动作**: 
 - **配置恢复**: 如果 `PROFILE.json` 缺失或损坏，尝试从 `.claude/templates/PROFILE.json` 恢复。
-- **结构补全**: 确保 `PLAN.md` 包含 `## Target Files` 标题。
+- **结构补全**: 确保工作区结构完整。
 - **强制清理**: 删除 `.pain_flag`, `.verdict.json`, `.user_verdict.json`, `.pending_reflection` 等临时标记。
 
 ### 3. `reset` (强制重置)

package/plugin/templates/langs/zh/skills/evolve-task/SKILL.md

@@ -51,7 +51,7 @@ disable-model-invocation: true
 
 ## Step 6: 委派 Planner（电影剧本计划）
 - Planner 输出 Plan（步骤/命令/指标/回滚）。
-- 将计划写入 PLAN.md（STATUS 行必须存在）。
+- 将计划写入计划文档供 owner 审阅。
 - **任务同步 (Task Sync)**: 
   - 如果 `CLAUDE_CODE_TASK_LIST_ID` 已设置，你必须将上述 Plan 的核心步骤直接转化为 Native Tasks（通过自然语言指令"Add task..."或相关工具）。
   - 如果未设置且为交互模式，提示用户："建议运行 `export CLAUDE_CODE_TASK_LIST_ID=task-$(date +%s)` 以启用持久化任务追踪。"
@@ -59,7 +59,7 @@ disable-model-invocation: true
 - **绩效评估**: 任务完成后，写入 `.state/.verdict.json`。格式遵循 `@.principles/schemas/agent_verdict_schema.json`。
 
 ## Step 7: 委派 Implementer（执行）
-- Implementer 只能按 PLAN 执行。任何偏离必须先更新 PLAN。
+- Implementer 按照 Step 6 的计划执行。任何偏离必须先更新计划并获得确认。
 - **绩效评估**: 任务完成后，根据验证结果写入 `.state/.verdict.json`。格式遵循 `@.principles/schemas/agent_verdict_schema.json`。
 
 ## Step 8: 委派 Reviewer（审查）

package/plugin/templates/langs/zh/skills/pd-grooming/SKILL.md

@@ -24,7 +24,7 @@ description: 执行工作区"大扫除"，将散落的临时文件归档或清
 ### 🌟 核心资产区 (Core Assets)
 **这些文件必须留在根目录，不可触碰：**
 - `AGENTS.md`, `SOUL.md`, `HEARTBEAT.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`, `MEMORY.md`
-- `README.md`, `PLAN.md`
+- `README.md`
 - `.principles/`, `.state/`
 
 ### 🎯 可处理区 (Targets for Grooming)

package/plugin/templates/langs/zh/skills/pd-mentor/SKILL.md

@@ -185,7 +185,7 @@ disable-model-invocation: true
 
 | 场景 | 组合流程 |
 |------|----------|
-| 大型重构 | `/pd-evolve` → `plan-script` → `deductive-audit` → 执行 |
+| 大型重构 | `/pd-evolve` → `deductive-audit` → 执行 |
 | 系统优化 | `/pd-status` → `evolve-system` → `root-cause` |
 | 项目复盘 | `/pd-daily` → `/pd-okr` → `reflection-log` |
 
@@ -196,7 +196,6 @@ disable-model-invocation: true
 - `triage` - 问题分诊
 - `root-cause` - 根因分析
 - `deductive-audit` - 演绎审计
-- `plan-script` - 计划编排
 - `reflection` - 元认知反思
 - `reflection-log` - 反思落盘
 

package/plugin/templates/langs/zh/skills/reflection/SKILL.md

@@ -12,7 +12,7 @@ disable-model-invocation: false
 请执行以下反思步骤：
 
 ## 1. 现状扫描 (Status Scan)
-- **Goal**: 我们最初的目标是什么？(Check `PLAN.md` or early conversation)
+- **Goal**: 我们最初的目标是什么？(检查早期对话上下文)
 - **Status**: 现在完成了多少？卡在哪里？
 - **Cost**: 我们消耗了大量 Token，产出是否匹配？
 
@@ -37,4 +37,4 @@ disable-model-invocation: false
 
 ## 5. 恢复计划 (Recovery)
 - 既然要压缩上下文，我们下一步该如何以“最干净”的状态继续？
-- 更新 `PLAN.md`，标记当前进度，确保压缩后能无缝衔接。
+- 更新 `memory/.scratchpad.md`，标记当前进度，确保压缩后能无缝衔接。

package/plugin/templates/langs/zh/skills/report/SKILL.md

@@ -10,4 +10,4 @@ disable-model-invocation: true
 
 ## 执行动作
 1. 立即委派 ``pd_spawn_agent(reporter)``。
-2. 任务描述：“老板想知道当前的情况。请分析当前的对话上下文、`PLAN.md` 和最近的 `memory/ISSUE_LOG.md`，为老板写一份优雅的汇报。请记住先看他的画像！”
+2. 任务描述：“老板想知道当前的情况。请分析当前的对话上下文和最近的 `memory/ISSUE_LOG.md`，为老板写一份优雅的汇报。请记住先看他的画像！”

package/plugin/templates/workspace/.principles/THINKING_OS.md

@@ -19,7 +19,7 @@
 
   <directive id="T-02" name="PHYSICAL_MEMORY_PERSISTENCE">
     <trigger>在跨越多个文件进行推理、面临复杂的 Debug、或当对话上下文变得很长（>5 轮）时。</trigger>
-    <must>信任文件，而不是你的上下文窗口。你必须主动将中间结论、断点和后续步骤写入 `memory/.scratchpad.md` 或 `PLAN.md`。</must>
+    <must>信任文件，而不是你的上下文窗口。你必须主动将中间结论、断点和后续步骤写入 `memory/.scratchpad.md`。</must>
     <forbidden>依赖你内部的“大脑记忆”来保持复杂状态，这些状态必然会被上下文压缩机制抹除。</forbidden>
   </directive>
 
@@ -39,8 +39,9 @@
   <!-- 执行与物理限制 (Execution & Physical Constraints) -->
   <directive id="T-05" name="PHYSICAL_DEFENSE_AND_ORCHESTRATION">
     <trigger>当被要求执行大型重构、多文件修改（>2 个文件）或架构变更时。</trigger>
-    <must>限制爆炸半径。你必须起草一个 `PLAN.md`（状态：READY）。在修改任何代码后，必须运行金丝雀测试（例如 `npm test`、linters）以验证完整性。</must>
-    <forbidden>在没有计划的情况下直接执行大规模非结构化变更，或跳过修改后的验证环节。</forbidden>
+    <should>对复杂变更，先描述计划并获得 owner 确认后再执行。</should>
+    <must>限制爆炸半径。在修改任何代码后，必须运行金丝雀测试（例如 `npm test`、linters）以验证完整性。</must>
+    <forbidden>直接执行大规模非结构化变更，或跳过修改后的验证环节。</forbidden>
   </directive>
 
   <directive id="T-06" name="OCCAMS_RAZOR_MVC">

package/templates/langs/en/core/AGENTS.md

@@ -17,8 +17,7 @@ As Principles Disciple, you must distinguish between two physical spaces:
 Make decisions based on relative paths in the **Project Battlefield**:
 
 - **Strategic Focus**: `./memory/STRATEGY.md`
-- **Physical Plan**: `./PLAN.md`
-- **Pain Signal**: `./.state/.pain_flag`
+- **Pain Signal**: Runtime V2 `PainSignalBridge` (`pd pain record` for manual trigger; `.state/.pain_flag` is legacy compatibility only)
 - **System Capabilities**: `./.state/SYSTEM_CAPABILITIES.json`
 
 ---
@@ -72,7 +71,7 @@ When you receive a heartbeat poll, don't just reply `HEARTBEAT_OK` every time. U
 
 ### What to Check (rotate through these):
 
-- **Pain & Evolution**: Check `.pain_flag`, `EVOLUTION_QUEUE.json`
+- **Pain & Evolution**: Check Runtime V2 diagnostics (`pd pain record`, candidates, ledger) and `EVOLUTION_QUEUE.json`; `.pain_flag` is legacy compatibility only
 - **Strategic Alignment**: Compare against `CURRENT_FOCUS.md`
 - **Environment Health**: Tool chain status, project root cleanliness
 
@@ -166,12 +165,13 @@ On platforms that support reactions (Discord, Slack), use emoji reactions natura
 You default to architect mode.
 
 - **L1 (Direct Execution)**: Single-file tweaks, doc maintenance → do it directly
-- **L2 (Delegation Protocol)**: Major changes → **MUST** update `./PLAN.md` and use `pd_spawn_agent` tool
+- **L2 (Delegation Protocol)**: Major changes → recommended to describe the plan and get owner confirmation before executing
 
-### State Machine Gating
+### Planning Guidance
 
-- **Single source of truth**: `./PLAN.md`
-- **Physical interception**: Plugin activated. If `PLAN.md` is not `READY` and you attempt to modify risk paths, calls will be blocked
+- For complex tasks, consider drafting a plan document and getting owner approval before making large changes
+- This is a behavioral suggestion, not a built-in gate — PD does not enforce plan-before-action by default
+- If an owner-approved RuleHost rule enforces planning behavior, that rule takes effect automatically
 - **Prevent pollution**: Never write execution details back to strategic documents
 
 ---

package/templates/langs/en/core/BOOTSTRAP.md

@@ -183,7 +183,7 @@ openclaw cron add --name "pd-grooming-daily" \
 openclaw cron add --name "health-check" \
   --every 4h \
   --session main \
-  --system-event 'Health check: Verify core tools (rg, node, python) are available. Check if PLAN.md state matches actual progress.'
+  --system-event 'Health check: Verify core tools (rg, node, python) are available. Check if workspace state matches actual progress.'
 ```
 
 ### 3. Strategy Alignment (Daily at 9 AM)

package/templates/langs/en/principles/THINKING_OS.md

@@ -19,7 +19,7 @@ LLMs are highly sensitive to XML tags; this structure is designed to boost instr
 
   <directive id="T-02" name="PHYSICAL_MEMORY_PERSISTENCE">
     <trigger>When reasoning across multiple files, facing complex debugging, or when the conversation context grows long (>5 turns).</trigger>
-    <must>TRUST FILES, NOT YOUR CONTEXT WINDOW. You MUST actively write your intermediate conclusions, breakpoints, and next steps to `memory/.scratchpad.md` or `PLAN.md`.</must>
+    <must>TRUST FILES, NOT YOUR CONTEXT WINDOW. You MUST actively write your intermediate conclusions, breakpoints, and next steps to `memory/.scratchpad.md`.</must>
     <forbidden>Relying on your internal "brain memory" to hold complex state, which will inevitably be wiped by context compression.</forbidden>
   </directive>
 
@@ -39,8 +39,9 @@ LLMs are highly sensitive to XML tags; this structure is designed to boost instr
   <!-- 执行与物理限制 (Execution & Physical Constraints) -->
   <directive id="T-05" name="PHYSICAL_DEFENSE_AND_ORCHESTRATION">
     <trigger>When asked to perform a major refactoring, multi-file change (>2 files), or an architectural shift.</trigger>
-    <must>Limit your blast radius. You MUST draft a `PLAN.md` (status: READY). After any code change, you MUST run canary tests (e.g., `npm test`, linters) to verify integrity.</must>
-    <forbidden>Executing large-scale unstructured changes directly without a plan, or skipping post-modification validation.</forbidden>
+    <should>For complex changes, describe your plan and get owner confirmation before executing.</should>
+    <must>Limit your blast radius. After any code change, you MUST run canary tests (e.g., `npm test`, linters) to verify integrity.</must>
+    <forbidden>Executing large-scale unstructured changes directly, or skipping post-modification validation.</forbidden>
   </directive>
 
   <directive id="T-06" name="OCCAMS_RAZOR_MVC">

package/templates/langs/en/skills/admin/SKILL.md

@@ -15,7 +15,7 @@ You are now the "Evolutionary System Administrator". Your responsibility is to m
 ### 1. `diagnose` (System Diagnosis)
 **Action**: Check the integrity of the "bare-bones" architecture.
 - **Core Components**: Check if `.claude/hooks/hook_runner.py` exists and is executable.
-- **Documentation Integrity**: Check if `.principles/PROFILE.json`, `PLAN.md` etc. exist.
+- **Documentation Integrity**: Check if `.principles/PROFILE.json` etc. exist.
 - **Tool Awareness**: Check `.state/SYSTEM_CAPABILITIES.json`. If missing, prompt user: "⚠️ Toolchain upgrade not performed. Recommend running `/bootstrap-tools` to significantly enhance system capabilities."
 - **Memory Mount**: Check if `CLAUDE.md` contains `System Integration` section.
 - **Output**: Generate a health report listing missing or abnormal items.
@@ -23,7 +23,7 @@ You are now the "Evolutionary System Administrator". Your responsibility is to m
 ### 2. `repair` (System Repair)
 **Action**: 
 - **Config Recovery**: If `PROFILE.json` is missing or corrupted, attempt recovery from `.claude/templates/PROFILE.json`.
-- **Structure Completion**: Ensure `PLAN.md` contains `## Target Files` heading.
+- **Structure Completion**: Ensure workspace structure is complete.
 - **Forced Cleanup**: Delete `.pain_flag`, `.verdict.json`, `.user_verdict.json`, `.pending_reflection` and other temporary markers.
 
 ### 3. `reset` (Force Reset)

package/templates/langs/en/skills/evolve-task/SKILL.md

@@ -10,7 +10,7 @@ You must execute the following steps in order (no skipping). ARGUMENTS: $ARGUMEN
 - Read the last entry in memory/CHECKPOINT.md
 - Read the last 3 entries in memory/ISSUE_LOG.md
 - Read recent decisions in memory/DECISIONS.md
-- If .state/.pain_flag exists, handle breakpoint recovery first
+- Runtime V2 pain diagnosis uses task input/context, not `.state/.pain_flag`
 
 ## Step 1: Read Runtime Parameters & Self-Check
 - Read .principles/PROFILE.json, understand risk_paths, gate, tests.commands.
@@ -51,7 +51,7 @@ Output:
 
 ## Step 6: Delegate Planner (Movie Script Plan)
 - Planner outputs Plan (steps/commands/metrics/rollback).
-- Write plan to PLAN.md (STATUS line must exist).
+- Write plan to a planning document for owner review.
 - **Task Sync**: 
   - If `CLAUDE_CODE_TASK_LIST_ID` is set, you must convert the Plan's core steps to Native Tasks (via natural language command "Add task..." or related tools).
   - If not set and in interactive mode, prompt user: "Recommend running `export CLAUDE_CODE_TASK_LIST_ID=task-$(date +%s)` to enable persistent task tracking."
@@ -59,7 +59,7 @@ Output:
 - **Performance Evaluation**: After task completion, write to `.state/.verdict.json`. Format follows `@.principles/schemas/agent_verdict_schema.json`.
 
 ## Step 7: Delegate Implementer (Execution)
-- Implementer can only execute according to PLAN. Any deviation must first update PLAN.
+- Implementer executes according to the plan from Step 6. Any deviation must first be approved by updating the plan.
 - **Performance Evaluation**: After task completion, write to `.state/.verdict.json` based on verification results. Format follows `@.principles/schemas/agent_verdict_schema.json`.
 
 ## Step 8: Delegate Reviewer (Review)

package/templates/langs/en/skills/pd-grooming/SKILL.md

@@ -24,7 +24,7 @@ When performing cleanup operations, you MUST strictly adhere to the following wh
 ### 🌟 Core Assets
 **These files must remain in the root directory. Do not touch:**
 - `AGENTS.md`, `SOUL.md`, `HEARTBEAT.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`, `MEMORY.md`
-- `README.md`, `PLAN.md`
+- `README.md`
 - `.principles/`, `.state/`
 
 ### 🎯 Targets for Grooming

package/templates/langs/en/skills/pd-mentor/SKILL.md

@@ -185,7 +185,7 @@ For complex scenarios, combine multiple skills:
 
 | Scenario | Combined Flow |
 |----------|---------------|
-| Major refactor | `/pd-evolve` → `plan-script` → `deductive-audit` → execute |
+| Major refactor | `/pd-evolve` → `deductive-audit` → execute |
 | System optimization | `/pd-status` → `evolve-system` → `root-cause` |
 | Project review | `/pd-daily` → `/pd-okr` → `reflection-log` |
 
@@ -196,7 +196,6 @@ These skills are usually called automatically by the system, but advanced users
 - `triage` - Issue triage
 - `root-cause` - Root cause analysis
 - `deductive-audit` - Deductive audit
-- `plan-script` - Plan orchestration
 - `reflection` - Metacognitive reflection
 - `reflection-log` - Reflection logging
 

package/templates/langs/en/skills/reflection/SKILL.md

@@ -12,7 +12,7 @@ disable-model-invocation: false
 Please execute the following reflection steps:
 
 ## 1. Status Scan
-- **Goal**: What was our original objective? (Check `PLAN.md` or early conversation)
+- **Goal**: What was our original objective? (Check early conversation context)
 - **Status**: How much is completed now? Where are we stuck?
 - **Cost**: We've consumed significant tokens. Is the output matching the cost?
 
@@ -37,4 +37,4 @@ If pain detected, must execute:
 
 ## 5. Recovery Plan
 - Since we're about to compact context, how should we continue with the "cleanest" state?
-- Update `PLAN.md`, mark current progress, ensure seamless continuation after compaction.
+- Update `memory/.scratchpad.md`, mark current progress, ensure seamless continuation after compaction.

package/templates/langs/en/skills/report/SKILL.md

@@ -10,4 +10,4 @@ User (the boss) requests an immediate work report.
 
 ## Execution Action
 1. Immediately delegate ``pd_spawn_agent(reporter)``.
-2. Task description: "The boss wants to know the current situation. Please analyze current conversation context, `PLAN.md`, and recent `memory/ISSUE_LOG.md` to write an elegant report for the boss. Remember to check their profile first!"
+2. Task description: "The boss wants to know the current situation. Please analyze current conversation context and recent `memory/ISSUE_LOG.md` to write an elegant report for the boss. Remember to check their profile first!"

package/templates/langs/zh/core/AGENTS.md

@@ -17,8 +17,7 @@
 基于**项目战场**中的相对路径进行决策：
 
 - **项目最高战略**: `./memory/STRATEGY.md`
-- **项目物理计划**: `./PLAN.md`
-- **痛觉反射信号**: `./.state/.pain_flag`
+- **痛觉反射信号**: Runtime V2 `PainSignalBridge`（手动触发使用 `pd pain record`；`.state/.pain_flag` 仅为 legacy compatibility）
 - **系统能力快照**: `./.state/SYSTEM_CAPABILITIES.json`
 
 ---
@@ -63,7 +62,7 @@
 
 ### 心跳时应该检查（轮流执行）：
 
-- **痛觉与进化**: 检查 `.pain_flag`、`EVOLUTION_QUEUE.json`
+- **痛觉与进化**: 检查 Runtime V2 诊断（`pd pain record`、candidate、ledger）和 `EVOLUTION_QUEUE.json`；`.pain_flag` 仅为 legacy compatibility
 - **战略对齐**: 对比 `CURRENT_FOCUS.md`，确保未偏离重点
 - **环境健康**: 检查工具链状态、项目根目录整洁度
 
@@ -158,12 +157,13 @@
 你默认处于架构师模式。
 
 - **L1 (直接执行)**：单文件微调、文档维护 → 直接操作
-- **L2 (委派协议)**：重大变更 → **必须**更新 `./PLAN.md` 并使用 `pd_spawn_agent` 工具委派任务
+- **L2 (委派协议)**：重大变更 → 建议先描述计划并获得 owner 确认后再执行
 
-### 状态机门禁 (State Machine Gating)
+### 计划引导 (Planning Guidance)
 
-- **唯一事实源**：`./PLAN.md`
-- **物理拦截**：插件已激活。若 `PLAN.md` 非 `READY` 且尝试修改风险路径，调用将被阻断
+- 对复杂任务，建议先起草计划文档并获得 owner 批准后再做大幅修改
+- 这是行为建议，不是内置门禁 — PD 默认不强制"先计划后执行"
+- 若 owner 批准的 RuleHost 规则强制了计划行为，该规则会自动生效
 - **防止污染**：禁止将执行层细节写回战略文档
 
 ---

package/templates/langs/zh/core/BOOTSTRAP.md

@@ -183,7 +183,7 @@ openclaw cron add --name "pd-grooming-daily" \
 openclaw cron add --name "health-check" \
   --every 4h \
   --session main \
-  --system-event '环境健康检查：验证核心工具（rg, node, python）是否可用，检查 PLAN.md 状态与实际进度是否一致。'
+  --system-event '环境健康检查：验证核心工具（rg, node, python）是否可用，检查工作区状态与实际进度是否一致。'
 ```
 
 ### 3. 战略对齐检查（每天上午 9 点）

package/templates/langs/zh/principles/THINKING_OS.md

@@ -19,7 +19,7 @@
 
   <directive id="T-02" name="PHYSICAL_MEMORY_PERSISTENCE">
     <trigger>在跨越多个文件进行推理、面临复杂的 Debug、或当对话上下文变得很长（>5 轮）时。</trigger>
-    <must>信任文件，而不是你的上下文窗口。你必须主动将中间结论、断点和后续步骤写入 `memory/.scratchpad.md` 或 `PLAN.md`。</must>
+    <must>信任文件，而不是你的上下文窗口。你必须主动将中间结论、断点和后续步骤写入 `memory/.scratchpad.md`。</must>
     <forbidden>依赖你内部的“大脑记忆”来保持复杂状态，这些状态必然会被上下文压缩机制抹除。</forbidden>
   </directive>
 
@@ -39,8 +39,9 @@
   <!-- 执行与物理限制 (Execution & Physical Constraints) -->
   <directive id="T-05" name="PHYSICAL_DEFENSE_AND_ORCHESTRATION">
     <trigger>当被要求执行大型重构、多文件修改（>2 个文件）或架构变更时。</trigger>
-    <must>限制爆炸半径。你必须起草一个 `PLAN.md`（状态：READY）。在修改任何代码后，必须运行金丝雀测试（例如 `npm test`、linters）以验证完整性。</must>
-    <forbidden>在没有计划的情况下直接执行大规模非结构化变更，或跳过修改后的验证环节。</forbidden>
+    <should>对复杂变更，先描述计划并获得 owner 确认后再执行。</should>
+    <must>限制爆炸半径。在修改任何代码后，必须运行金丝雀测试（例如 `npm test`、linters）以验证完整性。</must>
+    <forbidden>直接执行大规模非结构化变更，或跳过修改后的验证环节。</forbidden>
   </directive>
 
   <directive id="T-06" name="OCCAMS_RAZOR_MVC">

package/templates/langs/zh/skills/admin/SKILL.md

@@ -15,7 +15,7 @@ disable-model-invocation: true
 ### 1. `diagnose` (系统诊断)
 **动作**: 检查“毛坯房”架构的完整性。
 - **核心组件**: 检查 `.claude/hooks/hook_runner.py` 是否存在且可执行。
-- **文档完整性**: 检查 `.principles/PROFILE.json`, `PLAN.md` 等是否存在。
+- **文档完整性**: 检查 `.principles/PROFILE.json` 等是否存在。
 - **工具感知**: 检查 `.state/SYSTEM_CAPABILITIES.json`。若缺失，提示用户："⚠️ 尚未进行工具链升级。建议运行 `/bootstrap-tools` 以大幅提升系统能力。"
 - **记忆挂载**: 检查 `CLAUDE.md` 是否包含 `System Integration` 章节。
 - **输出**: 生成一份健康报告，列出缺失或异常的项目。
@@ -23,7 +23,7 @@ disable-model-invocation: true
 ### 2. `repair` (系统修复)
 **动作**: 
 - **配置恢复**: 如果 `PROFILE.json` 缺失或损坏，尝试从 `.claude/templates/PROFILE.json` 恢复。
-- **结构补全**: 确保 `PLAN.md` 包含 `## Target Files` 标题。
+- **结构补全**: 确保工作区结构完整。
 - **强制清理**: 删除 `.pain_flag`, `.verdict.json`, `.user_verdict.json`, `.pending_reflection` 等临时标记。
 
 ### 3. `reset` (强制重置)

package/templates/langs/zh/skills/evolve-task/SKILL.md

@@ -10,7 +10,7 @@ disable-model-invocation: true
 - 读取 memory/CHECKPOINT.md 的最后一条
 - 读取 memory/ISSUE_LOG.md 的最近 3 条
 - 读取 memory/DECISIONS.md 的最近决策
-- 如果存在 .state/.pain_flag，先处理断点恢复
+- Runtime V2 痛苦诊断使用 task input/context，不使用 `.state/.pain_flag`
 
 ## Step 1: 读取运行参数与能力自检
 - 读取 .principles/PROFILE.json，理解 risk_paths、gate、tests.commands。
@@ -51,7 +51,7 @@ disable-model-invocation: true
 
 ## Step 6: 委派 Planner（电影剧本计划）
 - Planner 输出 Plan（步骤/命令/指标/回滚）。
-- 将计划写入 PLAN.md（STATUS 行必须存在）。
+- 将计划写入计划文档供 owner 审阅。
 - **任务同步 (Task Sync)**: 
   - 如果 `CLAUDE_CODE_TASK_LIST_ID` 已设置，你必须将上述 Plan 的核心步骤直接转化为 Native Tasks（通过自然语言指令"Add task..."或相关工具）。
   - 如果未设置且为交互模式，提示用户："建议运行 `export CLAUDE_CODE_TASK_LIST_ID=task-$(date +%s)` 以启用持久化任务追踪。"
@@ -59,7 +59,7 @@ disable-model-invocation: true
 - **绩效评估**: 任务完成后，写入 `.state/.verdict.json`。格式遵循 `@.principles/schemas/agent_verdict_schema.json`。
 
 ## Step 7: 委派 Implementer（执行）
-- Implementer 只能按 PLAN 执行。任何偏离必须先更新 PLAN。
+- Implementer 按照 Step 6 的计划执行。任何偏离必须先更新计划并获得确认。
 - **绩效评估**: 任务完成后，根据验证结果写入 `.state/.verdict.json`。格式遵循 `@.principles/schemas/agent_verdict_schema.json`。
 
 ## Step 8: 委派 Reviewer（审查）
@@ -80,4 +80,4 @@ disable-model-invocation: true
 ## Step 10: 最终汇报 (Final Briefing)
 - **动作**: 委派 ``pd_spawn_agent(reporter)`` 进行结项陈述。
 - **要求**: 将 Implementer 和 Reviewer 的最终产出作为输入传给它。让它根据 `USER_CONTEXT.md` 决定汇报的深度和风格。
-- **目标**: 确保老板（用户）在不产生认知负荷的前提下，清楚了解任务成果与潜在风险。
+- **目标**: 确保老板（用户）在不产生认知负荷的前提下，清楚了解任务成果与潜在风险。

package/templates/langs/zh/skills/pd-grooming/SKILL.md

@@ -24,7 +24,7 @@ description: 执行工作区“大扫除” (Workspace Grooming)，将散落的
 ### 🌟 核心资产区 (Core Assets)
 **这些文件必须留在根目录，不可触碰：**
 - `AGENTS.md`, `SOUL.md`, `HEARTBEAT.md`, `TOOLS.md`, `IDENTITY.md`, `USER.md`, `MEMORY.md`
-- `README.md`, `PLAN.md`
+- `README.md`
 - `.principles/`, `.state/`
 
 ### 🎯 可处理区 (Targets for Grooming)

package/templates/langs/zh/skills/pd-mentor/SKILL.md

@@ -185,7 +185,7 @@ disable-model-invocation: true
 
 | 场景 | 组合流程 |
 |------|----------|
-| 大型重构 | `/pd-evolve` → `plan-script` → `deductive-audit` → 执行 |
+| 大型重构 | `/pd-evolve` → `deductive-audit` → 执行 |
 | 系统优化 | `/pd-status` → `evolve-system` → `root-cause` |
 | 项目复盘 | `/pd-daily` → `/pd-okr` → `reflection-log` |
 
@@ -196,7 +196,6 @@ disable-model-invocation: true
 - `triage` - 问题分诊
 - `root-cause` - 根因分析
 - `deductive-audit` - 演绎审计
-- `plan-script` - 计划编排
 - `reflection` - 元认知反思
 - `reflection-log` - 反思落盘
 

package/templates/langs/zh/skills/reflection/SKILL.md

@@ -12,7 +12,7 @@ disable-model-invocation: false
 请执行以下反思步骤：
 
 ## 1. 现状扫描 (Status Scan)
-- **Goal**: 我们最初的目标是什么？(Check `PLAN.md` or early conversation)
+- **Goal**: 我们最初的目标是什么？(检查早期对话上下文)
 - **Status**: 现在完成了多少？卡在哪里？
 - **Cost**: 我们消耗了大量 Token，产出是否匹配？
 
@@ -37,4 +37,4 @@ disable-model-invocation: false
 
 ## 5. 恢复计划 (Recovery)
 - 既然要压缩上下文，我们下一步该如何以“最干净”的状态继续？
-- 更新 `PLAN.md`，标记当前进度，确保压缩后能无缝衔接。
+- 更新 `memory/.scratchpad.md`，标记当前进度，确保压缩后能无缝衔接。

package/templates/langs/zh/skills/report/SKILL.md

@@ -10,4 +10,4 @@ disable-model-invocation: true
 
 ## 执行动作
 1. 立即委派 ``pd_spawn_agent(reporter)``。
-2. 任务描述：“老板想知道当前的情况。请分析当前的对话上下文、`PLAN.md` 和最近的 `memory/ISSUE_LOG.md`，为老板写一份优雅的汇报。请记住先看他的画像！”
+2. 任务描述："老板想知道当前的情况。请分析当前的对话上下文和最近的 `memory/ISSUE_LOG.md`，为老板写一份优雅的汇报。请记住先看他的画像！"

package/templates/workspace/.principles/THINKING_OS.md

@@ -39,8 +39,9 @@
   <!-- 执行与物理限制 (Execution & Physical Constraints) -->
   <directive id="T-05" name="PHYSICAL_DEFENSE_AND_ORCHESTRATION">
     <trigger>当被要求执行大型重构、多文件修改（>2 个文件）或架构变更时。</trigger>
-    <must>限制爆炸半径。你必须起草一个 `PLAN.md`（状态：READY）。在修改任何代码后，必须运行金丝雀测试（例如 `npm test`、linters）以验证完整性。</must>
-    <forbidden>在没有计划的情况下直接执行大规模非结构化变更，或跳过修改后的验证环节。</forbidden>
+    <should>对复杂变更，先描述计划并获得 owner 确认后再执行。</should>
+    <must>限制爆炸半径。在修改任何代码后，必须运行金丝雀测试（例如 `npm test`、linters）以验证完整性。</must>
+    <forbidden>直接执行大规模非结构化变更，或跳过修改后的验证环节。</forbidden>
   </directive>
 
   <directive id="T-06" name="OCCAMS_RAZOR_MVC">

package/core/dist/runtime-v2/__tests__/sqlite-confirm-first-state-store.test.d.ts

@@ -1,2 +0,0 @@
-export {};
-//# sourceMappingURL=sqlite-confirm-first-state-store.test.d.ts.map

package/core/dist/runtime-v2/__tests__/sqlite-confirm-first-state-store.test.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"sqlite-confirm-first-state-store.test.d.ts","sourceRoot":"","sources":["../../../src/runtime-v2/__tests__/sqlite-confirm-first-state-store.test.ts"],"names":[],"mappings":""}