create-principles-disciple 1.102.0 → 1.104.0

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

@@ -11,7 +11,7 @@ import { atomicWriteFileSync } from '../utils/io.js';
 // Re-export queue I/O (extracted to queue-io.ts)
 export { loadEvolutionQueue, saveEvolutionQueue, withQueueLock, acquireQueueLock, requireQueueLock } from './queue-io.js';
 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 { saveEvolutionQueue, requireQueueLock, loadEvolutionQueue } from './queue-io.js';
 import { WorkflowStore } from './subagent-workflow/workflow-store.js';
 import { PrincipleCompiler } from '../core/principle-compiler/index.js';
 import { loadLedger, updatePrinciple } from '../core/principle-tree-ledger.js';
@@ -58,8 +58,8 @@ import { runWorkflowWatchdog } from './workflow-watchdog.js';
 export { runWorkflowWatchdog };
 let timeoutId = null;
 // ── Queue Migration (extracted to queue-migration.ts) ────────────────────────
-import { migrateToV2, isLegacyQueueItem, migrateQueueToV2, DEFAULT_TASK_KIND, DEFAULT_PRIORITY, DEFAULT_MAX_RETRIES } from './queue-migration.js';
-export { migrateToV2, isLegacyQueueItem, migrateQueueToV2, DEFAULT_TASK_KIND, DEFAULT_PRIORITY, DEFAULT_MAX_RETRIES };
+import { migrateToV2, isLegacyQueueItem, migrateQueueToV2, DEFAULT_TASK_KIND, DEFAULT_PRIORITY, DEFAULT_MAX_RETRIES, validateQueueItem, VALID_TASK_KINDS, isValidQueueItem } from './queue-migration.js';
+export { migrateToV2, isLegacyQueueItem, migrateQueueToV2, DEFAULT_TASK_KIND, DEFAULT_PRIORITY, DEFAULT_MAX_RETRIES, validateQueueItem, VALID_TASK_KINDS, isValidQueueItem };
 // Queue lock constants and requireQueueLock are imported from queue-io.ts
 export function extractEvolutionTaskId(task) {
     if (!task)
@@ -302,30 +302,12 @@ async function processEvolutionQueue(wctx, logger, _eventLog, _api) {
             logger?.info?.(`[PD:EvolutionWorker] Dropped ${beforeLegacyPainDrop - queue.length} legacy pain_diagnosis queue item(s); use PainSignalBridge/pd pain record`);
         }
         // Validate queue items — filter out malformed entries before processing.
-        // Malformed items are logged + skipped; they never crash the evolution cycle.
+        // rc-1/rc-4 (ERR-007): consolidated in validateQueueItem (queue-migration.ts)
+        // so every load path applies the same filter. Malformed items are logged +
+        // skipped; they never crash the evolution cycle.
         const beforeValidation = queue.length;
         queue = queue.filter((item) => {
-            const errors = [];
-            if (!item.id || typeof item.id !== 'string')
-                errors.push('missing/invalid id');
-            if (!item.source || typeof item.source !== 'string')
-                errors.push('missing/invalid source');
-            if (typeof item.score !== 'number')
-                errors.push('missing/invalid score');
-            if (!item.status || typeof item.status !== 'string')
-                errors.push('missing/invalid status');
-            if (!item.taskKind || typeof item.taskKind !== 'string')
-                errors.push('missing/invalid taskKind');
-            else {
-                const validTaskKinds = ['model_eval'];
-                if (!validTaskKinds.includes(item.taskKind)) {
-                    errors.push(`invalid taskKind value '${item.taskKind}' (expected one of: ${validTaskKinds.join(', ')})`);
-                }
-            }
-            if (typeof item.retryCount !== 'number')
-                errors.push('missing/invalid retryCount');
-            if (typeof item.maxRetries !== 'number')
-                errors.push('missing/invalid maxRetries');
+            const errors = validateQueueItem(item);
             if (errors.length > 0) {
                 logger?.warn?.(`[PD:EvolutionWorker] Skipping malformed queue item: ${errors.join(', ')} | ${JSON.stringify(item).slice(0, 200)}`);
                 SystemLogger.log(wctx.workspaceDir, 'QUEUE_ITEM_MALFORMED', `Skipped: ${errors.join(', ')} | id=${item.id || 'N/A'}`);
@@ -361,16 +343,11 @@ export async function registerEvolutionTaskSession(workspaceResolve, taskId, ses
         return false;
     const releaseLock = await requireQueueLock(queuePath, logger, 'registerEvolutionTaskSession');
     try {
-        let rawQueue;
-        try {
-            rawQueue = JSON.parse(fs.readFileSync(queuePath, 'utf8'));
-        }
-        catch (parseErr) {
-            logger?.warn?.(`[PD:EvolutionWorker] Failed to parse EVOLUTION_QUEUE for session registration: ${queuePath} - ${parseErr instanceof Error ? parseErr.message : String(parseErr)}`);
-            return false;
-        }
-        // V2: Migrate queue to current schema
-        const queue = migrateQueueToV2(rawQueue);
+        // loadEvolutionQueue handles JSON parse + migrate + validate (rc-1/rc-4).
+        // Previously this inlined JSON.parse + migrate cast without validating,
+        // so malformed queue items could reach the find() below. Reusing the
+        // shared loader keeps a single chokepoint for queue validation.
+        const queue = loadEvolutionQueue(queuePath);
         const task = queue.find((item) => item.id === taskId && item.status === 'in_progress');
         if (!task) {
             logger?.warn?.(`[PD:EvolutionWorker] Could not find in-progress evolution task ${taskId} for session assignment`);
@@ -406,7 +383,11 @@ async function processEvolutionQueueWithResult(wctx, logger, eventLog, api) {
         if (!fs.existsSync(queuePath)) {
             return { queue: queueResult, errors };
         }
-        const queue = JSON.parse(fs.readFileSync(queuePath, 'utf8'));
+        // rc-1/rc-2/rc-4 (ERR-001/ERR-005/ERR-007): use the canonical loader
+        // instead of raw JSON.parse + cast. loadEvolutionQueue handles parse,
+        // migrate, and element-wise validation; malformed items are dropped
+        // with a console.warn (rc-9: no silent fallback).
+        const queue = loadEvolutionQueue(queuePath);
         // Purge stale failed tasks before processing (keeps queue lean)
         const purgeResult = purgeStaleFailedTasks(queue, logger);
         if (purgeResult.purged > 0) {

package/plugin/dist/service/queue-io.js

@@ -11,7 +11,7 @@ import { createHash } from 'crypto';
 import { acquireLockAsync, releaseLock as releaseImportedLock } from '../utils/file-lock.js';
 import { atomicWriteFileSync } from '../utils/io.js';
 import { LockUnavailableError } from '../config/errors.js';
-import { migrateQueueToV2 } from './queue-migration.js';
+import { migrateQueueToV2, validateQueueItem } from './queue-migration.js';
 export const EVOLUTION_QUEUE_LOCK_SUFFIX = '.lock';
 export const LOCK_MAX_RETRIES = 50;
 export const LOCK_RETRY_DELAY_MS = 50;
@@ -72,7 +72,19 @@ export function loadEvolutionQueue(queuePath) {
             rawQueue = [];
         }
     }
-    return migrateQueueToV2(rawQueue);
+    // rc-1/rc-4 (ERR-007): every element of the parsed array is untrusted disk
+    // JSON — validate before returning. Malformed items are filtered out and
+    // reported via console.warn (rc-9: no silent drop). This is the single
+    // chokepoint that loadEvolutionQueue callers inherit.
+    const migrated = migrateQueueToV2(rawQueue);
+    return migrated.filter((item) => {
+        const errors = validateQueueItem(item);
+        if (errors.length > 0) {
+            console.warn(`[queue-io] Dropping malformed queue item: ${errors.join(', ')} | id=${item?.id ?? 'N/A'}`);
+            return false;
+        }
+        return true;
+    });
 }
 export function saveEvolutionQueue(queuePath, queue) {
     atomicWriteFileSync(queuePath, JSON.stringify(queue, null, 2));

package/plugin/dist/service/queue-migration.d.ts

@@ -5,32 +5,8 @@
  * to the V2 schema. Zero I/O, zero imports from evolution-worker.ts.
  */
 import type { TaskKind, TaskPriority } from '../core/trajectory-types.js';
-export type QueueStatus = 'pending' | 'in_progress' | 'completed' | 'failed';
-export type TaskResolution = 'success' | 'failure' | 'skipped';
-export interface EvolutionQueueItem {
-    id: string;
-    taskKind: TaskKind;
-    priority: TaskPriority;
-    source: string;
-    traceId?: string;
-    task?: string;
-    score: number;
-    reason: string;
-    timestamp: string;
-    enqueued_at?: string;
-    started_at?: string;
-    completed_at?: string;
-    assigned_session_key?: string;
-    trigger_text_preview?: string;
-    status: QueueStatus;
-    resolution?: TaskResolution;
-    session_id?: string;
-    agent_id?: string;
-    retryCount: number;
-    maxRetries: number;
-    lastError?: string;
-    resultRef?: string;
-}
+import type { EvolutionQueueItem } from '../core/evolution-types.js';
+export type { QueueStatus, TaskResolution, EvolutionQueueItem } from '../core/evolution-types.js';
 /**
  * Legacy queue item shape (pre-V2) for migration compatibility.
  * These items lack taskKind, priority, retryCount, maxRetries, lastError fields.
@@ -81,3 +57,28 @@ export declare function isLegacyQueueItem(item: RawQueueItem): boolean;
  * Returns a new array with all items migrated to V2 format.
  */
 export declare function migrateQueueToV2(queue: RawQueueItem[]): EvolutionQueueItem[];
+/**
+ * Canonical set of valid taskKind values. Single source of truth — mirrors
+ * TaskKind in trajectory-types.ts. Previously the inline validator in
+ * evolution-worker.ts hard-coded `['model_eval']`, which silently rejected
+ * three legitimate taskKind values (pain_diagnosis / sleep_reflection /
+ * keyword_optimization). Keep this in sync with TaskKind.
+ */
+export declare const VALID_TASK_KINDS: readonly TaskKind[];
+/**
+ * Validate a single queue item loaded from untrusted disk JSON.
+ *
+ * Returns an array of human-readable error reasons; an empty array means the
+ * item is valid. Use {@link isValidQueueItem} for a type-guard form.
+ *
+ * This consolidates the inline validation that lived in processEvolutionQueue
+ * (evolution-worker.ts) so every queue load path (loadEvolutionQueue,
+ * registerEvolutionTaskSession) applies the same filter. rc-4 (ERR-007):
+ * array elements from parsed JSON must be element-wise validated.
+ */
+export declare function validateQueueItem(item: unknown): string[];
+/**
+ * Type-guard convenience over {@link validateQueueItem}.
+ * Drops the reason strings (callers that need them should call validateQueueItem).
+ */
+export declare function isValidQueueItem(item: unknown): item is EvolutionQueueItem;

package/plugin/dist/service/queue-migration.js

@@ -54,3 +54,60 @@ export function isLegacyQueueItem(item) {
 export function migrateQueueToV2(queue) {
     return queue.map(item => isLegacyQueueItem(item) ? migrateToV2(item) : item);
 }
+// ── Validation (rc-1/rc-2, rc-4: validate array elements from untrusted JSON) ─
+/**
+ * Canonical set of valid taskKind values. Single source of truth — mirrors
+ * TaskKind in trajectory-types.ts. Previously the inline validator in
+ * evolution-worker.ts hard-coded `['model_eval']`, which silently rejected
+ * three legitimate taskKind values (pain_diagnosis / sleep_reflection /
+ * keyword_optimization). Keep this in sync with TaskKind.
+ */
+export const VALID_TASK_KINDS = [
+    'pain_diagnosis',
+    'sleep_reflection',
+    'model_eval',
+    'keyword_optimization',
+];
+/**
+ * Validate a single queue item loaded from untrusted disk JSON.
+ *
+ * Returns an array of human-readable error reasons; an empty array means the
+ * item is valid. Use {@link isValidQueueItem} for a type-guard form.
+ *
+ * This consolidates the inline validation that lived in processEvolutionQueue
+ * (evolution-worker.ts) so every queue load path (loadEvolutionQueue,
+ * registerEvolutionTaskSession) applies the same filter. rc-4 (ERR-007):
+ * array elements from parsed JSON must be element-wise validated.
+ */
+export function validateQueueItem(item) {
+    const errors = [];
+    if (item === null || typeof item !== 'object' || Array.isArray(item)) {
+        return ['item is not an object'];
+    }
+    const it = item;
+    if (!it.id || typeof it.id !== 'string')
+        errors.push('missing/invalid id');
+    if (!it.source || typeof it.source !== 'string')
+        errors.push('missing/invalid source');
+    if (typeof it.score !== 'number')
+        errors.push('missing/invalid score');
+    if (!it.status || typeof it.status !== 'string')
+        errors.push('missing/invalid status');
+    if (!it.taskKind || typeof it.taskKind !== 'string')
+        errors.push('missing/invalid taskKind');
+    else if (!VALID_TASK_KINDS.includes(it.taskKind)) {
+        errors.push(`invalid taskKind value '${it.taskKind}' (expected one of: ${VALID_TASK_KINDS.join(', ')})`);
+    }
+    if (typeof it.retryCount !== 'number')
+        errors.push('missing/invalid retryCount');
+    if (typeof it.maxRetries !== 'number')
+        errors.push('missing/invalid maxRetries');
+    return errors;
+}
+/**
+ * Type-guard convenience over {@link validateQueueItem}.
+ * Drops the reason strings (callers that need them should call validateQueueItem).
+ */
+export function isValidQueueItem(item) {
+    return validateQueueItem(item).length === 0;
+}

package/plugin/docs/COMMAND_REFERENCE.md

@@ -12,7 +12,6 @@
 | `/pd-evolution-status` | 查看控制面与进化面的当前状态 | 读取 `RuntimeSummaryService` 的 canonical state |
 | `/pd-status empathy` | 查看情绪/共情事件统计 | 用于观察 `user_empathy` 与 `system_infer` 事件是否稳定落日志 |
 | `/pd-rollback last` | 回滚最近一次情绪惩罚 | 只回滚 `user_empathy` 对应的 GFI slice |
-| `/pd-evolve` | 执行进化任务 | 属于学习面，通过 EP 积累提升权限 |
 | `/pd-help` | 显示帮助 | |
 
 ---

package/plugin/docs/COMMAND_REFERENCE_EN.md

@@ -11,8 +11,6 @@
 | `/pd-evolution-status` | View EP tier, GFI, pain flag, and gate events |
 | `/pd-status empathy` | Inspect empathy/frustration event statistics |
 | `/pd-rollback last` | Roll back the latest empathy penalty |
-| `/pd-evolve` | Run an evolution task |
-| `/pd-evolution-points` | View current EP balance and tier |
 
 ---
 

package/plugin/scripts/sync-plugin.mjs

@@ -383,6 +383,18 @@ function buildPlugin() {
         process.exit(1);
     }
 
+    // Generate .d.ts declarations separately so a tsc failure on unrelated
+    // files does not invalidate the esbuild bundle. Matches install.mjs pattern.
+    console.log('📝 Generating TypeScript declaration files...');
+    try {
+        execSync('npx tsc --emitDeclarationOnly', {
+            cwd: SOURCE_DIR,
+            stdio: 'inherit'
+        });
+    } catch (error) {
+        console.warn('  ⚠️  Declaration generation failed (non-blocking):', error.message);
+    }
+
     verifyBundleContents();
 }
 

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

@@ -200,6 +200,6 @@ When completing any coding task (via AI coding assistant or direct):
 Use this to avoid confusing peer agents with Principles internal workers:
 
 - **Peer agents / peer sessions**: `agents_list`, `sessions_list`, `sessions_send`, `sessions_spawn`
-- **Internal workers** (for example `diagnostician`, `explorer`): use `sessions_spawn with pd-diagnostician/pd-explorer skills`
+- **Internal workers** (for example `explorer`): use `sessions_spawn with pd-explorer skill`
 - **Inspect internal workers**: use `subagents`
-- **Do not** treat `diagnostician` or `explorer` as peer session targets
+- **Do not** treat `explorer` as a peer session target

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

@@ -10,6 +10,6 @@
 ## 4. Agent Routing Clarification
 
 - `agents_list`, `sessions_list`, `sessions_send`, and `sessions_spawn` are for peer agents and peer sessions
-- Use `sessions_spawn` with `pd-diagnostician` or `pd-explorer` skills to start Principles internal workers
+- Use `sessions_spawn` with `pd-explorer` skill to start Principles internal workers (e.g., explorer)
 - `subagents` inspects already-started internal workers and their outputs
 - Do not use peer-session tools to pretend an internal worker is a peer agent

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

@@ -29,7 +29,6 @@ I'm your intelligent mentor, helping you understand and use all features of Prin
 | `/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-evolution-status` | View trust score and security stage | Permission check |
 | `/pd-status` | View system status (GFI and Pain Dictionary) | Health check |
 | `/pd-help` | Get interactive command guidance | This skill |
@@ -57,7 +56,7 @@ I'm your intelligent mentor, helping you understand and use all features of Prin
 
 **Recommended Flow**:
 1. `/pd-status` - Check system status (GFI and Pain Dictionary)
-2. `/pd-evolve` - Start full evolution loop
+2. `/pd-evolution-status` - View EP tier and evolution status
 
 **Script**: "Problems are the fuel of evolution. Let me help you diagnose and fix systematically."
 
@@ -170,7 +169,7 @@ For complex scenarios, combine multiple skills:
 
 | Scenario | Combined Flow |
 |----------|---------------|
-| Major refactor | `/pd-evolve` → `deductive-audit` → execute |
+| Major refactor | `/pd-evolution-status` → `deductive-audit` → execute |
 | System optimization | `/pd-status` → `root-cause` → optimize |
 | Project review | `/pd-evolution-status` → `/pd-status` → `reflection-log` |
 

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

@@ -192,6 +192,6 @@ _This folder is home. Treat it that way._
 用下面这几条避免把同级代理和 Principles 内部 worker 混淆：
 
 - **同级代理 / 同级会话**：`agents_list`、`sessions_list`、`sessions_send`、`sessions_spawn`
-- **内部 worker**（例如 `diagnostician`、`explorer`）：使用 `sessions_spawn` 配合 `pd-diagnostician/pd-explorer` skill 启动
+- **内部 worker**（例如 `explorer`）：使用 `sessions_spawn` 配合 `pd-explorer` skill 启动
 - **查询内部 worker**：使用 `subagents`
-- **不要**把 `diagnostician` 或 `explorer` 当成同级 peer session 目标
+- **不要**把 `explorer` 当成同级 peer session 目标

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

@@ -10,6 +10,6 @@
 ## 4. 智能体路由澄清
 
 - `agents_list`、`sessions_list`、`sessions_send`、`sessions_spawn` 用于同级代理和同级会话
-- 使用 `sessions_spawn` 配合 `pd-diagnostician/pd-explorer` skill 启动 Principles 内部 worker，例如 `diagnostician`、`explorer`
+- 使用 `sessions_spawn` 配合 `pd-explorer` skill 启动 Principles 内部 worker，例如 `explorer`
 - `subagents` 用于查看已启动内部 worker 的状态和输出
 - 不要用同级会话工具把内部 worker 伪装成同级代理

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

@@ -29,7 +29,6 @@ disable-model-invocation: true
 | `/pd-bootstrap` | 环境工具扫描与升级 | 装备升级 |
 | `/pd-research` | 发起工具升级研究 | 深度调研 |
 | `/pd-thinking` | 管理思维模型与候选方案 | 元认知管理 |
-| `/pd-evolve` | 执行完整进化循环 | 问题修复 |
 | `/pd-evolution-status` | 查看EP等级与安全状态 | 状态查询 |
 | `/pd-status` | 查看系统状态（GFI和痛苦词典） | 健康检查 |
 | `/pd-help` | 获取交互式命令引导 | 本技能 |
@@ -57,7 +56,7 @@ disable-model-invocation: true
 
 **推荐流程**:
 1. `/pd-status` - 检查系统状态（GFI 和痛苦词典）
-2. `/pd-evolve` - 启动完整的进化循环
+2. `/pd-evolution-status` - 查看 EP 等级和进化状态
 
 **话术**: "问题就是进化的燃料。让我帮你系统化地诊断和修复。"
 
@@ -170,7 +169,7 @@ disable-model-invocation: true
 
 | 场景 | 组合流程 |
 |------|----------|
-| 大型重构 | `/pd-evolve` → `deductive-audit` → 执行 |
+| 大型重构 | `/pd-evolution-status` → `deductive-audit` → 执行 |
 | 系统优化 | `/pd-status` → `root-cause` → 优化实施 |
 | 项目复盘 | `/pd-evolution-status` → `/pd-status` → `reflection-log` |
 

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

@@ -200,6 +200,6 @@ When completing any coding task (via AI coding assistant or direct):
 Use this to avoid confusing peer agents with Principles internal workers:
 
 - **Peer agents / peer sessions**: `agents_list`, `sessions_list`, `sessions_send`, `sessions_spawn`
-- **Internal workers** (for example `diagnostician`, `explorer`): use `sessions_spawn with pd-diagnostician/pd-explorer skills`
+- **Internal workers** (for example `explorer`): use `sessions_spawn with pd-explorer skill`
 - **Inspect internal workers**: use `subagents`
-- **Do not** treat `diagnostician` or `explorer` as peer session targets
+- **Do not** treat `explorer` as a peer session target

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

@@ -162,20 +162,7 @@ If the user has clear project goals, run `/init-strategy` skill to:
 
 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.
 
@@ -186,7 +173,7 @@ openclaw cron add --name "health-check" \
   --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)
+### 2. Strategy Alignment (Daily at 9 AM)
 
 **What it does:** Checks if daily operations have drifted from CURRENT_FOCUS.md strategic goals.
 
@@ -198,7 +185,7 @@ openclaw cron add --name "strategy-alignment" \
   --message 'Execute strategy alignment check: Compare against memory/okr/CURRENT_FOCUS.md. Confirm if past 24 hours of operations have drifted from strategic focus. Alert user if drifted.'
 ```
 
-### 4. Memory Weekly Cleanup (Monday 10 AM)
+### 3. Memory Weekly Cleanup (Monday 10 AM)
 
 **What it does:** Reviews daily memory files, extracts important content to MEMORY.md, cleans outdated info.
 
@@ -210,7 +197,7 @@ openclaw cron add --name "memory-weekly" \
   --message 'Execute weekly memory cleanup: Review recent memory/YYYY-MM-DD.md files, extract important content to MEMORY.md, clean outdated info.'
 ```
 
-### 5. Weekly Governance (Sunday Midnight UTC)
+### 4. Weekly Governance (Sunday Midnight UTC)
 
 Update WEEK_STATE.json and validate CURRENT_FOCUS.md:
 

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

@@ -53,6 +53,6 @@ Tool returns: Blind Spots → Risk Warnings → Alternative Approaches → Recom
 ## 4. Agent Routing Clarification
 
 - `agents_list`, `sessions_list`, `sessions_send`, and `sessions_spawn` are for peer agents and peer sessions
-- Use `sessions_spawn` with `pd-diagnostician` or `pd-explorer` skills to start Principles internal workers
+- Use `sessions_spawn` with `pd-explorer` skill to start Principles internal workers (e.g., explorer)
 - `subagents` inspects already-started internal workers and their outputs
 - Do not use peer-session tools to pretend an internal worker is a peer agent

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

@@ -26,15 +26,10 @@ 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-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-trust` | 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 |
 
 ---
@@ -60,7 +55,7 @@ I'm your intelligent mentor, helping you understand and use all features of Prin
 
 **Recommended Flow**:
 1. `/pd-status` - Check system status (GFI and Pain Dictionary)
-2. `/pd-evolve` - Start full evolution loop
+2. `/pd-evolution-status` - Start full evolution loop
 
 **Script**: "Problems are the fuel of evolution. Let me help you diagnose and fix systematically."
 
@@ -71,38 +66,26 @@ 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-trust` - View current trust score
-3. `/pd-okr` - Check OKR alignment
+1. `/pd-evolution-status` - Send today's evolution report
+2. `/pd-evolution-status` - View current trust score
 
 **Script**: "Daily report in hand, evolution I command. Let me help you review today's achievements."
 
 ---
 
-### 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"
 
 **Recommended Flow**:
-1. `/pd-trust` - View trust score and security stage
+1. `/pd-evolution-status` - View trust score and security stage
 2. Explain current stage's capability boundaries
 
 **Script**: "Trust is earned, not given. Let me help you understand your current security level."
 
 ---
 
-### Scenario 6: Tool Upgrade Needs
+### Scenario 5: Tool Upgrade Needs
 
 **Trigger**: User says "want to upgrade tools", "research new version", "tech stack update"
 
@@ -160,7 +143,6 @@ Use `AskUserQuestion` to ask user about current task scenario:
 - 🆕 New project initialization
 - 🐛 Bug fix
 - 📊 Daily review
-- 🧹 Workspace cleanup
 - 🔐 Permission/Security
 - 🔧 Tool upgrade
 - ❓ Other
@@ -185,9 +167,9 @@ For complex scenarios, combine multiple skills:
 
 | Scenario | Combined Flow |
 |----------|---------------|
-| Major refactor | `/pd-evolve` → `deductive-audit` → execute |
+| Major refactor | `/pd-evolution-status` → `deductive-audit` → execute |
 | System optimization | `/pd-status` → `evolve-system` → `root-cause` |
-| Project review | `/pd-daily` → `/pd-okr` → `reflection-log` |
+| Project review | `/pd-evolution-status` → `/pd-okr` → `reflection-log` |
 
 ### Internal Skill Calls
 

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

@@ -192,6 +192,6 @@ _This folder is home. Treat it that way._
 用下面这几条避免把同级代理和 Principles 内部 worker 混淆：
 
 - **同级代理 / 同级会话**：`agents_list`、`sessions_list`、`sessions_send`、`sessions_spawn`
-- **内部 worker**（例如 `diagnostician`、`explorer`）：使用 `sessions_spawn` 配合 `pd-diagnostician/pd-explorer` skill 启动
+- **内部 worker**（例如 `explorer`）：使用 `sessions_spawn` 配合 `pd-explorer` skill 启动
 - **查询内部 worker**：使用 `subagents`
-- **不要**把 `diagnostician` 或 `explorer` 当成同级 peer session 目标
+- **不要**把 `explorer` 当成同级 peer session 目标

package/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）是否可用，异常时告警。
 
@@ -186,7 +173,7 @@ openclaw cron add --name "health-check" \
   --system-event '环境健康检查：验证核心工具（rg, node, python）是否可用，检查工作区状态与实际进度是否一致。'
 ```
 
-### 3. 战略对齐检查（每天上午 9 点）
+### 2. 战略对齐检查（每天上午 9 点）
 
 **功能：** 检查过去 24 小时的操作是否偏离 CURRENT_FOCUS.md 战略目标。
 
@@ -198,7 +185,7 @@ openclaw cron add --name "strategy-alignment" \
   --message '执行战略对齐检查：对比 memory/okr/CURRENT_FOCUS.md，确认过去24小时的操作是否偏离战略重点。如有偏离，提醒用户。'
 ```
 
-### 4. Memory 周度整理（每周一上午 10 点）
+### 3. Memory 周度整理（每周一上午 10 点）
 
 **功能：** 回顾每日记忆文件，提炼重要内容到 MEMORY.md，清理过时信息。
 
@@ -210,7 +197,7 @@ openclaw cron add --name "memory-weekly" \
   --message '执行 Memory 周度整理：翻阅近期的 memory/YYYY-MM-DD.md 文件，提炼重要内容到 MEMORY.md，清理过时信息。'
 ```
 
-### 5. 周治理（每周日 UTC 0 点）
+### 4. 周治理（每周日 UTC 0 点）
 
 更新 WEEK_STATE.json 并验证 CURRENT_FOCUS.md：
 

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

@@ -53,6 +53,6 @@ deep_reflect(
 ## 4. 智能体路由澄清
 
 - `agents_list`、`sessions_list`、`sessions_send`、`sessions_spawn` 用于同级代理和同级会话
-- 使用 `sessions_spawn` 配合 `pd-diagnostician/pd-explorer` skill 启动 Principles 内部 worker，例如 `diagnostician`、`explorer`
+- 使用 `sessions_spawn` 配合 `pd-explorer` skill 启动 Principles 内部 worker，例如 `explorer`
 - `subagents` 用于查看已启动内部 worker 的状态和输出
 - 不要用同级会话工具把内部 worker 伪装成同级代理