create-principles-disciple 1.76.0 → 1.78.0

package/plugin/dist/service/evolution-worker.js

@@ -13,9 +13,6 @@ export { loadEvolutionQueue, saveEvolutionQueue, withQueueLock, acquireQueueLock
 export { EVOLUTION_QUEUE_LOCK_SUFFIX, LOCK_MAX_RETRIES, LOCK_RETRY_DELAY_MS, LOCK_STALE_MS } from './queue-io.js';
 import { saveEvolutionQueue, requireQueueLock } from './queue-io.js';
 import { WorkflowStore } from './subagent-workflow/workflow-store.js';
-import { WorkflowFunnelLoader, PiAiRuntimeAdapter, CorrectionObserver, AgentScheduler, } from '@principles/core/runtime-v2';
-import { KeywordOptimizationService } from './keyword-optimization-service.js';
-import { CorrectionCueLearner } from '../core/correction-cue-learner.js';
 import { PrincipleCompiler } from '../core/principle-compiler/index.js';
 import { loadLedger, updatePrinciple } from '../core/principle-tree-ledger.js';
 import { findRecentDuplicateTask } from './evolution-dedup.js';
@@ -482,46 +479,6 @@ async function processEvolutionQueueWithResult(wctx, logger, eventLog, api) {
     }
     return { queue: queueResult, errors };
 }
-function resolveCorrectionObserver(wctx, logger) {
-    try {
-        const loader = new WorkflowFunnelLoader(wctx.stateDir);
-        const funnel = loader.getFunnel('pd-correction-observer');
-        const policy = funnel?.policy;
-        if (!policy || policy.runtimeKind !== 'pi-ai') {
-            logger?.debug?.('[PD:Correction] workflows.yaml pd-correction-observer policy not found. Falling back to environment variables.');
-            const provider = process.env.PD_CORRECTION_PROVIDER || 'anthropic';
-            const model = process.env.PD_CORRECTION_MODEL || 'anthropic/claude-3-5-sonnet';
-            const apiKeyEnv = process.env.PD_CORRECTION_API_KEY_ENV || 'ANTHROPIC_API_KEY';
-            const baseUrl = process.env.PD_CORRECTION_BASE_URL;
-            if (!process.env[apiKeyEnv]) {
-                logger?.debug?.(`[PD:Correction] Correction observer API key env ${apiKeyEnv} is not set. Periodic optimization disabled.`);
-                return null;
-            }
-            const adapter = new PiAiRuntimeAdapter({
-                provider,
-                model,
-                apiKeyEnv,
-                baseUrl,
-                workspace: wctx.workspaceDir,
-            });
-            return new CorrectionObserver({ runtimeAdapter: adapter });
-        }
-        const adapter = new PiAiRuntimeAdapter({
-            provider: String(policy.provider),
-            model: String(policy.model),
-            apiKeyEnv: String(policy.apiKeyEnv),
-            maxRetries: policy.maxRetries,
-            timeoutMs: policy.timeoutMs ?? 30_000,
-            baseUrl: policy.baseUrl,
-            workspace: wctx.workspaceDir,
-        });
-        return new CorrectionObserver({ runtimeAdapter: adapter }, { timeoutMs: policy.timeoutMs });
-    }
-    catch (err) {
-        logger?.warn?.(`[PD:Correction] Failed to resolve CorrectionObserver: ${String(err)}`);
-        return null;
-    }
-}
 export const EvolutionWorkerService = {
     id: 'principles-evolution-worker',
     api: null,
@@ -587,73 +544,7 @@ export const EvolutionWorkerService = {
                     await processDetectionQueue(wctx, api, eventLog);
                 }
                 // processPromotion removed (D-06) — promotion via PAIN_CANDIDATES no longer needed
-                // ── Correction Observer: periodic keyword optimization (D-40-08 / H-1) ──
-                try {
-                    const observer = resolveCorrectionObserver(wctx, logger);
-                    if (observer) {
-                        logger?.info?.('[PD:EvolutionWorker] Correction Observer resolved. Initiating periodic optimization...');
-                        const db = TrajectoryRegistry.get(wctx.workspaceDir);
-                        const recentSessions = db.listRecentSessions({ limit: 20 });
-                        const recentSessionIds = recentSessions.map(s => s.sessionId);
-                        if (recentSessionIds.length > 0) {
-                            const recentMessages = [];
-                            for (const sId of recentSessionIds.slice(0, 5)) {
-                                try {
-                                    const turns = db.listUserTurnsForSession(sId);
-                                    for (const t of turns) {
-                                        if (t.rawExcerpt) {
-                                            recentMessages.push(t.rawExcerpt);
-                                        }
-                                    }
-                                }
-                                catch (turnErr) {
-                                    logger?.warn?.(`[PD:EvolutionWorker] Failed to load user turns for session ${sId}: ${String(turnErr)}`);
-                                }
-                            }
-                            const learner = CorrectionCueLearner.get(wctx.stateDir);
-                            const keywords = learner.getStore().keywords;
-                            const keywordStoreSummary = {
-                                totalKeywords: keywords.length,
-                                terms: keywords.map(k => ({
-                                    term: k.term,
-                                    weight: k.weight,
-                                    hitCount: k.hitCount ?? 0,
-                                    truePositiveCount: k.truePositiveCount ?? 0,
-                                    falsePositiveCount: k.falsePositiveCount ?? 0,
-                                })),
-                            };
-                            const optimizationService = KeywordOptimizationService.get(wctx.stateDir, wctx.workspaceDir, logger);
-                            const trajectoryHistory = await optimizationService.buildTrajectoryHistory(recentSessionIds);
-                            const payload = {
-                                parentSessionId: 'evolution-worker',
-                                workspaceDir: wctx.workspaceDir,
-                                keywordStoreSummary,
-                                recentMessages,
-                                trajectoryHistory,
-                            };
-                            const scheduler = new AgentScheduler();
-                            scheduler.register({
-                                agentId: 'correction-observer',
-                                mode: 'realtime',
-                                runner: observer,
-                            });
-                            logger?.info?.(`[PD:EvolutionWorker] Dispatching correction-observer with ${trajectoryHistory.length} trajectory events, ${recentMessages.length} recent messages.`);
-                            const result = await scheduler.dispatch('correction-observer', payload);
-                            logger?.info?.(`[PD:EvolutionWorker] Correction-observer completed: updated=${result.updated}, summary="${result.summary}"`);
-                            if (result.updated) {
-                                optimizationService.applyResult(result);
-                            }
-                        }
-                        else {
-                            logger?.info?.('[PD:EvolutionWorker] No recent sessions found. Skipping correction optimization.');
-                        }
-                    }
-                }
-                catch (corrErr) {
-                    const corrErrMsg = `Correction observer execution failed: ${String(corrErr)}`;
-                    cycleResult.errors.push(corrErrMsg);
-                    logger?.warn?.(`[PD:EvolutionWorker] ${corrErrMsg}`);
-                }
+                // Correction Observer extracted to independent service (PRI-293) — no longer runs on EvolutionWorker heartbeat
                 try {
                     const subagentRuntime = api?.runtime?.subagent;
                     const workflowStore = new WorkflowStore({ workspaceDir: wctx.workspaceDir });

package/plugin/dist/types.d.ts

@@ -25,9 +25,9 @@ export interface ContextInjectionConfig {
 }
 /**
  * Default context injection configuration
- * Based on user requirements:
+ * Based on MVP-first strategy (ADR-0014):
  * - principles: always on (not configurable)
- * - thinkingOs: true (can be turned off)
+ * - thinkingOs: false by default (MVP-Quiet, user can opt-in via /pd-context)
  * - projectFocus: 'off' (default closed, user can enable)
  */
 export declare const defaultContextConfig: ContextInjectionConfig;

package/plugin/dist/types.js

@@ -1,12 +1,12 @@
 /**
  * Default context injection configuration
- * Based on user requirements:
+ * Based on MVP-first strategy (ADR-0014):
  * - principles: always on (not configurable)
- * - thinkingOs: true (can be turned off)
+ * - thinkingOs: false by default (MVP-Quiet, user can opt-in via /pd-context)
  * - projectFocus: 'off' (default closed, user can enable)
  */
 export const defaultContextConfig = {
-    thinkingOs: true,
+    thinkingOs: false,
     projectFocus: 'off',
     evolutionContext: {
         enabled: true,

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

@@ -145,12 +145,11 @@ If the user has clear project goals, run `/init-strategy` skill to:
 
 ## ⏰ Cron Jobs Initialization (Recommended)
 
-**Why you need this:** Your HEARTBEAT.md has been simplified to reduce token cost. But the tasks that were removed (grooming, health checks, strategy alignment, weekly governance) are still important — they just moved here. Without these cron jobs, your workspace will accumulate temp files, drift from strategy, and lose track of weekly progress.
+**Why you need this:** Your HEARTBEAT.md has been simplified to reduce token cost. But the tasks that were removed (health checks, strategy alignment, weekly governance) are still important — they just moved here. Without these cron jobs, your workspace will drift from strategy and lose track of weekly progress.
 
 **How to install:** Ask the user for permission, then execute the CLI commands below. Each command creates a background task that runs automatically.
 
 **What you get:**
-- Clean workspace (no temp file buildup)
 - Early warning on tool failures
 - Automatic strategy alignment
 - Weekly governance with evidence-based task validation
@@ -158,24 +157,11 @@ If the user has clear project goals, run `/init-strategy` skill to:
 
 ### Ask the User
 
-> "I can set up background cron jobs for automatic maintenance: cleanup, health checks, strategy alignment, and weekly governance. Should I configure them?"
+> "I can set up background cron jobs for automatic maintenance: health checks, strategy alignment, and weekly governance. Should I configure them?"
 
 If the user agrees, **execute these commands:**
 
-### 1. Grooming (Daily at 2 AM)
-
-**What it does:** Cleans workspace temp files daily to prevent clutter buildup.
-
-```bash
-openclaw cron add --name "pd-grooming-daily" \
-  --cron "0 2 * * *" --tz "UTC" \
-  --session isolated \
-  --light-context \
-  --no-deliver \
-  --message 'Execute pd-grooming skill: Check workspace root, clean temp files and digital clutter. Follow safety rules strictly. Do not delete business code.'
-```
-
-### 2. Health Check (Every 4 hours)
+### 1. Health Check (Every 4 hours)
 
 **What it does:** Verifies core tools (rg, node, python) are available and alerts on failure.
 
@@ -183,7 +169,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)
@@ -220,7 +206,7 @@ openclaw cron add --name "weekly-governance" \
   --cron "0 0 * * 0" --tz "UTC" \
   --session isolated \
   --timeout 300000 \
-  --message 'Execute weekly governance: 1) Validate CURRENT_FOCUS.md claims (PR merged? docs exist? tests pass?), 2) Update WEEK_STATE.json metrics, 3) Record to WEEK_EVENTS.jsonl, 4) If task queue empty, derive tasks from OKR and notify user'
+  --message 'Execute weekly governance: 1) Validate CURRENT_FOCUS.md claims (PR merged? docs exist? tests pass?), 2) Update WEEK_STATE.json metrics, 3) Record to WEEK_EVENTS.jsonl, 4) If task queue empty, remind user to plan next phase tasks'
 ```
 
 **JSON config reference:**

package/plugin/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>
 

package/plugin/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/plugin/templates/langs/en/skills/bootstrap-tools/SKILL.md

@@ -46,7 +46,7 @@ Your goal is to equip the agent team with the most advanced weapons. By analyzin
             ## Environment Capabilities
             Check @.state/SYSTEM_CAPABILITIES.json for high-performance tools (e.g., ripgrep, ast-grep) available in this environment. Use them!
             ```
-          - Prompt user to run `/manage-okr` or `/admin diagnose` to let Agent perceive new capabilities.
+          - Prompt user to run `/pd-status` or `/admin diagnose` to let Agent perceive new capabilities.
 
 ## Core Principles
 - **Prefer New Over Old**: Dare to recommend new tools to replace old ones (e.g., recommend `pnpm` over `npm`, `vitest` over `jest`), but explain the reasoning.

package/plugin/templates/langs/en/skills/init-strategy/SKILL.md

@@ -51,4 +51,4 @@ Based on user's responses, extract 1-3 macro **Objectives (O)**.
 ```
 
 ## Completion
-After writing, prompt user: "✅ Strategic anchor locked. Recommend running `/manage-okr` for quarterly/iteration-level task breakdown."
+After writing, prompt user: "✅ Strategic anchor locked. Recommend running `/pd-status` to check system status, or use `/pd-bootstrap` to scan environment tools."

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

@@ -25,16 +25,13 @@ I'm your intelligent mentor, helping you understand and use all features of Prin
 
 | Command | Purpose | Use Case |
 |---------|---------|----------|
-| `/pd-init` | Initialize strategy and OKRs | New project startup |
-| `/pd-okr` | Objectives and Key Results management | Weekly/monthly review |
+| `/pd-init` | Initialize strategy | New project startup |
 | `/pd-bootstrap` | Environment tool scan and upgrade | Tool upgrade |
 | `/pd-research` | Initiate tool upgrade research | Deep research |
 | `/pd-thinking` | Manage mental models and candidates | Metacognition |
 | `/pd-evolve` | Execute full evolution loop | Bug fix |
-| `/pd-daily` | Configure and send evolution daily report | Daily review |
 | `/pd-evolution-status` | View trust score and security stage | Permission check |
 | `/pd-status` | View system status (GFI and Pain Dictionary) | Health check |
-| `/pd-grooming` | Workspace digital cleanup | Entropy reduction |
 | `/pd-help` | Get interactive command guidance | This skill |
 
 ---
@@ -46,7 +43,7 @@ I'm your intelligent mentor, helping you understand and use all features of Prin
 **Trigger**: User says "I just created a new project" or similar
 
 **Recommended Flow**:
-1. `/pd-init` - Establish strategic vision and OKR framework
+1. `/pd-init` - Establish strategic vision
 2. `/pd-bootstrap` - Scan environment tools, get capability list
 3. `/pd-thinking` - Establish project's mental model baseline
 
@@ -71,26 +68,14 @@ I'm your intelligent mentor, helping you understand and use all features of Prin
 **Trigger**: User says "what did I do today", "check progress", "give me a report"
 
 **Recommended Flow**:
-1. `/pd-daily` - Send today's evolution report
-2. `/pd-evolution-status` - View current trust score
-3. `/pd-okr` - Check OKR alignment
+1. `/pd-evolution-status` - View current trust score
+2. `/pd-status` - Check GFI and Pain Dictionary status
 
-**Script**: "Daily report in hand, evolution I command. Let me help you review today's achievements."
+**Script**: "Let me help you review the current system status."
 
 ---
 
-### Scenario 4: Messy Workspace
-
-**Trigger**: User says "project is too messy", "too many files", "need to organize"
-
-**Recommended Flow**:
-1. `/pd-grooming` - Start workspace cleanup
-
-**Script**: "Digital cleanliness is a virtue. Let me help you reduce entropy."
-
----
-
-### Scenario 5: Permission or Security Related
+### Scenario 4: Permission or Security Related
 
 **Trigger**: User says "not enough permissions", "blocked", "security level"
 
@@ -186,8 +171,8 @@ For complex scenarios, combine multiple skills:
 | Scenario | Combined Flow |
 |----------|---------------|
 | Major refactor | `/pd-evolve` → `deductive-audit` → execute |
-| System optimization | `/pd-status` → `evolve-system` → `root-cause` |
-| Project review | `/pd-daily` → `/pd-okr` → `reflection-log` |
+| System optimization | `/pd-status` → `root-cause` → optimize |
+| Project review | `/pd-evolution-status` → `/pd-status` → `reflection-log` |
 
 ### Internal Skill Calls
 

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/BOOTSTRAP.md

@@ -162,20 +162,7 @@ memory/
 
 如果用户同意，**执行以下命令：**
 
-### 1. 熵减巡检（每天凌晨 2 点）
-
-**功能：** 每天清理工作区临时文件，保持项目整洁。
-
-```bash
-openclaw cron add --name "pd-grooming-daily" \
-  --cron "0 2 * * *" --tz "UTC" \
-  --session isolated \
-  --light-context \
-  --no-deliver \
-  --message '执行 pd-grooming 技能：检查工作区根目录，清理临时文件和数字垃圾。严格遵循安全红线，不要删除业务代码。'
-```
-
-### 2. 环境健康检查（每 4 小时）
+### 1. 环境健康检查（每 4 小时）
 
 **功能：** 验证核心工具（rg, node, python）是否可用，异常时告警。
 
@@ -183,7 +170,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 点）
@@ -220,7 +207,7 @@ openclaw cron add --name "weekly-governance" \
   --cron "0 0 * * 0" --tz "UTC" \
   --session isolated \
   --timeout 300000 \
-  --message '执行周治理：1) 验证 CURRENT_FOCUS.md 声称（PR 合并？文档存在？测试通过？），2) 更新 WEEK_STATE.json 指标，3) 记录到 WEEK_EVENTS.jsonl，4) 如果任务队列为空，从 OKR 推导任务并通知用户'
+  --message '执行周治理：1) 验证 CURRENT_FOCUS.md 声称（PR 合并？文档存在？测试通过？），2) 更新 WEEK_STATE.json 指标，3) 记录到 WEEK_EVENTS.jsonl，4) 如果任务队列为空，提醒用户规划下一阶段任务'
 ```
 
 **JSON 配置参考：**

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>
 

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/bootstrap-tools/SKILL.md

@@ -46,7 +46,7 @@ disable-model-invocation: true
             ## Environment Capabilities
             Check @.state/SYSTEM_CAPABILITIES.json for high-performance tools (e.g., ripgrep, ast-grep) available in this environment. Use them!
             ```
-          - 提示用户运行 `/manage-okr` 或 `/admin diagnose` 以让 Agent 感知新能力。
+          - 提示用户运行 `/pd-status` 或 `/admin diagnose` 以让 Agent 感知新能力。
 ## 核心原则
 - **喜新厌旧**: 敢于推荐新工具替代旧工具（如推荐 `pnpm` 替 `npm`，推荐 `vitest` 替 `jest`），但要说明理由。
 - **安全第一**: 在安装前必须获得用户明确授权。

package/plugin/templates/langs/zh/skills/init-strategy/SKILL.md

@@ -51,4 +51,4 @@ disable-model-invocation: true
 ```
 
 ## 结项
-完成写入后，提示用户：“✅ 战略锚点已锁定。建议运行 `/manage-okr` 进行季度/迭代级的任务拆解。”
+完成写入后，提示用户：”✅ 战略锚点已锁定。建议运行 `/pd-status` 查看系统状态，或使用 `/pd-bootstrap` 扫描环境工具。”

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

@@ -25,16 +25,13 @@ disable-model-invocation: true
 
 | 命令 | 用途 | 适用场景 |
 |------|------|----------|
-| `/pd-init` | 初始化战略与OKR | 新项目启动 |
-| `/pd-okr` | 目标与关键结果管理 | 周/月度复盘 |
+| `/pd-init` | 初始化战略 | 新项目启动 |
 | `/pd-bootstrap` | 环境工具扫描与升级 | 装备升级 |
 | `/pd-research` | 发起工具升级研究 | 深度调研 |
 | `/pd-thinking` | 管理思维模型与候选方案 | 元认知管理 |
 | `/pd-evolve` | 执行完整进化循环 | 问题修复 |
-| `/pd-daily` | 配置并发送进化日报 | 日常查看 |
 | `/pd-evolution-status` | 查看EP等级与安全状态 | 状态查询 |
 | `/pd-status` | 查看系统状态（GFI和痛苦词典） | 健康检查 |
-| `/pd-grooming` | 工作区数字大扫除 | 熵减维护 |
 | `/pd-help` | 获取交互式命令引导 | 本技能 |
 
 ---
@@ -71,26 +68,14 @@ disable-model-invocation: true
 **触发条件**: 用户说"今天干了什么"、"看看进度"、"汇报一下"
 
 **推荐流程**:
-1. `/pd-daily` - 发送今日进化日报
-2. `/pd-evolution-status` - 查看当前信任积分
-3. `/pd-okr` - 检查 OKR 对齐情况
+1. `/pd-evolution-status` - 查看当前信任积分
+2. `/pd-status` - 查看 GFI 和痛苦词典状态
 
-**话术**: "日报在手，进化我有。让我帮你回顾今天的成果。"
+**话术**: "让我帮你回顾一下系统状态。"
 
 ---
 
-### 场景 4: 工作区太乱
-
-**触发条件**: 用户说"项目太乱了"、"文件一堆"、"需要整理"
-
-**推荐流程**:
-1. `/pd-grooming` - 启动工作区大扫除
-
-**话术**: "数字洁癖是一种美德。让我帮你熵减。"
-
----
-
-### 场景 5: 权限或安全相关
+### 场景 4: 权限或安全相关
 
 **触发条件**: 用户说"权限不够"、"被拦截了"、"安全等级"
 
@@ -186,8 +171,8 @@ disable-model-invocation: true
 | 场景 | 组合流程 |
 |------|----------|
 | 大型重构 | `/pd-evolve` → `deductive-audit` → 执行 |
-| 系统优化 | `/pd-status` → `evolve-system` → `root-cause` |
-| 项目复盘 | `/pd-daily` → `/pd-okr` → `reflection-log` |
+| 系统优化 | `/pd-status` → `root-cause` → 优化实施 |
+| 项目复盘 | `/pd-evolution-status` → `/pd-status` → `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>
 

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>
 

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/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/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/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 点）