principles-disciple 1.81.0 → 1.83.0

package/openclaw.plugin.json

@@ -2,7 +2,7 @@
   "id": "principles-disciple",
   "name": "Principles Disciple",
   "description": "Evolutionary programming agent framework with strategic guardrails and reflection loops.",
-  "version": "1.81.0",
+  "version": "1.83.0",
   "activation": {
     "onCapabilities": [
       "hook"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "principles-disciple",
-  "version": "1.81.0",
+  "version": "1.83.0",
   "description": "Native OpenClaw plugin for Principles Disciple",
   "type": "module",
   "main": "./dist/bundle.js",
@@ -52,12 +52,12 @@
     "@types/ws": "^8.5.13",
     "@typescript-eslint/eslint-plugin": "^8.58.2",
     "@typescript-eslint/parser": "^8.58.0",
-    "@vitest/coverage-v8": "^4.1.5",
+    "@vitest/coverage-v8": "^4.1.8",
     "esbuild": "^0.28.0",
-    "eslint": "^10.2.1",
+    "eslint": "^10.4.1",
     "jsdom": "^29.1.1",
     "typescript": "^6.0.3",
-    "vitest": "^4.1.5",
+    "vitest": "^4.1.8",
     "ws": "^8.18.0"
   },
   "peerDependencies": {

package/src/commands/strategy.ts

@@ -19,21 +19,3 @@ export function handleInitStrategy(ctx: PluginCommandContext): PluginCommandResu
       `Then update \`${userContextPath}\` with key user preferences discovered.`,
   };
 }
-
-export function handleManageOkr(ctx: PluginCommandContext): PluginCommandResult {
-  const workspaceDir = resolvePluginCommandWorkspaceDir(ctx, 'strategy:manageOkr');
-  const wctx = WorkspaceContext.fromHookContext({ workspaceDir, ...ctx.config });
-
-  const focusPath = wctx.resolve('CURRENT_FOCUS').replace(workspaceDir, '').replace(/^\/+/, '');
-  const weekStatePath = wctx.resolve('WEEK_STATE').replace(workspaceDir, '').replace(/^\/+/, '');
-
-  return {
-    text:
-      `📊 **OKR Management**\n\n` +
-      `The Agent will analyze recent work and align sub-agent objectives.\n\n` +
-      `**Instructions for Agent:** Read \`${focusPath}\` and \`${weekStatePath}\`. ` +
-      `Compare them against recent session history. ` +
-      `Update OKRs as needed and output a brief alignment report. ` +
-      `If OKRs are stale (>7 days), prompt the user for a re-alignment conversation.`,
-  };
-}

package/src/i18n/commands.ts

@@ -21,10 +21,6 @@ export const commandDescriptions: Record<string, Record<SupportedLanguage, strin
     zh: '初始化工作区（生成 PRINCIPLES.md、THINKING_OS.md 等）',
     en: 'Initialize workspace (generate PRINCIPLES.md, THINKING_OS.md, etc.)'
   },
-  'pd-okr': {
-    zh: '管理 OKR 目标与关键结果',
-    en: 'Manage OKR goals and key results'
-  },
   'pd-bootstrap': {
     zh: '扫描环境工具并建议升级',
     en: 'Scan environment tools and suggest upgrades'
@@ -37,14 +33,6 @@ export const commandDescriptions: Record<string, Record<SupportedLanguage, strin
     zh: '管理思维模型 [status|propose|audit]（默认关闭，/pd-context thinking on 开启）',
     en: 'Manage Thinking OS [status|propose|audit] (off by default, enable via /pd-context thinking on)'
   },
-  'pd-daily': {
-    zh: '配置并发送进化日报',
-    en: 'Configure and send daily evolution report'
-  },
-  'pd-grooming': {
-    zh: '工作区清理与大扫除',
-    en: 'Workspace cleanup and grooming'
-  },
   'pd-help': {
     zh: '显示所有命令和使用指南',
     en: 'Show all commands and usage guide'

package/src/index.ts

@@ -32,7 +32,7 @@ import { handleBeforeReset, handleBeforeCompaction, handleAfterCompaction } from
 import { handleLlmOutput } from './hooks/llm.js';
 import { handleSubagentEnded } from './hooks/subagent.js';
 import * as TrajectoryCollector from './hooks/trajectory-collector.js';
-import { handleInitStrategy, handleManageOkr } from './commands/strategy.js';
+import { handleInitStrategy } from './commands/strategy.js';
 import { handleBootstrapTools, handleResearchTools } from './commands/capabilities.js';
 import { handleThinkingOs } from './commands/thinking-os.js';
 import { handlePainCommand, handlePainReportCommand } from './commands/pain.js';
@@ -603,24 +603,12 @@ const plugin = {
      
     registerCommandWithAlias('pd-init', 'pdi', getCommandDescription('pd-init', language), (ctx: any) => handleInitStrategy(ctx));
      
-    registerCommandWithAlias('pd-okr', 'pdk', getCommandDescription('pd-okr', language), (ctx: any) => handleManageOkr(ctx));
-     
     registerCommandWithAlias('pd-bootstrap', 'pdb', getCommandDescription('pd-bootstrap', language), (ctx: any) => handleBootstrapTools(ctx));
-     
+
     registerCommandWithAlias('pd-research', 'pdr', getCommandDescription('pd-research', language), (ctx: any) => handleResearchTools(ctx));
-     
+
     registerCommandWithAlias('pd-thinking', 'pdt', getCommandDescription('pd-thinking', language), (ctx: any) => handleThinkingOs(ctx), { acceptsArgs: true });
-     
-    registerCommandWithAlias('pd-daily', 'pdd', getCommandDescription('pd-daily', language), () => ({
-      text: language === 'zh'
-        ? "请执行 pd-daily 技能来配置并发送进化日报。系统将引导你完成配置流程，包括发送时间、渠道和报告风格偏好。"
-        : "Please execute the pd-daily skill to configure and send your daily evolution report. The system will guide you through the configuration process."
-    }));
-    registerCommandWithAlias('pd-grooming', 'pdg', getCommandDescription('pd-grooming', language), () => ({
-      text: language === 'zh'
-        ? "请执行 pd-grooming 技能来执行大扫除。例如输入: '执行 pd-grooming 技能'"
-        : "Please execute the pd-grooming skill to clean up. For example: 'Execute pd-grooming skill'"
-    }));
+
     registerCommandWithAlias('pd-help', 'pdh', getCommandDescription('pd-help', language), () => {
         if (language === 'zh') {
           return { text: `
@@ -636,10 +624,7 @@ const plugin = {
 ## 状态查询
 | 短命令 | 长命令 | 用途 |
 |--------|--------|------|
-| \`/pdk\` | \`/pd-okr\` | OKR 目标管理 |
 | \`/pdt\` | \`/pd-thinking\` | 思维模型管理 |
-| \`/pdd\` | \`/pd-daily\` | 进化日报 |
-| \`/pdg\` | \`/pd-grooming\` | 工作区清理 |
 
 ## 其他命令
 | 命令 | 用途 |
@@ -667,10 +652,7 @@ const plugin = {
 ## Status
 | Short | Full | Purpose |
 |-------|------|---------|
-| \`/pdk\` | \`/pd-okr\` | OKR goal management |
 | \`/pdt\` | \`/pd-thinking\` | Mental model management |
-| \`/pdd\` | \`/pd-daily\` | Evolution report |
-| \`/pdg\` | \`/pd-grooming\` | Workspace cleanup |
 
 ## Other Commands
 | Command | Purpose |

package/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.
 
@@ -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/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/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/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/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）是否可用，异常时告警。
 
@@ -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/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/templates/langs/zh/skills/init-strategy/SKILL.md

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

package/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/tests/commands/strategy.test.ts

@@ -1,9 +1,9 @@
 import { describe, it, expect } from 'vitest';
-import { handleInitStrategy, handleManageOkr } from '../../src/commands/strategy';
+import { handleInitStrategy } from '../../src/commands/strategy';
 
 describe('Slash Commands Hook', () => {
   it('should handle /init-strategy command', () => {
-    const mockCtx = { 
+    const mockCtx = {
         workspaceDir: '/mock/workspace',
         commandBody: '/init-strategy',
         channel: 'cli',
@@ -16,19 +16,4 @@ describe('Slash Commands Hook', () => {
     expect(result).toBeDefined();
     expect(result.text).toContain('Strategy Initialization');
   });
-
-  it('should handle /manage-okr command', () => {
-    const mockCtx = { 
-        workspaceDir: '/mock/workspace',
-        commandBody: '/manage-okr',
-        channel: 'cli',
-        isAuthorizedSender: true,
-        config: {} as any
-    };
-
-    const result = handleManageOkr(mockCtx as any);
-
-    expect(result).toBeDefined();
-    expect(result.text).toContain('OKR Management');
-  });
-});
+});

package/templates/langs/en/skills/ai-sprint-orchestration/EXAMPLES.md

@@ -1,63 +0,0 @@
-# AI Sprint Orchestration Examples
-
-## Example 1: baseline + validation
-
-```powershell
-node scripts/run.mjs --self-check
-node scripts/run.mjs --help
-node scripts/run.mjs --task workflow-validation-minimal
-node scripts/run.mjs --task workflow-validation-minimal-verify
-```
-
-## Example 2: custom runtime root
-
-```powershell
-node scripts/run.mjs --task workflow-validation-minimal --runtime-root D:/Temp/ai-sprint-runtime
-```
-
-## Example 3: classify a failure
-
-- `workflow bug`: package-local script still writes to repo-root `ops/ai-sprints`
-- `agent behavior issue`: reviewer omits `VERDICT` or malformed `DIMENSIONS`
-- `environment issue`: `acpx` missing or workspace not writable
-- `sample-spec issue`: validation spec asks for a field that the current product sample does not implement
-
-## Example 4: when to stop
-
-Stop the iteration after classification if:
-
-- the issue belongs to `packages/openclaw-plugin`
-- the issue depends on `D:/Code/openclaw`
-- the fix would require dashboard/stageGraph/self-optimization sprint expansion
-- the problem is a sample-side or product-side gap rather than workflow plumbing
-
-## Example 5: start from a complex bugfix template
-
-1. Copy `references/specs/bugfix-complex-template.json`
-2. Replace every placeholder in `taskContract`
-3. Narrow `executionScope` to the smallest useful round
-4. Run the packaged entrypoint with the edited spec:
-
-```powershell
-node scripts/run.mjs --task custom-bugfix --task-spec D:/path/to/your-bugfix-spec.json
-```
-
-## Example 6: start from a complex feature template
-
-1. Copy `references/specs/feature-complex-template.json`
-2. Fill `Goal`, `In scope`, `Out of scope`, `Validation commands`, and `Expected artifacts`
-3. Confirm the spec does not require product-side closure outside this milestone
-4. Run:
-
-```powershell
-node scripts/run.mjs --task custom-feature --task-spec D:/path/to/your-feature-spec.json
-```
-
-## Example 7: inspect checkpoint summary before continuation
-
-When a round ends in `revise`, inspect:
-
-- `stages/<stage>/checkpoint-summary.md`
-- `stages/<stage>/handoff.json`
-
-The next round should use the checkpoint summary as the primary carry-forward context and only fall back to full prior decision text when needed.

package/templates/langs/en/skills/ai-sprint-orchestration/REFERENCE.md

@@ -1,136 +0,0 @@
-# AI Sprint Orchestration Reference
-
-## Package layout
-
-- `scripts/run.mjs`: package-local orchestrator entrypoint
-- `scripts/lib/`: decision, contract validation, state store, spec loading, archive helpers
-- `references/specs/`: built-in validation specs
-- `references/agent-registry.json`: package-local agent/model registry
-- `references/workflow-v1-acceptance-checklist.md`: handoff checklist
-- `runtime/`: default location for run artifacts
-
-## Runtime layout
-
-Default runtime root:
-
-- `packages/openclaw-plugin/templates/langs/<lang>/skills/ai-sprint-orchestration/runtime`
-
-Subdirectories:
-
-- `runs/<run-id>/`
-- `archive/<run-id>/`
-- `tmp/sprint-agent/<run-id>/...`
-
-Override with either:
-
-- `--runtime-root <path>`
-- `AI_SPRINT_RUNTIME_ROOT=<path>`
-
-## Self check
-
-Run this first in a newly installed environment:
-
-- `node scripts/run.mjs --self-check`
-
-It verifies:
-
-- package-local references exist
-- built-in specs load
-- `agent-registry.json` exists
-- `acpx` is callable
-- runtime root is writable
-
-## Built-in specs
-
-- `workflow-validation-minimal`
-- `workflow-validation-minimal-verify`
-- `bugfix-complex-template` (copy and fill before use)
-- `feature-complex-template` (copy and fill before use)
-
-These built-in specs are package self-checks. They validate the workflow package itself, not product features.
-
-## Key artifacts
-
-For each run, inspect:
-
-- `sprint.json`
-- `timeline.md`
-- `latest-summary.md`
-- `decision.md`
-- `scorecard.json`
-
-Important persisted fields:
-
-- `outputQuality`
-- `qualityReasons`
-- `validation`
-- `nextRunRecommendation`
-- `failureClassification`
-- `failureSource`
-- `recommendedNextAction`
-
-Per-stage carry-forward artifact:
-
-- `checkpoint-summary.md`
-
-The next round should prefer `checkpoint-summary.md` as carry-forward context before falling back to a full prior `decision.md` or `handoff.json`.
-
-## Failure classification
-
-Use exactly one:
-
-- `workflow bug`: orchestration logic, artifact layout, CLI, validation, persistence
-- `agent behavior issue`: output quality or format drift despite correct workflow prompts/contracts
-- `environment issue`: missing binaries, permissions, filesystem, PATH, runtime access
-- `sample-spec issue`: the spec itself, or sample-side/product-side gaps that should not be fixed in this workflow milestone
-
-## Minimum task contract for complex work
-
-Complex bugfix and feature specs must explicitly provide:
-
-- `Goal`
-- `In scope`
-- `Out of scope`
-- `Validation commands`
-- `Expected artifacts`
-
-If any of these are missing or left as placeholders, the packaged skill refuses to start the sprint.
-
-## Execution scope limits
-
-Complex specs may define:
-
-- `maxFiles`
-- `maxChecks`
-- `maxDeliverables`
-
-The producer should declare `PLANNED_FILES`, `PLANNED_CHECKS`, and `DELIVERABLES` in the worklog before editing code. If one round would exceed scope, narrow the round or continue in a later round instead of forcing a large change through one execution.
-
-## Synchronization rule
-
-Source of truth remains:
-
-- the repository copy at `packages/openclaw-plugin/templates/langs/zh/skills/ai-sprint-orchestration`
-
-Sync the packaged copy only when the change affects:
-
-- package-local CLI behavior
-- validation behavior
-- artifact layout
-- package-local references or runtime assumptions
-
-Do not blindly mirror every upstream orchestrator edit into this package.
-
-## Current work-unit direction
-
-This package now supports a finer-grained `work-unit` layer to force tighter context boundaries between bounded units:
-
-- `workUnitId`
-- `workUnitGoal`
-- `allowedFiles`
-- `unitChecks`
-- `unitDeliverables`
-- `unitSummary`
-- `carryForwardSummary`
-
-Continuation should prefer the shorter `carryForwardSummary` before falling back to a full prior decision or handoff. The goal is to minimize cross-unit context while preserving the smallest necessary state for the next unit.