@ai-content-space/loopx 0.1.9 → 0.1.10

package/README.md

@@ -228,11 +228,14 @@ Main artifacts:
 - `.loopx/workflows/<slug>/development-plan.md`
 - `.loopx/workflows/<slug>/test-plan.md`
 - `.loopx/workflows/<slug>/requirement-traceability.md`
+- `.loopx/workflows/<slug>/plan-delegation-decision.md`
 
 After a successful plan run, loopx also writes derived reading views at `.loopx/workflows/<slug>/view/index.html`, `.loopx/workflows/<slug>/view/plan.html`, and `.loopx/views/index.html`. Use these for human review; keep Markdown and JSON as the editable sources of truth.
 
 `requirement-traceability.md` maps the original source requirements or PRD to the generated plan package, change delta, vertical slices, and tests. If explicit source coverage items or source requirement tables are not covered by the plan package, `plan` stays blocked before build approval.
 
+`plan-delegation-decision.md` records whether planning should stay local or use stronger critic/parallel-review depth. The decision uses risk, scope, state/data integrity, verification complexity, and architecture tradeoffs as triggers; missing delegation rationale blocks build handoff.
+
 `spec-delta.md` uses requirement deltas: `## ADDED Requirements`, `## MODIFIED Requirements`, `## REMOVED Requirements`, and `## RENAMED Requirements`. ADDED and MODIFIED entries are full `### Requirement:` blocks with SHALL/MUST language and `#### Scenario:` examples, so archive can merge them into the current long-lived spec state.
 
 ### build
@@ -386,6 +389,7 @@ Documents users normally need to watch:
 - `.loopx/workflows/<slug>/spec.md`: the current requirement working copy.
 - `.loopx/workflows/<slug>/plan.md`, `architecture.md`, `development-plan.md`, and `test-plan.md`: the current task's plan, architecture, execution, and verification contract.
 - `.loopx/workflows/<slug>/requirement-traceability.md`: original requirement coverage gate used by plan, build, and review.
+- `.loopx/workflows/<slug>/plan-delegation-decision.md`: recorded local/critic/parallel-review planning delegation rationale.
 - `.loopx/workflows/<slug>/execution-record.md` and `review-report.md`: execution evidence and review result.
 - `.loopx/views/index.html` and `.loopx/workflows/<slug>/view/index.html`: reading entrypoints written after `plan` and regenerated by `loopx render`.
 
@@ -522,4 +526,4 @@ node src/cli.mjs status --json
 
 ## Version
 
-Current npm package version: `0.1.9`.
+Current npm package version: `0.1.10`.

package/README.zh-CN.md

@@ -230,11 +230,14 @@ node scripts/verify-skills.mjs
 - `.loopx/workflows/<slug>/development-plan.md`
 - `.loopx/workflows/<slug>/test-plan.md`
 - `.loopx/workflows/<slug>/requirement-traceability.md`
+- `.loopx/workflows/<slug>/plan-delegation-decision.md`
 
 plan 成功后，loopx 还会写入派生阅读视图：`.loopx/workflows/<slug>/view/index.html`、`.loopx/workflows/<slug>/view/plan.html` 和 `.loopx/views/index.html`。这些视图用于人工审阅；Markdown 和 JSON 仍然是可编辑事实源。
 
 `requirement-traceability.md` 会把原始需求或 PRD 映射到生成的 plan package、change delta、vertical slices 和测试。若显式需求覆盖项或需求表格项没有被计划包覆盖，`plan` 会在 build approval 前保持 blocked。
 
+`plan-delegation-decision.md` 会记录规划阶段应保持本地顺序审阅，还是需要更强的 critic/parallel-review 深度。决策依据包括风险、范围、状态/数据完整性、验证复杂度和架构取舍；缺少委派依据会阻塞 build handoff。
+
 `spec-delta.md` 使用 requirement delta：`## ADDED Requirements`、`## MODIFIED Requirements`、`## REMOVED Requirements` 和 `## RENAMED Requirements`。ADDED / MODIFIED 必须是完整的 `### Requirement:` 块，包含 SHALL/MUST 约束和 `#### Scenario:` 场景，archive 才能把它们合并进长期 spec 当前状态。
 
 ### build
@@ -397,6 +400,7 @@ loopx 在当前项目下写入 `.loopx/`：
 - `.loopx/workflows/<slug>/spec.md`：当前需求工作副本。
 - `.loopx/workflows/<slug>/plan.md`、`architecture.md`、`development-plan.md`、`test-plan.md`：当前任务的计划、架构和验证约定。
 - `.loopx/workflows/<slug>/requirement-traceability.md`：plan、build、review 都会消费的原始需求覆盖门禁。
+- `.loopx/workflows/<slug>/plan-delegation-decision.md`：记录 local / critic-only / parallel-review 规划委派依据。
 - `.loopx/workflows/<slug>/execution-record.md`、`review-report.md`：执行证据和评审结论。
 - `.loopx/views/index.html` 与 `.loopx/workflows/<slug>/view/index.html`：plan 后写入、也可由 `loopx render` 重新生成的阅读入口。
 
@@ -533,4 +537,4 @@ node src/cli.mjs status --json
 
 ## 版本
 
-当前 npm 包版本：`0.1.9`。
+当前 npm 包版本：`0.1.10`。

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@ai-content-space/loopx",
   "type": "module",
-  "version": "0.1.9",
+  "version": "0.1.10",
   "description": "Skill-first loopx workflow product for Codex",
   "repository": {
     "type": "git",

package/plugins/loopx/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "loopx",
-  "version": "0.1.9",
+  "version": "0.1.10",
   "description": "Skill-first loopx workflow product for Codex",
   "skills": "./skills/",
   "interface": {

package/plugins/loopx/skills/archive/SKILL.md

@@ -3,7 +3,7 @@ name: archive
 description: "Archives an approved loopx change delta into long-lived specs and writes an ADR candidate after done approval. Not for active builds or unapproved reviews."
 when_to_use: "archive, done workflow, spec delta, long-lived specs, ADR candidate, review approved, 归档, 同步规格"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 argument-hint: "<workflow slug>"
 ---
 

package/plugins/loopx/skills/autopilot/SKILL.md

@@ -3,7 +3,7 @@ name: autopilot
 description: "Runs one bounded autonomous loopx orchestration over clarify, plan, build, and review while preserving canonical artifacts. Not for manual gate-by-gate control."
 when_to_use: "autopilot, autonomous loopx run, end-to-end workflow, run all stages, bounded orchestration, 自动执行, 全流程"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 argument-hint: "<workflow slug>"
 ---
 

package/plugins/loopx/skills/build/SKILL.md

@@ -3,7 +3,7 @@ name: build
 description: "Executes an approved loopx plan or review rework contract with evidence, verification, deslop, and regression gates. Not for unclear requirements or independent review."
 when_to_use: "build, implement approved plan, execute PRD, --from-review, review rework, implementation fixes, 执行, 实现, 修改"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 argument-hint: "[--no-deslop] <approved PRD path or workflow slug> | --from-review <review artifact path>"
 ---
 

package/plugins/loopx/skills/clarify/SKILL.md

@@ -3,7 +3,7 @@ name: clarify
 description: "Clarifies ambiguous loopx work into requirements, non-goals, decision boundaries, and design-ready specs before planning. Not for already-approved plans or concrete implementation tasks."
 when_to_use: "clarify, requirements, ambiguous request, unclear scope, non-goals, decision boundaries, acceptance criteria, 需求澄清, 范围不清"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # loopx Clarify

package/plugins/loopx/skills/debug/SKILL.md

@@ -3,7 +3,7 @@ name: debug
 description: "Finds root cause for bugs, failing tests, build failures, regressions, and unexpected behavior before fixes. Not for new feature planning or routine code review."
 when_to_use: "debug, bug, test failure, build failure, regression, unexpected behavior, root cause, 报错, 失败, 回归, 排查"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # Systematic Debugging

package/plugins/loopx/skills/go-style/SKILL.md

@@ -3,7 +3,7 @@ name: go-style
 description: "Applies loopx Go coding style for .go edits, tests, errors, context, naming, and interface boundaries. Not for non-Go code or Kratos-specific architecture by itself."
 when_to_use: "go-style, Go, golang, .go files, go tests, gofmt, idiomatic Go, Go style, Go 代码"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # Go Style

package/plugins/loopx/skills/kratos/SKILL.md

@@ -3,7 +3,7 @@ name: kratos
 description: "Supports Go-Kratos microservices, proto/buf APIs, service/biz/data layers, middleware, auth, config, and troubleshooting. Not for generic Go style alone."
 when_to_use: "kratos, Go-Kratos, proto, buf, service layer, biz layer, data layer, middleware, auth, config, Kratos 微服务"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # Kratos

package/plugins/loopx/skills/plan/SKILL.md

@@ -3,7 +3,7 @@ name: plan
 description: "Creates a consensus-first loopx plan package with Planner, Architect, and Critic review from an approved spec. Not for unresolved requirements or direct implementation."
 when_to_use: "plan, planning, consensus planning, PRD, architecture plan, test plan, approved clarify spec, 规划, 方案, 架构评审"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 argument-hint: "[--interactive] [--deliberate] [--direct <spec-path>] <clarified task or spec path>"
 ---
 
@@ -34,6 +34,7 @@ By default, `plan` includes the full consensus review loop formerly documented u
 - Keep planning artifact-bound: produce PRD, architecture, development plan, and test plan outputs.
 - Preserve accepted intent as durable change artifacts: proposal, spec delta, design, tasks, and artifact dependency graph.
 - Separate planning approval from execution approval.
+- Treat human review as a first-class product surface: planning Markdown and HTML views must be readable enough for a reviewer to approve or reject without opening runtime state JSON.
 - Do not start implementation from `plan`.
 - Prefer a smaller executable plan over a broad plan that cannot be verified.
 - Preserve non-goals, decision boundaries, and residual-risk warnings from clarify.
@@ -165,6 +166,7 @@ On approval, write canonical planning artifacts:
 - `.loopx/workflows/<slug>/development-plan.md`
 - `.loopx/workflows/<slug>/test-plan.md`
 - `.loopx/workflows/<slug>/requirement-traceability.md`
+- `.loopx/workflows/<slug>/plan-delegation-decision.md`
 - `.loopx/plans/prd-<slug>.md`
 - `.loopx/plans/test-spec-<slug>.md`
 - `.loopx/changes/active/<change-id>/proposal.md`
@@ -184,7 +186,10 @@ The HTML files are derived reading views for human plan review. They are not can
 
 The final plan must include:
 
+- Chinese reviewer-facing Markdown for `plan.md`, `architecture.md`, `development-plan.md`, `test-plan.md`, canonical PRD/test spec, traceability, and delegation decision; English prose is allowed only for code paths, API names, commands, enum values, and source terms
+- an HTML reading view that exposes stage status, human approval points, blockers, source coverage, and artifact summaries before the full Markdown bodies
 - a source-requirement coverage matrix that maps the original requirements/PRD to plan, architecture, slices, spec delta, and tests
+- a delegation decision with mode `local|critic-only|parallel-review`, score, triggers, and reason for whether subagent-style review is warranted
 - ADR: Decision, Drivers, Alternatives considered, Why chosen, Consequences, Follow-ups
 - concrete implementation steps sized to the actual task
 - target long-lived spec domains and an OpenSpec-style requirements delta for archive
@@ -247,11 +252,15 @@ HTML:
 - `plan_execution_inputs_resolved`: `true|false`
 - `source_requirements_status`: `complete|partial`
 - `requirement_traceability_path`: `.loopx/workflows/<slug>/requirement-traceability.md`
+- `plan_delegation_mode`: `local|critic-only|parallel-review`
+- `plan_delegation_decision_path`: `.loopx/workflows/<slug>/plan-delegation-decision.md`
 - `requested_transition`: remains explicit before build/autopilot
 
 The plan gate is blocked until:
 
 - plan package artifacts exist
+- Planner, Architect, and Critic evidence artifacts exist
+- reviewer-facing planning docs and derived canonical PRD/test spec are Chinese-readable
 - change proposal, spec delta, design, tasks, vertical slices, and artifact graph exist
 - spec delta declares target domains and `## ADDED|MODIFIED|REMOVED|RENAMED Requirements` blocks
 - every ADDED or MODIFIED requirement uses `### Requirement:`, contains SHALL or MUST text, and includes at least one `#### Scenario:`
@@ -262,6 +271,7 @@ The plan gate is blocked until:
 - verification steps are concrete
 - execution inputs are fully mapped to concrete sources
 - source requirements are covered by `requirement-traceability.md`; uncovered original PRD requirements block build handoff
+- delegation decision is recorded in `plan-delegation-decision.md`; absence of an explicit local/critic/parallel-review rationale blocks build handoff
 - user approval exists for any execution transition
 </Runtime_State_Machine>
 
@@ -279,6 +289,7 @@ Primary outputs:
 
 - approved plan package under `.loopx/workflows/<slug>/`
 - original source requirements and traceability matrix under `.loopx/workflows/<slug>/requirement-traceability.md`
+- delegation decision under `.loopx/workflows/<slug>/plan-delegation-decision.md`
 - canonical PRD and test spec under `.loopx/plans/`
 - change artifacts under `.loopx/changes/active/<change-id>/`
 - derived HTML reading views under `.loopx/workflows/<slug>/view/` and `.loopx/views/`

package/plugins/loopx/skills/review/SKILL.md

@@ -3,7 +3,7 @@ name: review
 description: "Reviews a loopx build execution record for acceptance, code risks, evidence quality, and architecture smells. Not for doing implementation work or replanning."
 when_to_use: "review, code review, acceptance, go no-go, execution-record, architecture smell, build complete, 审查, 验收"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 argument-hint: "<execution-record path or workflow slug>"
 ---
 

package/plugins/loopx/skills/tdd/SKILL.md

@@ -3,7 +3,7 @@ name: tdd
 description: "Guides feature and bugfix implementation through a failing test before production code and red-green-refactor discipline. Not for generated files or throwaway prototypes."
 when_to_use: "tdd, failing test first, feature implementation, bugfix, regression test, red green refactor, 测试先行"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # Test-Driven Development (TDD)

package/plugins/loopx/skills/verify/SKILL.md

@@ -3,7 +3,7 @@ name: verify
 description: "Requires fresh verification evidence before claiming work is complete, fixed, passing, review-ready, or ready to commit. Not for speculative confidence or stale results."
 when_to_use: "verify, completion claim, fixed claim, tests pass, review-ready, commit, fresh evidence, 验证, 完成前检查"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # Verification Before Completion

package/skills/archive/SKILL.md

@@ -3,7 +3,7 @@ name: archive
 description: "Archives an approved loopx change delta into long-lived specs and writes an ADR candidate after done approval. Not for active builds or unapproved reviews."
 when_to_use: "archive, done workflow, spec delta, long-lived specs, ADR candidate, review approved, 归档, 同步规格"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 argument-hint: "<workflow slug>"
 ---
 

package/skills/autopilot/SKILL.md

@@ -3,7 +3,7 @@ name: autopilot
 description: "Runs one bounded autonomous loopx orchestration over clarify, plan, build, and review while preserving canonical artifacts. Not for manual gate-by-gate control."
 when_to_use: "autopilot, autonomous loopx run, end-to-end workflow, run all stages, bounded orchestration, 自动执行, 全流程"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 argument-hint: "<workflow slug>"
 ---
 

package/skills/build/SKILL.md

@@ -3,7 +3,7 @@ name: build
 description: "Executes an approved loopx plan or review rework contract with evidence, verification, deslop, and regression gates. Not for unclear requirements or independent review."
 when_to_use: "build, implement approved plan, execute PRD, --from-review, review rework, implementation fixes, 执行, 实现, 修改"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 argument-hint: "[--no-deslop] <approved PRD path or workflow slug> | --from-review <review artifact path>"
 ---
 

package/skills/clarify/SKILL.md

@@ -3,7 +3,7 @@ name: clarify
 description: "Clarifies ambiguous loopx work into requirements, non-goals, decision boundaries, and design-ready specs before planning. Not for already-approved plans or concrete implementation tasks."
 when_to_use: "clarify, requirements, ambiguous request, unclear scope, non-goals, decision boundaries, acceptance criteria, 需求澄清, 范围不清"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # loopx Clarify

package/skills/debug/SKILL.md

@@ -3,7 +3,7 @@ name: debug
 description: "Finds root cause for bugs, failing tests, build failures, regressions, and unexpected behavior before fixes. Not for new feature planning or routine code review."
 when_to_use: "debug, bug, test failure, build failure, regression, unexpected behavior, root cause, 报错, 失败, 回归, 排查"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # Systematic Debugging

package/skills/go-style/SKILL.md

@@ -3,7 +3,7 @@ name: go-style
 description: "Applies loopx Go coding style for .go edits, tests, errors, context, naming, and interface boundaries. Not for non-Go code or Kratos-specific architecture by itself."
 when_to_use: "go-style, Go, golang, .go files, go tests, gofmt, idiomatic Go, Go style, Go 代码"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # Go Style

package/skills/kratos/SKILL.md

@@ -3,7 +3,7 @@ name: kratos
 description: "Supports Go-Kratos microservices, proto/buf APIs, service/biz/data layers, middleware, auth, config, and troubleshooting. Not for generic Go style alone."
 when_to_use: "kratos, Go-Kratos, proto, buf, service layer, biz layer, data layer, middleware, auth, config, Kratos 微服务"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # Kratos

package/skills/plan/SKILL.md

@@ -3,7 +3,7 @@ name: plan
 description: "Creates a consensus-first loopx plan package with Planner, Architect, and Critic review from an approved spec. Not for unresolved requirements or direct implementation."
 when_to_use: "plan, planning, consensus planning, PRD, architecture plan, test plan, approved clarify spec, 规划, 方案, 架构评审"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 argument-hint: "[--interactive] [--deliberate] [--direct <spec-path>] <clarified task or spec path>"
 ---
 
@@ -34,6 +34,7 @@ By default, `plan` includes the full consensus review loop formerly documented u
 - Keep planning artifact-bound: produce PRD, architecture, development plan, and test plan outputs.
 - Preserve accepted intent as durable change artifacts: proposal, spec delta, design, tasks, and artifact dependency graph.
 - Separate planning approval from execution approval.
+- Treat human review as a first-class product surface: planning Markdown and HTML views must be readable enough for a reviewer to approve or reject without opening runtime state JSON.
 - Do not start implementation from `plan`.
 - Prefer a smaller executable plan over a broad plan that cannot be verified.
 - Preserve non-goals, decision boundaries, and residual-risk warnings from clarify.
@@ -165,6 +166,7 @@ On approval, write canonical planning artifacts:
 - `.loopx/workflows/<slug>/development-plan.md`
 - `.loopx/workflows/<slug>/test-plan.md`
 - `.loopx/workflows/<slug>/requirement-traceability.md`
+- `.loopx/workflows/<slug>/plan-delegation-decision.md`
 - `.loopx/plans/prd-<slug>.md`
 - `.loopx/plans/test-spec-<slug>.md`
 - `.loopx/changes/active/<change-id>/proposal.md`
@@ -184,7 +186,10 @@ The HTML files are derived reading views for human plan review. They are not can
 
 The final plan must include:
 
+- Chinese reviewer-facing Markdown for `plan.md`, `architecture.md`, `development-plan.md`, `test-plan.md`, canonical PRD/test spec, traceability, and delegation decision; English prose is allowed only for code paths, API names, commands, enum values, and source terms
+- an HTML reading view that exposes stage status, human approval points, blockers, source coverage, and artifact summaries before the full Markdown bodies
 - a source-requirement coverage matrix that maps the original requirements/PRD to plan, architecture, slices, spec delta, and tests
+- a delegation decision with mode `local|critic-only|parallel-review`, score, triggers, and reason for whether subagent-style review is warranted
 - ADR: Decision, Drivers, Alternatives considered, Why chosen, Consequences, Follow-ups
 - concrete implementation steps sized to the actual task
 - target long-lived spec domains and an OpenSpec-style requirements delta for archive
@@ -247,11 +252,15 @@ HTML:
 - `plan_execution_inputs_resolved`: `true|false`
 - `source_requirements_status`: `complete|partial`
 - `requirement_traceability_path`: `.loopx/workflows/<slug>/requirement-traceability.md`
+- `plan_delegation_mode`: `local|critic-only|parallel-review`
+- `plan_delegation_decision_path`: `.loopx/workflows/<slug>/plan-delegation-decision.md`
 - `requested_transition`: remains explicit before build/autopilot
 
 The plan gate is blocked until:
 
 - plan package artifacts exist
+- Planner, Architect, and Critic evidence artifacts exist
+- reviewer-facing planning docs and derived canonical PRD/test spec are Chinese-readable
 - change proposal, spec delta, design, tasks, vertical slices, and artifact graph exist
 - spec delta declares target domains and `## ADDED|MODIFIED|REMOVED|RENAMED Requirements` blocks
 - every ADDED or MODIFIED requirement uses `### Requirement:`, contains SHALL or MUST text, and includes at least one `#### Scenario:`
@@ -262,6 +271,7 @@ The plan gate is blocked until:
 - verification steps are concrete
 - execution inputs are fully mapped to concrete sources
 - source requirements are covered by `requirement-traceability.md`; uncovered original PRD requirements block build handoff
+- delegation decision is recorded in `plan-delegation-decision.md`; absence of an explicit local/critic/parallel-review rationale blocks build handoff
 - user approval exists for any execution transition
 </Runtime_State_Machine>
 
@@ -279,6 +289,7 @@ Primary outputs:
 
 - approved plan package under `.loopx/workflows/<slug>/`
 - original source requirements and traceability matrix under `.loopx/workflows/<slug>/requirement-traceability.md`
+- delegation decision under `.loopx/workflows/<slug>/plan-delegation-decision.md`
 - canonical PRD and test spec under `.loopx/plans/`
 - change artifacts under `.loopx/changes/active/<change-id>/`
 - derived HTML reading views under `.loopx/workflows/<slug>/view/` and `.loopx/views/`

package/skills/review/SKILL.md

@@ -3,7 +3,7 @@ name: review
 description: "Reviews a loopx build execution record for acceptance, code risks, evidence quality, and architecture smells. Not for doing implementation work or replanning."
 when_to_use: "review, code review, acceptance, go no-go, execution-record, architecture smell, build complete, 审查, 验收"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 argument-hint: "<execution-record path or workflow slug>"
 ---
 

package/skills/tdd/SKILL.md

@@ -3,7 +3,7 @@ name: tdd
 description: "Guides feature and bugfix implementation through a failing test before production code and red-green-refactor discipline. Not for generated files or throwaway prototypes."
 when_to_use: "tdd, failing test first, feature implementation, bugfix, regression test, red green refactor, 测试先行"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # Test-Driven Development (TDD)

package/skills/verify/SKILL.md

@@ -3,7 +3,7 @@ name: verify
 description: "Requires fresh verification evidence before claiming work is complete, fixed, passing, review-ready, or ready to commit. Not for speculative confidence or stale results."
 when_to_use: "verify, completion claim, fixed claim, tests pass, review-ready, commit, fresh evidence, 验证, 完成前检查"
 metadata:
-  version: "0.1.9"
+  version: "0.1.10"
 ---
 
 # Verification Before Completion

package/src/cli.mjs

@@ -90,6 +90,8 @@ function printHumanStatus(status) {
     console.log(`plan_architect_review_status: ${status.state.plan_architect_review_status}`);
     console.log(`plan_critic_verdict: ${status.state.plan_critic_verdict}`);
     console.log(`plan_artifact_status: ${status.state.plan_docs_status}`);
+    console.log(`plan_delegation_mode: ${status.state.plan_delegation_mode ?? 'unknown'}`);
+    console.log(`plan_delegation_decision_path: ${status.state.plan_delegation_decision_path ?? '(none)'}`);
     console.log(`source_requirements_status: ${status.state.source_requirements_status ?? 'unknown'}`);
     console.log(`requirement_traceability_path: ${status.state.requirement_traceability_path ?? '(none)'}`);
     console.log(`plan_blockers: ${Array.isArray(status.state.plan_blockers) && status.state.plan_blockers.length > 0 ? status.state.plan_blockers.join(', ') : '(none)'}`);