@ai-content-space/loopx 0.1.8 → 0.1.9

package/README.md

@@ -522,4 +522,4 @@ node src/cli.mjs status --json
 
 ## Version
 
-Current npm package version: `0.1.8`.
+Current npm package version: `0.1.9`.

package/README.zh-CN.md

@@ -533,4 +533,4 @@ node src/cli.mjs status --json
 
 ## 版本
 
-当前 npm 包版本：`0.1.8`。
+当前 npm 包版本：`0.1.9`。

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@ai-content-space/loopx",
   "type": "module",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "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.8",
+  "version": "0.1.9",
   "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.8"
+  version: "0.1.9"
 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.8"
+  version: "0.1.9"
 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.8"
+  version: "0.1.9"
 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.8"
+  version: "0.1.9"
 ---
 
 # 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.8"
+  version: "0.1.9"
 ---
 
 # 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.8"
+  version: "0.1.9"
 ---
 
 # 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.8"
+  version: "0.1.9"
 ---
 
 # 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.8"
+  version: "0.1.9"
 argument-hint: "[--interactive] [--deliberate] [--direct <spec-path>] <clarified task or spec path>"
 ---
 

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.8"
+  version: "0.1.9"
 argument-hint: "<execution-record path or workflow slug>"
 ---
 
@@ -101,13 +101,16 @@ For approval:
 
 ```text
 Next:
-loopx approve <slug> --from review --to done
+$archive <slug>
 ```
 
-After the workflow reaches `done`, run:
+`$archive` consumes the pending `review -> done` completion transition before syncing specs. Do not ask the user to run a separate `loopx approve <slug> --from review --to done` command in the normal Codex-facing flow.
 
-```text
-$archive <slug>
+For CLI/runtime debugging only, the equivalent explicit sequence is:
+
+```bash
+loopx approve <slug> --from review --to done
+loopx archive <slug>
 ```
 
 This syncs the approved `.loopx/changes/active/<change-id>/spec-delta.md` into long-lived `.loopx/specs/` files and moves the change folder under `.loopx/changes/archive/<change-id>/`.

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.8"
+  version: "0.1.9"
 ---
 
 # 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.8"
+  version: "0.1.9"
 ---
 
 # Verification Before Completion

package/scripts/codex-workflow-hook.mjs

@@ -40,6 +40,13 @@ function nextSkill(state) {
     && state.archive_status !== 'archived') {
     return `$archive ${state.slug}`;
   }
+  if (state.current_stage === 'review'
+    && state.review_verdict === 'approve'
+    && state.pending_user_decision === 'review->done'
+    && ['requested', 'approved'].includes(state.approval?.complete)
+    && state.archive_status !== 'archived') {
+    return `$archive ${state.slug}`;
+  }
   if (state.stage_status === 'awaiting-approval'
     && state.current_stage === 'plan'
     && Array.isArray(state.plan_blockers)
@@ -84,9 +91,6 @@ function nextSkill(state) {
     && state.approval?.rollback === 'approved') {
     return `$clarify ${state.slug}`;
   }
-  if (state.current_stage === 'review' && state.review_verdict === 'approve' && state.pending_user_decision === 'review->done') {
-    return `loopx approve ${state.slug} --from review --to done`;
-  }
   return null;
 }
 

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.8"
+  version: "0.1.9"
 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.8"
+  version: "0.1.9"
 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.8"
+  version: "0.1.9"
 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.8"
+  version: "0.1.9"
 ---
 
 # 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.8"
+  version: "0.1.9"
 ---
 
 # 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.8"
+  version: "0.1.9"
 ---
 
 # 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.8"
+  version: "0.1.9"
 ---
 
 # 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.8"
+  version: "0.1.9"
 argument-hint: "[--interactive] [--deliberate] [--direct <spec-path>] <clarified task or spec path>"
 ---
 

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.8"
+  version: "0.1.9"
 argument-hint: "<execution-record path or workflow slug>"
 ---
 
@@ -101,13 +101,16 @@ For approval:
 
 ```text
 Next:
-loopx approve <slug> --from review --to done
+$archive <slug>
 ```
 
-After the workflow reaches `done`, run:
+`$archive` consumes the pending `review -> done` completion transition before syncing specs. Do not ask the user to run a separate `loopx approve <slug> --from review --to done` command in the normal Codex-facing flow.
 
-```text
-$archive <slug>
+For CLI/runtime debugging only, the equivalent explicit sequence is:
+
+```bash
+loopx approve <slug> --from review --to done
+loopx archive <slug>
 ```
 
 This syncs the approved `.loopx/changes/active/<change-id>/spec-delta.md` into long-lived `.loopx/specs/` files and moves the change folder under `.loopx/changes/archive/<change-id>/`.

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.8"
+  version: "0.1.9"
 ---
 
 # 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.8"
+  version: "0.1.9"
 ---
 
 # Verification Before Completion

package/src/next-skill.mjs

@@ -19,6 +19,13 @@ export function nextSkillCommand(state) {
     && state.archive_status !== 'archived') {
     return `$archive ${state.slug}`;
   }
+  if (state.current_stage === 'review'
+    && state.review_verdict === 'approve'
+    && state.pending_user_decision === 'review->done'
+    && ['requested', 'approved'].includes(state.approval?.complete)
+    && state.archive_status !== 'archived') {
+    return `$archive ${state.slug}`;
+  }
   if (state.stage_status !== 'awaiting-approval') {
     return null;
   }

package/src/workflow.mjs

@@ -2248,7 +2248,7 @@ function buildCurrentEvidenceChain(state, readiness = buildReadiness(state), aut
     evidence.push(evidenceEntry(
       'review_approved',
       'Review verdict is approve.',
-      authorization.done.authorized ? 'The approved review -> done transition can be consumed.' : 'Completion still requires explicit review -> done authorization.',
+      authorization.done.authorized ? 'Archive can consume the approved review -> done transition before syncing specs.' : 'Completion still requires explicit review -> done authorization.',
     ));
   }
   if (state.archive_status === 'archived' && state.spec_sync_status === 'synced') {
@@ -2371,9 +2371,7 @@ function recommendedAction(state, legacy = false) {
         : 'Approve build -> review when execution-record.md is complete.';
     case STAGES.REVIEW:
       if (state.review_verdict === 'approve') {
-        return state.approval.complete === APPROVAL_STATES.APPROVED
-          ? 'Run loopx review again to consume the approved review -> done transition.'
-          : 'Approve review -> done to complete the workflow.';
+        return 'Run loopx archive; archive consumes the pending review -> done completion transition before syncing specs.';
       }
       if (state.review_verdict === 'request-changes') {
         if (state.requested_transition === TRANSITIONS.REVIEW_TO_BUILD && state.approval.build === APPROVAL_STATES.APPROVED) {
@@ -2574,7 +2572,11 @@ function nextCommandForRollbackTarget(slug, target) {
   if (target === 'none') {
     return [
       'Next:',
+      `$archive ${slug}`,
+      '',
+      'CLI-only equivalent:',
       `loopx approve ${slug} --from review --to done`,
+      `loopx archive ${slug}`,
     ].join('\n');
   }
   return [
@@ -2587,7 +2589,7 @@ function nextCommandForRollbackTarget(slug, target) {
 function reviewUserMessageZh({ slug, verdict, rollbackTarget, findings }) {
   const label = reviewVerdictLabel(verdict);
   const next = verdict === 'APPROVE'
-    ? `下一步：批准 review -> done 后完成工作流。\n${nextCommandForRollbackTarget(slug, 'none')}`
+    ? `下一步：直接归档；archive 会先消费 pending 的 review -> done 完成态。\n${nextCommandForRollbackTarget(slug, 'none')}`
     : `下一步：按审查发现处理，并${rollbackTargetLabel(rollbackTarget)}。\n${nextCommandForRollbackTarget(slug, rollbackTarget)}`;
   const findingText = Array.isArray(findings) && findings.length > 0 ? findings.join('；') : '无额外发现。';
   return `Review 结果：${slug} ${label}。审查发现：${findingText} ${next}`;
@@ -3929,7 +3931,7 @@ export async function reviewStage(cwd, slug, { reviewer = 'independent-reviewer'
         verdict: reviewInput.verdict,
         reviewMessageZh: reviewMessage,
         evidenceManifest: reviewInput.evidenceManifest,
-        followUps: ['等待 review -> done 审批。'],
+        followUps: ['执行 $archive；archive 会消费 pending 的 review -> done 完成态。'],
       });
     } catch (error) {
       journalWarning = error instanceof Error ? error.message : String(error);