mancode 0.3.13 → 0.3.15

package/README.en.md

@@ -17,7 +17,7 @@
 <p align="center">
   <a href="./LICENSE"><img src="https://img.shields.io/badge/License-AGPL--3.0-blue.svg?style=flat-square" alt="License: AGPL-3.0" /></a>
   <a href="https://www.npmjs.com/package/mancode"><img src="https://img.shields.io/npm/v/mancode?style=flat-square" alt="npm version" /></a>
-  <img src="https://img.shields.io/badge/status-stable%20v0.3.13-green?style=flat-square" alt="Status: stable v0.3.13" />
+  <img src="https://img.shields.io/badge/status-Continuity%20v0.3.15-2f855a?style=flat-square" alt="Status: mancode Continuity v0.3.15" />
   <img src="https://img.shields.io/badge/platforms-Claude%20Code%20%7C%20Cursor%20%7C%20Codex%20%7C%20Copilot%20%7C%20ZCode-5865F2?style=flat-square" alt="Platforms: Claude Code, Cursor, Codex in ChatGPT desktop and CLI, GitHub Copilot, ZCode" />
 </p>
 
@@ -34,6 +34,9 @@ different gears for different stakes: light solo mode for daily practice, `/man`
 for playoff-level engineering discipline, and coaching-staff subagents for
 research, planning, implementation, and review.
 
+**mancode Continuity** is the continuous-context runtime that carries tasks,
+decisions, and verification evidence safely into later conversations.
+
 [Installation](#installation) · [Usage](#usage)
 
 mancode ships with adapters for Claude Code, Cursor, Codex in the ChatGPT
@@ -102,7 +105,7 @@ explicitly resumes the existing TaskRef, preserving continuity without treating
 one window's temporary state as another window's identity.
 
 ```bash
-mancode status --json
+mancode status --brief --json
 mancode context session new --client claude-code
 mancode context resume <namespace:ULID> --session <id> --client claude-code
 mancode context show --purpose orient --session <id> --client claude-code
@@ -177,7 +180,7 @@ the original mode entries, never task/session snapshots. `mancode init
   default `solo` for lightweight implementation, or continue the full `/man`
   validation and bounded risk-review workflow.
 - **Keep workflow artifacts on disk**: save research, plans, review reports,
-  and summaries under `.mancode/local/workflows/<taskId>/`.
+  and summaries under `.mancode/<namespace>/workflows/<ULID>/`.
 - **Support team context**: use `/manteam` with confirmed typed entities under
   `.mancode/shared/`.
 - **Scan project health**: use `mancode manps` to detect stale TODOs, unused
@@ -263,7 +266,7 @@ Context Pack:
 work. A planning or research request made from default `solo` routes into `/man`.
 It inspects the project, asks only questions that can change scope, architecture,
 cost, or acceptance, and recommends 2–3 options when a decision benefits from
-guidance. It writes the plan under `.mancode/local/workflows/<taskId>/` only
+guidance. It writes the plan under `.mancode/local/workflows/<ULID>/` only
 after the requirements are ready.
 
 Finishing the plan does not automatically start the full workflow. At the plan
@@ -350,9 +353,8 @@ it should behave, and why previous decisions were made.
 
 ## Installation
 
-**Status**: stable v0.3.13. Claude Code, Cursor, Codex in the ChatGPT desktop app
-and CLI, and GitHub Copilot are supported. ZCode adapter support is included,
-with project skill discovery kept behind a verification gate before release.
+**Status**: mancode Continuity v0.3.15. Claude Code, Cursor, Codex in the ChatGPT
+desktop app and CLI, GitHub Copilot, and ZCode adapters are included.
 
 Requires Node.js 20 or newer. macOS, Linux, Windows CMD, PowerShell, and Git Bash
 are supported. Git is optional: without it, initialization continues with solo
@@ -421,11 +423,14 @@ mancode init
 mancode init --legacy
 mancode status
 mancode status --json
+mancode status --brief --json
 mancode install <claude-code|cursor|codex|copilot|zcode>
 mancode list-platforms
 mancode team identity create --name "<name>"
 mancode context session new --client <platform>
 mancode workflow create <man|manba|manteam> "<task>" --session <id>
+mancode workflow list --json
+mancode workflow show <namespace:ULID> --json
 mancode context resume <local:ULID|shared:ULID> --session <id>
 mancode workflow requirements <namespace:ULID> finalize --file <requirements.json> --expected-revision <n> --session <id>
 mancode workflow plan <namespace:ULID> revise --file <plan.md> --expected-revision <n> --session <id>
@@ -447,7 +452,7 @@ mancode version
 Simplified output:
 
 ```text
-mancode v0.3.13
+mancode v0.3.15
 
 Project:     my-app
 Runtime:     ready
@@ -486,12 +491,15 @@ mancode init
 
 ### `mancode status`
 
-Shows activation, runtime binding, identity/session evidence, transport, and
-the physical readiness of each platform bootstrap and original mode entry.
+The default and full JSON views show activation, runtime binding,
+identity/session evidence, transport, and the physical readiness of each
+platform bootstrap and original mode entry. Coding agents should combine
+`--brief --json` to read only the compact Continuity runtime view.
 
 ```bash
 mancode status
 mancode status --json
+mancode status --brief --json
 ```
 
 ### `mancode workflow`
@@ -507,9 +515,11 @@ mancode context session new --client codex
 mancode workflow create man "refactor auth module" --session <id>
 mancode workflow requirements <local:ULID> finalize --file requirements.json --expected-revision <n> --session <id>
 mancode workflow plan <local:ULID> revise --file plan.md --expected-revision <n> --session <id>
+mancode workflow plan <local:ULID> confirm --plan-decision <plan_only|governed_execution> --expected-revision <n> --session <id>
 mancode workflow review <local:ULID> apply --file review-ledger.json --expected-revision <n> --session <id>
 mancode workflow verify <local:ULID> apply --file verification-ledger.json --expected-revision <n> --session <id>
 mancode workflow complete <local:ULID> --expected-revision <n> --session <id>
+mancode context compact --dry-run
 ```
 
 ### `mancode manps`
@@ -635,23 +645,34 @@ Ensure the `.cursor/rules/mancode-*.mdc` files exist. Rules with
 Mode-specific rules (manba, man, manteam, manps) trigger based on the
 description field — invoke them by asking for `/manba` or similar.
 
-### How to do a clean reinstall
+### How to reinstall Continuity adapters
 
 ```bash
-mancode uninstall --all --force
-mancode init
-mancode install <platform>
+mancode uninstall claude-code --force
+mancode uninstall cursor --force
+mancode uninstall codex --force
+mancode uninstall copilot --force
+mancode uninstall zcode --force
+mancode install claude-code
+mancode install cursor
+mancode install codex
+mancode install copilot
+mancode install zcode
 ```
 
-### How to completely remove mancode
+Continuity authority is protected, so `mancode uninstall --all` does not delete workflow
+authority. To inspect removable runtime records, run
+`mancode context compact --dry-run` first.
+
+### How to remove the CLI
 
 ```bash
-mancode uninstall --all --force
 npm uninstall -g mancode
 ```
 
-This removes `.mancode/`, platform config files, and mancode hooks from
-`.claude/settings.json`. User-authored rules and instructions are preserved.
+Uninstalling each platform removes its mancode bootstrap while preserving
+user-authored rules, instructions, and Continuity workflow data. The `--all` form is only
+supported for projects explicitly initialized with `mancode init --legacy`.
 
 ## FAQ
 

package/README.md

@@ -17,7 +17,7 @@
 <p align="center">
   <a href="./LICENSE"><img src="https://img.shields.io/badge/License-AGPL--3.0-blue.svg?style=flat-square" alt="许可证：AGPL-3.0" /></a>
   <a href="https://www.npmjs.com/package/mancode"><img src="https://img.shields.io/npm/v/mancode?style=flat-square" alt="npm 版本" /></a>
-  <img src="https://img.shields.io/badge/status-stable%20v0.3.13-green?style=flat-square" alt="状态：稳定版 v0.3.13" />
+  <img src="https://img.shields.io/badge/status-Continuity%20v0.3.15-2f855a?style=flat-square" alt="状态：mancode Continuity v0.3.15" />
   <img src="https://img.shields.io/badge/platforms-Claude%20Code%20%7C%20Cursor%20%7C%20Codex%20%7C%20Copilot%20%7C%20ZCode-5865F2?style=flat-square" alt="平台：Claude Code、Cursor、ChatGPT 桌面端 Codex、Codex CLI、GitHub Copilot、ZCode" />
 </p>
 
@@ -36,6 +36,8 @@
 日常任务用轻量 `solo`，关键任务用季后赛级别的 `/man`，复杂任务让教练组 subagents
 负责调研、计划、实现和审查。
 
+**mancode Continuity（连续上下文运行时）**负责把任务、决策和验证证据安全地带到后续对话。
+
 mancode 当前支持 Claude Code、Cursor、ChatGPT 桌面端中的 Codex、Codex CLI、
 GitHub Copilot 和 ZCode。每个平台继续使用原来的 `man*` 入口，并通过静态
 bootstrap 接入统一的 Context Pack 与 workflow authority。
@@ -92,7 +94,7 @@ mancode 把目标、需求、计划、检查结果和交接信息保存在稳定
 窗口的临时状态误当成另一个窗口的身份。
 
 ```bash
-mancode status --json
+mancode status --brief --json
 mancode context session new --client claude-code
 mancode context resume <namespace:ULID> --session <id> --client claude-code
 mancode context show --purpose orient --session <id> --client claude-code
@@ -155,7 +157,7 @@ AGENTS.md                        # Codex（ChatGPT 桌面端/CLI）：托管 ins
 - **在存在 UI 时匹配现有设计系统**：检查项目 UI 依赖、Tailwind 配置、CSS 变量和已有组件，让 agent 复用现有颜色、字体和交互模式。
 - **先把需求和计划对齐**：`/man` 会调研项目、引导澄清会改变方案的需求、推荐可行选项并生成可确认的持久计划；计划完成后不会自动进入完整实施。
 - **自由选择执行强度**：计划确认后，可只保留计划、交给默认 `solo` 轻量开发，或继续完整 `/man` 的验证与有界风险审查。
-- **保留工作流产物**：调研、计划、审查报告和总结会保存到 `.mancode/local/workflows/<taskId>/`。
+- **保留工作流产物**：调研、计划、审查报告和总结会保存到 `.mancode/<namespace>/workflows/<ULID>/`。
 - **支持团队上下文**：`/manteam` 通过 `.mancode/shared/` 的类型化实体共享已确认信息。
 - **扫描项目健康度**：`mancode manps` 检测陈旧 TODO、未使用依赖、风险依赖和硬编码设计值。
 
@@ -228,7 +230,7 @@ mancode 不把“当前模式”写进持久状态。需要某种工作方式时
 `solo`，当用户要求先调研、给方案或出计划时，也会进入 `/man`。它会先了解项目，
 只追问会改变范围、架构、成本或验收的问题；适合由系统推荐的决策会给出 2–3 个
 方案、优缺点和明确建议。需求足够清楚后，计划才会写入
-`.mancode/local/workflows/<taskId>/plan.md`。
+`.mancode/local/workflows/<ULID>/plan.md`。
 
 计划完成不会自动开始完整开发。用户在计划关卡选择：交给 `solo` 按已确认计划
 轻量开发、继续完整 `/man`、只保留计划，或修改计划。只有选择完整 `/man` 才继续
@@ -305,9 +307,8 @@ src/components/
 
 ## 安装
 
-**状态**：稳定版 v0.3.13。Claude Code、Cursor、ChatGPT 桌面端中的 Codex、
-Codex CLI 和 GitHub Copilot 均已支持。ZCode adapter 已接入，但项目级 skill
-发现路径在发布前仍作为验证门禁。
+**状态**：mancode Continuity v0.3.15。Claude Code、Cursor、ChatGPT 桌面端中的
+Codex、Codex CLI、GitHub Copilot 和 ZCode adapter 均已接入。
 
 需要 Node.js 20 或更高版本。原生支持 macOS、Linux、Windows CMD、
 PowerShell 和 Git Bash。Git 是可选依赖：未安装时仍可初始化，只会把团队
@@ -374,11 +375,14 @@ mancode init
 mancode init --legacy
 mancode status
 mancode status --json
+mancode status --brief --json
 mancode install <claude-code|cursor|codex|copilot|zcode>
 mancode list-platforms
 mancode team identity create --name "<name>"
 mancode context session new --client <platform>
 mancode workflow create <man|manba|manteam> "<task>" --session <id>
+mancode workflow list --json
+mancode workflow show <namespace:ULID> --json
 mancode context resume <local:ULID|shared:ULID> --session <id>
 mancode workflow requirements <namespace:ULID> finalize --file <requirements.json> --expected-revision <n> --session <id>
 mancode workflow plan <namespace:ULID> revise --file <plan.md> --expected-revision <n> --session <id>
@@ -400,7 +404,7 @@ mancode version
 以下是简化输出示例：
 
 ```text
-mancode v0.3.13
+mancode v0.3.15
 
 Project:     my-app
 Runtime:     ready
@@ -438,12 +442,14 @@ mancode init
 
 ### `mancode status`
 
-显示 activation、runtime binding、identity/session evidence、transport 和各平台
-bootstrap/原 mode 入口的实际就绪状态。
+默认输出和完整 JSON 显示 activation、runtime binding、identity/session evidence、
+transport 和各平台 bootstrap/原 mode 入口的实际就绪状态。编码 Agent 应组合使用
+`--brief --json`，只读取精简的 Continuity 运行时视图。
 
 ```bash
 mancode status
 mancode status --json
+mancode status --brief --json
 ```
 
 ### `mancode workflow`
@@ -458,9 +464,11 @@ mancode context session new --client codex
 mancode workflow create man "refactor auth module" --session <id>
 mancode workflow requirements <local:ULID> finalize --file requirements.json --expected-revision <n> --session <id>
 mancode workflow plan <local:ULID> revise --file plan.md --expected-revision <n> --session <id>
+mancode workflow plan <local:ULID> confirm --plan-decision <plan_only|governed_execution> --expected-revision <n> --session <id>
 mancode workflow review <local:ULID> apply --file review-ledger.json --expected-revision <n> --session <id>
 mancode workflow verify <local:ULID> apply --file verification-ledger.json --expected-revision <n> --session <id>
 mancode workflow complete <local:ULID> --expected-revision <n> --session <id>
+mancode context compact --dry-run
 ```
 
 ### `mancode manps`
@@ -575,23 +583,33 @@ mancode/
 （context、practice、solo）在每次对话加载。模式规则（manba、man、manteam、
 manps）按 description 触发——输入 `/manba` 等关键词即可激活。
 
-### 如何完全重装
+### 如何重装 Continuity 适配器
 
 ```bash
-mancode uninstall --all --force
-mancode init
-mancode install <platform>
+mancode uninstall claude-code --force
+mancode uninstall cursor --force
+mancode uninstall codex --force
+mancode uninstall copilot --force
+mancode uninstall zcode --force
+mancode install claude-code
+mancode install cursor
+mancode install codex
+mancode install copilot
+mancode install zcode
 ```
 
-### 如何完全卸载 mancode
+Continuity authority 受保护，`mancode uninstall --all` 不会删除工作流权威数据。需要
+清理运行时保留记录时，先用 `mancode context compact --dry-run` 检查候选。
+
+### 如何移除 CLI
 
 ```bash
-mancode uninstall --all --force
 npm uninstall -g mancode
 ```
 
-这会移除 `.mancode/`、平台配置文件和 `.claude/settings.json` 中的 mancode
-hooks。用户自定义的 rules 和 instructions 会被保留。
+逐个平台卸载会移除对应的 mancode bootstrap，并保留用户自定义 rules、instructions
+和 Continuity 工作流数据。旧项目若明确使用 `mancode init --legacy`，才支持 legacy 的
+`mancode uninstall --all --force`。
 
 ## 常见问题
 

package/dist/{chunk-O3QAKAPJ.js → chunk-LMXUPBCN.js}

@@ -6714,14 +6714,9 @@ var V3ContextStore = class {
       })
     };
   }
-  /**
-   * Lists non-terminal children from canonical metadata only. Callers that
-   * need a completion gate must hold the parent task lock while invoking it;
-   * V3 child creation takes that same parent lock before publishing.
-   */
-  async listActiveChildTaskRefs(parentTaskRef) {
-    const parent = parseTaskRefValue(parentTaskRef);
-    const children = [];
+  /** Lists every canonical V3 workflow without relying on a session pointer. */
+  async listWorkflowMetadata() {
+    const workflows = [];
     for (const namespace of ["local", "shared"]) {
       const directory = path9.join(".mancode", namespace, "workflows");
       const entries = await readDirectoryEntriesWithin(
@@ -6730,7 +6725,7 @@ var V3ContextStore = class {
       );
       for (const taskId of entries.sort(compareUtf83)) {
         try {
-          assertUlid(taskId, "workflow child directory");
+          assertUlid(taskId, "workflow directory");
         } catch {
           throw new Error("MANCODE_CONTEXT_COLLECTION_ENTRY_INVALID");
         }
@@ -6745,12 +6740,26 @@ var V3ContextStore = class {
           "metadata.json",
           parseWorkflowMetadata
         );
-        if (metadata.parent !== null && sameTaskRef(metadata.parent.taskRef, parent) && !isTerminalWorkflowStatus(metadata.status)) {
-          children.push(metadata.taskRef);
+        if (!sameTaskRef(metadata.taskRef, taskRef)) {
+          throw new Error("MANCODE_CONTEXT_TASK_LOCATION_MISMATCH");
         }
+        workflows.push(metadata);
       }
     }
-    return children.sort(
+    return workflows.sort(
+      (left, right) => Date.parse(right.updatedAt) - Date.parse(left.updatedAt) || compareUtf83(left.taskRef.namespace, right.taskRef.namespace) || compareUtf83(left.taskRef.taskId, right.taskRef.taskId)
+    );
+  }
+  /**
+   * Lists non-terminal children from canonical metadata only. Callers that
+   * need a completion gate must hold the parent task lock while invoking it;
+   * V3 child creation takes that same parent lock before publishing.
+   */
+  async listActiveChildTaskRefs(parentTaskRef) {
+    const parent = parseTaskRefValue(parentTaskRef);
+    return (await this.listWorkflowMetadata()).filter(
+      (metadata) => metadata.parent !== null && sameTaskRef(metadata.parent.taskRef, parent) && !isTerminalWorkflowStatus(metadata.status)
+    ).map((metadata) => metadata.taskRef).sort(
       (left, right) => compareUtf83(left.namespace, right.namespace) || compareUtf83(left.taskId, right.taskId)
     );
   }
@@ -7114,4 +7123,4 @@ export {
   V3ContextStore,
   storedTaskAggregateDigest
 };
-//# sourceMappingURL=chunk-O3QAKAPJ.js.map
+//# sourceMappingURL=chunk-LMXUPBCN.js.map