mancode 0.3.12 → 0.3.13

package/README.en.md

@@ -17,10 +17,8 @@
 <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.12-green?style=flat-square" alt="Status: stable v0.3.12" />
-  <img src="https://img.shields.io/badge/V3-cross--CLI%20team%20Beta-FB6A21?style=flat-square" alt="V3: cross-CLI team Beta" />
+  <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/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" />
-  <img src="https://img.shields.io/badge/tests-passing-brightgreen?style=flat-square" alt="Tests passing" />
 </p>
 
 <p align="center">
@@ -39,17 +37,17 @@ research, planning, implementation, and review.
 [Installation](#installation) · [Usage](#usage)
 
 mancode ships with adapters for Claude Code, Cursor, Codex in the ChatGPT
-desktop app and CLI, GitHub Copilot, and ZCode. V3 keeps the original `man*`
+desktop app and CLI, GitHub Copilot, and ZCode. It keeps the original `man*`
 entries on every platform and connects them to one Context Pack and workflow
 authority through static bootstraps.
 
 mancode installs three things:
 
-1. **V3 authority** for explicit sessions, TaskRefs, Context Packs, workflows,
+1. **Workflow authority** for explicit sessions, TaskRefs, Context Packs, workflows,
    and team coordination.
 2. **Skills / modes** for `solo`, `/manba`, `/man`, `/manteam`, `/manps`, and
    `/mansolo`.
-3. **Platform bootstraps** that connect those original entries to V3; only
+3. **Platform bootstraps** that connect those original entries to mancode; only
    `--legacy` installs the old hooks.
 
 Use mancode when an AI coding agent writes too much code, ignores your existing
@@ -90,13 +88,36 @@ These are agent skills, not deprecated custom prompts. See the official
 [slash-command](https://learn.chatgpt.com/docs/reference/slash-commands) docs.
 Existing workflow metadata remains compatible and does not need migration.
 
-## V3 Cross-CLI and Team Beta
+## Continue Work Across Sessions
 
-V3 gives new team projects stable `TaskRef` context, isolated sessions,
-governance ledgers, worktree claims and handoffs, and optional git-ref
-coordination across clones. It is a **hard-gated Beta**: adapters bootstrap
-Claude Code, Cursor, Codex, GitHub Copilot, and ZCode, but platform files never
-become the authority for task or session state.
+mancode keeps goals, requirements, plans, validation results, and handoff notes
+under a stable `TaskRef`. When you open a new chat window, restart your coding
+agent, or continue from another supported CLI, the new session can resume the
+same task and load a purpose-specific Context Pack without depending on the old
+conversation remaining open.
+
+This resumes **task context**, not raw chat history. Sessions from different
+clients remain isolated. A new session uses its own client identity and
+explicitly resumes the existing TaskRef, preserving continuity without treating
+one window's temporary state as another window's identity.
+
+```bash
+mancode status --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
+```
+
+The original `/man`, `/manba`, and `/manteam` entries handle these steps. The
+CLI form above is useful for diagnostics, automation, or manual recovery.
+
+## Cross-Client and Team Collaboration
+
+mancode gives team projects stable TaskRefs, isolated sessions, governance
+ledgers, worktree claims and handoffs, and optional git-ref coordination across
+clones. Claude Code, Cursor, Codex, GitHub Copilot, and ZCode use the same
+workflow data through platform bootstraps; platform files do not hold task or
+session copies.
 
 For a new project, start with one platform you actually use:
 
@@ -107,38 +128,19 @@ mancode context session new --client claude-code
 mancode list-platforms
 ```
 
-Plain `mancode init` is now the V3 entry and still generates the original
-`man`, `manba`, `manteam`, `manps`, and `mansolo` host commands. No separate V3
-command name is required. `--v3` remains an explicit compatibility alias; use
+Plain `mancode init` generates the original `man`, `manba`, `manteam`, `manps`,
+and `mansolo` host commands. No separate command family is required. Use
 `mancode init --legacy` only when the old `state.json` architecture is required.
 
 Use the CLI for creation, resume, and coordination: `mancode workflow create`,
 `mancode context resume`, `mancode team claim`, and `mancode team handoff`. For
 an existing project, begin with `mancode migrate context --dry-run`, then follow
 its stage and activation report. Do not manually mix legacy `state.json` writes
-with V3 authority.
-
-### Beta validation boundary
-
-- The `main` branch requires a Windows gate that runs smoke tests in CMD,
-  PowerShell, and Git Bash.
-- `mancode context beta --release-candidate <commit> --json` checks activation,
-  adapters, repair state, worktree binding, and session evidence for all five
-  platforms. Evidence must bind to that immutable release candidate; any blocker
-  stops broad enablement.
-- Each platform must prove distinct sessions in two real host windows, child-command
-  propagation, and child-agent inheritance (or record a specific reason it is not
-  applicable). `context session spike` records an operator-attested real-host result;
-  it never infers propagation from a temporary environment variable. Stored evidence
-  never includes raw session keys.
-
-Until that gate passes, use an explicit `--session <id>` and do not treat host
-identity as verified. This lets you try V3 without presenting unproven
-cross-platform session behavior as a fact.
+with current workflow authority.
 
 ## What Gets Installed
 
-By default, `mancode init` creates V3 authority and platform integration files:
+By default, `mancode init` creates mancode workflow and platform integration files:
 
 ```text
 .mancode/
@@ -156,7 +158,7 @@ AGENTS.md                        # Codex (ChatGPT desktop/CLI): managed instruct
 .github/prompts/                 # GitHub Copilot: original mode prompts
 ```
 
-`.mancode/` separates shareable V3 authority from checkout-local sessions,
+`.mancode/` separates shareable workflow data from checkout-local sessions,
 workflows, and scan reports. Platform files contain only bootstrap guidance and
 the original mode entries, never task/session snapshots. `mancode init
 --legacy` creates the old `state.json` layout.
@@ -187,7 +189,7 @@ mancode is useful for:
 
 - Developers using AI coding agents on backend, web, mobile, desktop, CLI,
   library, data, or mixed projects
-- Users who want V3 Context Packs, skills, and explicit governance behind the original `man*` entries
+- Users who want Context Packs, skills, and explicit governance behind the original `man*` entries
 - Teams that want AI agents to reuse existing components and patterns
 - Projects that need a repeatable AI-assisted code review workflow
 - UI codebases with existing design conventions (when a UI is present)
@@ -242,8 +244,8 @@ The default workflow asks six questions before writing code:
 
 ## Usage
 
-V3 no longer persists a “current mode.” Invoke the original command for the
-kind of work you need; the entry resolves V3 status, session, TaskRef, and
+mancode does not persist a “current mode.” Invoke the original command for the
+kind of work you need; the entry resolves status, session, TaskRef, and
 Context Pack:
 
 | Mode | Best For | What It Does |
@@ -253,7 +255,7 @@ Context Pack:
 | `/man` | Work needing requirement alignment or a formal plan · playoffs | Research, recommendations, and a durable plan; then choose lightweight solo delivery or the full 9-step workflow |
 | `/manteam` | Team projects · five on the floor, one mind | Shared memory, decisions, coordination, and Conventional Commits |
 | `/manps` | Cleanup and maintenance · preseason | Project health scan with Markdown and JSON reports |
-| `/mansolo` | Returning to lightweight work | Writes no legacy mode; performs an explicit V3 handoff only when needed |
+| `/mansolo` | Returning to lightweight work | Writes no legacy mode; performs an explicit handoff only when needed |
 
 ## How `/man` Works: Playoffs Mode
 
@@ -286,10 +288,10 @@ decision was made later.
 
 ### Bootstrap and Adapters
 
-V3 assumes no hook approval. Each adapter installs a stable bootstrap plus the
-original `man/manba/manteam/manps/mansolo` entries; task, mode, and session
-authority stays in V3. Claude Code's internal bootstrap is hidden from users,
-so it does not add a public `/mancode-v3` command. Until real-host session
+mancode assumes no hook approval. Each adapter installs a stable bootstrap plus
+the original `man/manba/manteam/manps/mansolo` entries; task, mode, and session
+authority stays in mancode workflow data. Claude Code's internal bootstrap is
+hidden from users, so it does not add another public command. Until real-host session
 propagation is proven, mutations require an explicit `--session`.
 
 Only `mancode init --legacy` installs the old Claude hooks that read
@@ -297,7 +299,7 @@ Only `mancode init --legacy` installs the old Claude hooks that read
 
 ### Design Token Awareness
 
-V3 writes detected project facts to `.mancode/shared/context/project.json` and
+mancode writes detected project facts to `.mancode/shared/context/project.json` and
 keeps checkout-local design-token caches under `.mancode/local/cache/`. It can
 work with backend services, web applications, mobile apps, desktop apps, CLIs,
 libraries, and mixed repositories; it does not assume a JavaScript or UI stack.
@@ -333,7 +335,7 @@ Before writing new code, mancode pushes the agent through this priority order:
 
 ### Team Memory
 
-`/manteam` reads and updates confirmed entities in V3 shared authority:
+`/manteam` reads and updates confirmed entities in shared workflow data:
 
 ```text
 .mancode/shared/
@@ -348,7 +350,7 @@ it should behave, and why previous decisions were made.
 
 ## Installation
 
-**Status**: stable v0.3.12. Claude Code, Cursor, Codex in the ChatGPT desktop app
+**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.
 
@@ -368,7 +370,7 @@ mancode init --platform all
 
 Supported platforms:
 
-- Claude Code: hidden bootstrap plus original mode skills; V3 does not depend on hooks
+- Claude Code: hidden bootstrap plus original mode skills; the default setup does not depend on hooks
 - Cursor: `.cursor/rules/*.mdc` bootstrap plus original mode commands under `.cursor/commands/`
 - Codex (ChatGPT desktop app, CLI, and IDE extension): managed `AGENTS.md`
   block plus `$man*` repo skills under `.agents/skills/`
@@ -390,8 +392,8 @@ mancode init --platform PLATFORMS # One or more: claude-code,cursor,codex,copilo
 mancode init --empty      # Allow a safe empty directory in non-interactive scripts
 mancode init --lang zh-CN # Explicit initialization language (zh-CN or en)
 mancode refresh-project   # Refresh facts after Git or project files are added
-mancode install --force   # Repair or reinstall the selected V3 adapter
-mancode install --minimal # V3 is already bootstrap-only; retained for compatibility
+mancode install --force   # Repair or reinstall the selected adapter
+mancode install --minimal # The bootstrap is already minimal; retained for compatibility
 ```
 
 ## Agent Modes
@@ -442,19 +444,18 @@ mancode version
 
 ### `mancode status`
 
-Simplified V3 output:
+Simplified output:
 
 ```text
-mancode v0.3.12 (V3 authority)
+mancode v0.3.13
 
 Project:     my-app
-Activation:  v3_active
 Runtime:     ready
 Transport:   local
 Identity:    not configured
 Session evidence: explicit required
 
-V3 adapter status:
+mancode adapter status:
   ○ Claude Code: not installed
   ○ Cursor: not installed
   ✓ Codex (ChatGPT desktop/CLI): ready
@@ -475,8 +476,8 @@ Issue DB: .mancode/local/preseason-issues.json
 
 ### `mancode init`
 
-Initializes V3 authority and connects the selected platform's original mode
-entries to V3 Context Packs and workflow commands. It does not create legacy
+Initializes mancode workflow data and connects the selected platform's original
+mode entries to Context Packs and workflow commands. It does not create legacy
 `state.json`; use `mancode init --legacy` explicitly for the old architecture.
 
 ```bash
@@ -485,7 +486,7 @@ mancode init
 
 ### `mancode status`
 
-Shows V3 activation, runtime binding, identity/session evidence, transport, and
+Shows activation, runtime binding, identity/session evidence, transport, and
 the physical readiness of each platform bootstrap and original mode entry.
 
 ```bash
@@ -495,7 +496,7 @@ mancode status --json
 
 ### `mancode workflow`
 
-Creates and manages V3 workflows used by `/manba`, `/man`, and `/manteam`.
+Creates and manages workflows used by `/manba`, `/man`, and `/manteam`.
 Every mutation uses a `namespace:ULID` TaskRef, an explicit session, and the
 latest expected revision. Requirements, plan, review, verification, and
 completion use dedicated commands instead of the legacy `--step` protocol.
@@ -541,7 +542,7 @@ tokens. It updates:
 .mancode/shared/context/project.json
 ```
 
-V3 adapters are static bootstraps that embed no task or style snapshot, so
+Platform adapters are static bootstraps that embed no task or style snapshot, so
 refreshing project facts does not require reinstalling them.
 
 ## Project Files
@@ -553,7 +554,7 @@ mancode/
 │   ├── mancode status
 │   └── mancode install <platform>
 │
-├── V3 authority
+├── Workflow authority
 │   ├── shared/context + team
 │   └── local/session + workflow + cache
 │
@@ -681,7 +682,7 @@ are opt-in for work that needs planning, tests, and review.
 
 Yes. mancode supports Claude Code, Cursor, Codex in the ChatGPT desktop app and
 CLI, GitHub Copilot, and experimental ZCode adaptation through static
-bootstraps and original mode entries. V3 treats no platform hook as approved by
+bootstraps and original mode entries. mancode treats no platform hook as approved by
 default.
 
 ### Can mancode help with frontend consistency?

package/README.md

@@ -17,10 +17,8 @@
 <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.12-green?style=flat-square" alt="状态：稳定版 v0.3.12" />
-  <img src="https://img.shields.io/badge/V3-%E8%B7%A8%20CLI%20%E5%9B%A2%E9%98%9F%20Beta-FB6A21?style=flat-square" alt="V3：跨 CLI 团队协作 Beta" />
+  <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/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" />
-  <img src="https://img.shields.io/badge/tests-passing-brightgreen?style=flat-square" alt="测试通过" />
 </p>
 
 <p align="center">
@@ -39,15 +37,15 @@
 负责调研、计划、实现和审查。
 
 mancode 当前支持 Claude Code、Cursor、ChatGPT 桌面端中的 Codex、Codex CLI、
-GitHub Copilot 和 ZCode。V3 在每个平台继续使用原 `man*` 入口，并通过静态
-bootstrap 接入统一 Context Pack 与 workflow authority。
+GitHub Copilot 和 ZCode。每个平台继续使用原来的 `man*` 入口，并通过静态
+bootstrap 接入统一的 Context Pack 与 workflow authority。
 
 mancode 会安装三类能力：
 
-1. **V3 authority**：管理显式 session、TaskRef、Context Pack、workflow 和团队协调。
+1. **工作流权威数据**：管理显式 session、TaskRef、Context Pack、workflow 和团队协调。
 2. **Skills / modes**：提供 `solo`、`/manba`、`/man`、`/manteam`、`/manps`、
    `/mansolo` 工作流模式。
-3. **平台 bootstrap**：把原入口接到 V3；只有 `--legacy` 才安装旧 hooks。
+3. **平台 bootstrap**：把原入口接到 mancode；只有 `--legacy` 才安装旧 hooks。
 
 当 AI 编码代理写太多代码、忽略已有 UI 系统、跳过计划，或者关键改动需要稳定工程流程时，
 mancode 可以作为一层本地工作流约束。
@@ -83,12 +81,31 @@ ChatGPT 桌面端、Codex CLI 和 Codex IDE 扩展会从 `.agents/skills/` 读
 和 [slash command 文档](https://learn.chatgpt.com/docs/reference/slash-commands)。
 已有 workflow 元数据继续兼容，不需要迁移。
 
-## V3 跨 CLI 与团队协作 Beta
+## 跨会话继续工作
 
-V3 为新团队项目提供稳定 `TaskRef` 上下文、隔离 session、治理账本、worktree
-claim/handoff，以及可选的 git-ref 跨 clone 协调。它是**带硬门禁的 Beta**：adapter 能为
-Claude Code、Cursor、Codex、GitHub Copilot 和 ZCode 提供 bootstrap，但不会把平台文件
-当作任务或 session 状态的权威来源。
+mancode 把目标、需求、计划、检查结果和交接信息保存在稳定 `TaskRef` 下。换一个聊天
+窗口、重启编码 Agent，或者从另一个受支持的 CLI 继续时，新会话可以恢复同一项任务，
+再按当前目的读取精简的 Context Pack，而不必依赖上一段对话仍然打开。
+
+它续接的是**任务上下文**，不是原始聊天记录。不同客户端的 session 仍然隔离；新会话
+必须使用自己的 client 身份，并显式恢复已有 TaskRef。这样既能延续工作，也不会把一个
+窗口的临时状态误当成另一个窗口的身份。
+
+```bash
+mancode status --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
+```
+
+原来的 `/man`、`/manba` 和 `/manteam` 入口会处理这些步骤。上面的 CLI 形式适合排查、
+自动化或手工恢复任务。
+
+## 跨客户端与团队协作
+
+mancode 为团队项目提供稳定 TaskRef、隔离 session、治理账本、worktree claim/handoff，
+以及可选的 git-ref 跨 clone 协调。Claude Code、Cursor、Codex、GitHub Copilot 和
+ZCode 都通过 bootstrap 使用同一套工作流数据；平台文件本身不保存任务或 session 副本。
 
 在全新项目中，从一个实际使用的平台开始：
 
@@ -99,30 +116,18 @@ mancode context session new --client claude-code
 mancode list-platforms
 ```
 
-普通 `mancode init` 现在就是 V3 入口，并继续生成原来的 `man`、`manba`、
-`manteam`、`manps`、`mansolo` 平台命令；不需要改用另一套 V3 命令名。
-`--v3` 仅保留为显式兼容别名；确实需要旧 `state.json` 架构时才使用
+普通 `mancode init` 会生成原来的 `man`、`manba`、`manteam`、`manps`、
+`mansolo` 平台命令，不需要改用另一套命令名。确实需要旧 `state.json` 架构时才使用
 `mancode init --legacy`。
 
 创建、恢复和协作均通过 CLI 完成：`mancode workflow create`、`mancode context resume`、
 `mancode team claim` 和 `mancode team handoff`。已有项目先运行
 `mancode migrate context --dry-run`，再按迁移报告确认 stage/activation；不要手工混写
-legacy `state.json` 与 V3 authority。
-
-### Beta 的验证边界
-
-- `main` 的 Windows 门禁会从 CMD、PowerShell 和 Git Bash 运行 smoke 测试。
-- `mancode context beta --release-candidate <commit> --json` 会检查 activation、adapter、repair、worktree binding 和
-  五个平台的 session evidence；evidence 必须绑定同一个不可变发布候选，任何 blocker 都会阻止大范围启用。
-- 每个平台都必须在真实宿主中证明两个窗口的 session 区分、子命令传播以及子 agent 继承（或记录明确的不适用原因）。
-  `context session spike` 只记录操作者报告的真实宿主结果，不会由临时环境变量自动推断传播成功；证据不保存原始 session key。
-
-在门禁通过前，继续显式传入 `--session <id>`，不要把 host identity 视为已验证。这样可以
-先试用 V3，同时避免把尚未证明的跨平台 session 行为当作事实。
+legacy `state.json` 与当前工作流权威数据。
 
 ## 安装后创建哪些文件？
 
-默认的 `mancode init` 会创建 V3 权威目录和平台适配文件：
+默认的 `mancode init` 会创建 mancode 工作流目录和平台适配文件：
 
 ```text
 .mancode/
@@ -140,7 +145,7 @@ AGENTS.md                        # Codex（ChatGPT 桌面端/CLI）：托管 ins
 .github/prompts/                 # GitHub Copilot：原 mode prompts
 ```
 
-`.mancode/` 把可共享的 V3 权威与 checkout-local 的 session、workflow 和扫描报告分开。
+`.mancode/` 把可共享的工作流数据与 checkout-local 的 session、workflow 和扫描报告分开。
 平台文件只保存 bootstrap 和原模式入口，不保存 task/session 副本。
 `mancode init --legacy` 才会创建旧的 `state.json` 布局。
 
@@ -159,7 +164,7 @@ AGENTS.md                        # Codex（ChatGPT 桌面端/CLI）：托管 ins
 mancode 适合：
 
 - 正在使用 AI 编码代理的后端、Web、移动端、桌面端、CLI、库、数据或混合项目
-- 希望在原 `man*` 命令中使用 V3 Context Pack、skills 和显式治理的用户
+- 希望在原 `man*` 命令中使用 Context Pack、skills 和显式治理的用户
 - 希望 AI 代理复用已有组件和代码模式的团队
 - 需要可重复 AI 辅助代码审查流程的项目
 - 已有 UI 组件、主题、CSS 变量或设计约定的界面项目
@@ -205,8 +210,8 @@ mancode 不是 Claude Code、Cursor、Codex 或 Copilot 的替代品。它是在
 
 ## 使用方法
 
-V3 不再把“当前模式”写进持久状态。需要某种工作方式时，直接在 AI 编码代理的
-对话中调用原命令；入口会解析 V3 status、session、TaskRef 和 Context Pack：
+mancode 不把“当前模式”写进持久状态。需要某种工作方式时，直接在 AI 编码代理的
+对话中调用原命令；入口会解析 status、session、TaskRef 和 Context Pack：
 
 | 模式 | 适合场景 | 做什么 |
 |---|---|---|
@@ -215,7 +220,7 @@ V3 不再把“当前模式”写进持久状态。需要某种工作方式时
 | `/man` | 需要需求对齐或正式计划的改动 · 季后赛 | 调研、方案推荐和持久计划；确认后选择 solo 轻量开发或完整 9 步治理 |
 | `/manteam` | 团队项目 · 上场五人，一条心 | 共享记忆、决策记录、协作和 Conventional Commits |
 | `/manps` | 清理和维护 · 季前赛 | 输出 Markdown 和 JSON 项目健康报告 |
-| `/mansolo` | 回到轻量工作 | 不写 legacy mode；需要时执行显式 V3 handoff |
+| `/mansolo` | 回到轻量工作 | 不写 legacy mode；需要时执行显式 handoff |
 
 ## `/man` 如何工作：季后赛模式
 
@@ -245,16 +250,16 @@ V3 不再把“当前模式”写进持久状态。需要某种工作方式时
 
 ### Bootstrap 和 Adapters
 
-V3 默认不假设任何 hook 已获批准。平台 adapter 只安装稳定 bootstrap 与原来的
-`man/manba/manteam/manps/mansolo` 入口；任务、模式和 session 仍以 V3 authority
-为准。Claude Code 的内部 bootstrap 对用户隐藏，不会增加 `/mancode-v3` 公共命令。
+mancode 默认不假设任何 hook 已获批准。平台 adapter 只安装稳定 bootstrap 与原来的
+`man/manba/manteam/manps/mansolo` 入口；任务、模式和 session 以 mancode 工作流数据
+为准。Claude Code 的内部 bootstrap 对用户隐藏，不会增加额外的公共命令。
 没有经真实宿主验证的 session 传播时，写命令必须显式传入 `--session`。
 
 只有 `mancode init --legacy` 才安装读取 `.mancode/state.json` 的旧 Claude hooks。
 
 ### 设计 Token 感知
 
-mancode 会把检测到的 V3 项目事实写入 `.mancode/shared/context/project.json`；
+mancode 会把检测到的项目事实写入 `.mancode/shared/context/project.json`；
 checkout-local 的设计 token 缓存位于 `.mancode/local/cache/`。它可用于后端服务、
 Web、移动端、桌面端、CLI、库和混合仓库；不会预设 JavaScript 或 UI 技术栈。
 
@@ -286,7 +291,7 @@ src/components/
 
 ### 团队记忆
 
-`/manteam` 通过 V3 shared authority 读写经过确认的团队实体：
+`/manteam` 通过共享工作流数据读写经过确认的团队实体：
 
 ```text
 .mancode/shared/
@@ -300,7 +305,7 @@ src/components/
 
 ## 安装
 
-**状态**：稳定版 v0.3.12。Claude Code、Cursor、ChatGPT 桌面端中的 Codex、
+**状态**：稳定版 v0.3.13。Claude Code、Cursor、ChatGPT 桌面端中的 Codex、
 Codex CLI 和 GitHub Copilot 均已支持。ZCode adapter 已接入，但项目级 skill
 发现路径在发布前仍作为验证门禁。
 
@@ -319,7 +324,7 @@ mancode init --platform all
 
 平台支持：
 
-- Claude Code：隐藏 bootstrap 与原 mode skills；V3 默认不依赖 hooks
+- Claude Code：隐藏 bootstrap 与原 mode skills；默认不依赖 hooks
 - Cursor：`.cursor/rules/*.mdc` bootstrap 与 `.cursor/commands/` 原 mode commands
 - Codex（ChatGPT 桌面端、CLI、IDE 扩展）：托管 `AGENTS.md` block，并在
   `.agents/skills/` 下提供 `$man*` 项目 skills
@@ -340,8 +345,8 @@ mancode init --platform PLATFORMS # 一个或多个：claude-code,cursor,codex,c
 mancode init --empty      # 非交互脚本中允许安全的空目录
 mancode init --lang zh-CN # 显式指定初始化语言（zh-CN 或 en）
 mancode refresh-project   # 后续加入 Git 或项目文件后刷新项目事实
-mancode install --force   # 修复或重装所选 V3 adapter
-mancode install --minimal # V3 bootstrap 已是最小形态；保留兼容参数
+mancode install --force   # 修复或重装所选 adapter
+mancode install --minimal # bootstrap 已是最小形态；保留兼容参数
 ```
 
 ## Agent Modes
@@ -392,19 +397,18 @@ mancode version
 
 ### `mancode status`
 
-以下是 V3 项目的简化输出示例：
+以下是简化输出示例：
 
 ```text
-mancode v0.3.12 (V3 authority)
+mancode v0.3.13
 
 Project:     my-app
-Activation:  v3_active
 Runtime:     ready
 Transport:   local
 Identity:    not configured
 Session evidence: explicit required
 
-V3 adapter status:
+mancode adapter status:
   ○ Claude Code: not installed
   ○ Cursor: not installed
   ✓ Codex (ChatGPT desktop/CLI): ready
@@ -425,7 +429,7 @@ Issue DB: .mancode/local/preseason-issues.json
 
 ### `mancode init`
 
-初始化 V3 authority，并把所选平台的原 mode 入口接到 V3 Context Pack 与 workflow CLI。
+初始化 mancode 工作流数据，并把所选平台的原 mode 入口接到 Context Pack 与 workflow CLI。
 不会创建 legacy `state.json`；旧架构需显式运行 `mancode init --legacy`。
 
 ```bash
@@ -434,7 +438,7 @@ mancode init
 
 ### `mancode status`
 
-显示 V3 activation、runtime binding、identity/session evidence、transport 和各平台
+显示 activation、runtime binding、identity/session evidence、transport 和各平台
 bootstrap/原 mode 入口的实际就绪状态。
 
 ```bash
@@ -444,7 +448,7 @@ mancode status --json
 
 ### `mancode workflow`
 
-创建和管理 `/manba`、`/man` 和 `/manteam` 使用的 V3 workflow。每次写入使用
+创建和管理 `/manba`、`/man` 和 `/manteam` 使用的 workflow。每次写入使用
 `namespace:ULID` TaskRef、显式 session 和最新 expected revision；requirements、plan、
 review、verification 与 completion 各走专用命令，不再使用 legacy `--step` 协议。
 
@@ -488,7 +492,7 @@ mancode manps config
 .mancode/shared/context/project.json
 ```
 
-V3 adapter 是不嵌入 task/style 快照的静态 bootstrap，因此刷新项目事实后不需要重装。
+平台 adapter 是不嵌入 task/style 快照的静态 bootstrap，因此刷新项目事实后不需要重装。
 
 ## 项目文件
 
@@ -499,7 +503,7 @@ mancode/
 │   ├── mancode status
 │   └── mancode install <platform>
 │
-├── V3 authority
+├── Workflow authority
 │   ├── shared/context + team
 │   └── local/session + workflow + cache
 │
@@ -615,7 +619,7 @@ hooks。用户自定义的 rules 和 instructions 会被保留。
 
 支持。mancode 通过静态 bootstrap 和原 mode 入口支持 Claude Code、Cursor、
 ChatGPT 桌面端中的 Codex、Codex CLI、GitHub Copilot，并提供实验性 ZCode adapter。
-V3 默认不把任何平台的 hook 当成已批准能力。
+mancode 默认不把任何平台的 hook 当成已批准能力。
 
 ### mancode 能改善前端一致性吗？