mancode 0.4.1 → 0.4.2

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-Continuity%20v0.4.1-2f855a?style=flat-square" alt="Status: mancode Continuity v0.4.1" />
+  <img src="https://img.shields.io/badge/status-Continuity%20v0.4.2-2f855a?style=flat-square" alt="Status: mancode Continuity v0.4.2" />
   <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>
 
@@ -137,6 +137,13 @@ the code baseline, then run
 `MANCODE_GIT_REF_DEFERRED_SYNC_REQUIRED`; cross-clone synchronization is
 complete only after the push returns a receipt.
 
+Atomic git-ref mutations that explicitly require `--sync`, such as
+`workflow update`, complete the remote CAS before materializing the local
+projection. If a resumable `in_progress` or `blocked` task leaves tracked
+`.mancode/shared` changes, commit that projection and run the same
+`team sync push` with the unchanged task revision to rebind the remote code
+head. Another clone must not resume until this push returns a receipt.
+
 For a new project, start with one platform you actually use:
 
 ```bash
@@ -374,7 +381,7 @@ it should behave, and why previous decisions were made.
 
 ## Installation
 
-**Status**: mancode Continuity v0.4.1. Claude Code, Cursor, Codex in the ChatGPT
+**Status**: mancode Continuity v0.4.2. 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
@@ -481,7 +488,7 @@ mancode version
 Simplified output:
 
 ```text
-mancode v0.4.1
+mancode v0.4.2
 
 Project:     my-app
 Runtime:     ready
@@ -628,14 +635,16 @@ mancode/
 - Complete real-host session acceptance for Claude Code, Codex, Cursor,
   GitHub Copilot, and ZCode on one release candidate; verified host sessions
   and isolated explicit sessions are both valid evidence paths.
-- Run `npm run release:check -- --candidate <full-commit-sha>` for the clean
-  checkout, automated two-clone/legacy checks, tarball SHA-256, and install
-  smoke; complete cross-host recovery separately.
+- Merge the final candidate into `main`, then run
+  `npm run release:check -- --candidate <full-commit-sha>` from that same
+  `origin/main` commit for the clean checkout, automated two-clone/legacy
+  checks, tarball SHA-256, and install smoke; complete cross-host recovery
+  separately.
 - Confirm ZCode project-skill discovery and workspace-command paths; keep the
   adapter provisional until then.
 - Evaluate Windsurf, Cline, and Roo Code adapters based on real demand.
 
-See [0.4.1 Continuity Release Acceptance](./docs/release-acceptance.md) for the complete gate.
+See [0.4.2 Continuity Release Acceptance](./docs/release-acceptance.md) for the complete gate.
 
 ## Troubleshooting
 
@@ -660,7 +669,9 @@ hook architecture still uses `mancode init --legacy --force`.
 This means the platform's target files are missing or their digest is stale.
 Preview `mancode adapter upgrade --platform <platform> --dry-run`, inspect the
 staged result, then run it with the returned `--operation-id`, an active session,
-and `--confirm`. For managed-block
+and `--confirm`. A successful confirmation removes that operation's staging
+preview so internal temporary files cannot make a later Git sync report a dirty
+worktree. For managed-block
 platforms (Codex, ZCode, Copilot), the managed block in `AGENTS.md` or
 `.github/copilot-instructions.md` may have been manually edited or deleted.
 

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-Continuity%20v0.4.1-2f855a?style=flat-square" alt="状态：mancode Continuity v0.4.1" />
+  <img src="https://img.shields.io/badge/status-Continuity%20v0.4.2-2f855a?style=flat-square" alt="状态：mancode Continuity v0.4.2" />
   <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>
 
@@ -116,6 +116,12 @@ git-ref 下的 workflow create、requirements、plan、review 和 verification
 `--sync` 会返回 `MANCODE_GIT_REF_DEFERRED_SYNC_REQUIRED`；只有拿到 push receipt
 才表示跨 clone 同步完成。
 
+`workflow update` 等明确要求 `--sync` 的原子 git-ref mutation 会先完成远端 CAS，
+再 materialize 本地投影。如果仍需 resume 的 `in_progress` 或 `blocked` 任务因此产生
+tracked `.mancode/shared` 变更，应先提交这些投影，再用不变的 task revision 执行同一条
+`team sync push`，把远端 code head 重绑到新提交；另一个 clone 只能在这次 push 返回
+receipt 后 resume。
+
 在全新项目中，从一个实际使用的平台开始：
 
 ```bash
@@ -329,7 +335,7 @@ src/components/
 
 ## 安装
 
-**状态**：mancode Continuity v0.4.1。Claude Code、Cursor、ChatGPT 桌面端中的
+**状态**：mancode Continuity v0.4.2。Claude Code、Cursor、ChatGPT 桌面端中的
 Codex、Codex CLI、GitHub Copilot 和 ZCode adapter 均已接入。
 
 需要 Node.js 20 或更高版本。原生支持 macOS、Linux、Windows CMD、
@@ -434,7 +440,7 @@ mancode version
 以下是简化输出示例：
 
 ```text
-mancode v0.4.1
+mancode v0.4.2
 
 Project:     my-app
 Runtime:     ready
@@ -570,11 +576,11 @@ mancode/
 ## 仍在推进
 
 - 在同一发布候选上完成 Claude Code、Codex、Cursor、GitHub Copilot 和 ZCode 的真实宿主 session 验收；宿主自动 session 和显式双 session 都是合法证据路径。
-- 使用 `npm run release:check -- --candidate <完整提交 SHA>` 完成干净 checkout、自动双 clone/legacy、tarball SHA-256 和安装 smoke；另完成跨真实宿主恢复。
+- 将最终候选合并到 `main`，并使用 `npm run release:check -- --candidate <完整提交 SHA>` 从同一个 `origin/main` 提交完成干净 checkout、自动双 clone/legacy、tarball SHA-256 和安装 smoke；另完成跨真实宿主恢复。
 - 确认 ZCode 项目级 skill 发现和 workspace command 路径；完成前继续标记为 provisional。
 - 根据真实需求评估 Windsurf、Cline 和 Roo Code adapter。
 
-完整发布条件见 [0.4.1 Continuity 发布验收](./docs/release-acceptance.md)。
+完整发布条件见 [0.4.2 Continuity 发布验收](./docs/release-acceptance.md)。
 
 ## 故障排查
 
@@ -596,7 +602,8 @@ mancode/
 
 该平台的目标文件缺失或 digest 不匹配。先运行
 `mancode adapter upgrade --platform <platform> --dry-run`，确认 staging 结果后再用
-该预览返回的 `--operation-id` 和 active session 执行 `--confirm`。
+该预览返回的 `--operation-id` 和 active session 执行 `--confirm`。确认成功后会删除
+该 operation 的 staging 预览，避免内部临时文件让后续 Git 同步误判工作区不干净。
 对于 Codex、ZCode 和 Copilot，`AGENTS.md` 或 `.github/copilot-instructions.md`
 中的受控区可能被手动编辑或删除了。
 

package/dist/{chunk-S3BAOJPP.js → chunk-3FOBYCF4.js}

@@ -3632,10 +3632,6 @@ var WorkflowPolicyVersionUnsupportedError = class extends Error {
     this.requiredWriter = requiredWriter;
     this.name = "WorkflowPolicyVersionUnsupportedError";
   }
-  component;
-  observedVersion;
-  supportedVersions;
-  requiredWriter;
   code = "MANCODE_POLICY_VERSION_UNSUPPORTED";
 };
 var TRANSITION_STATES = /* @__PURE__ */ new Set([
@@ -7275,4 +7271,4 @@ export {
   V3ContextStore,
   storedTaskAggregateDigest
 };
-//# sourceMappingURL=chunk-S3BAOJPP.js.map
+//# sourceMappingURL=chunk-3FOBYCF4.js.map