@hunter-harness/workflow-harness 0.2.74 → 0.2.75

package/harness/bundles/general/claude-code/.harness-build.json

@@ -2,5 +2,5 @@
   "schemaVersion": 1,
   "overlay": "none",
   "agent": "claude-code",
-  "coreHash": "d0ad43fe132b6817"
+  "coreHash": "24b43afeb4dc4c52"
 }

package/harness/bundles/general/claude-code/harness-archive/SKILL.md

@@ -21,7 +21,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-archive — 变更归档
 
 ## Purpose
@@ -56,6 +56,7 @@ disallowed-tools:
 
 ## 统一读取协议
 
+0. **脚本在 `<skills-root>/scripts/` 共享，不在每个 skill 子目录下** — 实际形态是 `.codebuddy/skills/scripts/harness_*.py`（`.claude`/`.cursor`/`.codex` 同理），**没有** `.../skills/harness-<phase>/scripts/`。plan、run/test、archive 三份执行日志里都先猜成后者、报 `No such file` 再靠 Search 找回来；照第一种写法直接用
 1. **`.harness/changes/<change-name>/` 是唯一真相源** — 所有输入从该目录读取，产物写入对应子目录
 2. **change-name 优先从 frontmatter 读取** — `plans/*-design.md`、`spec/*-design.md`、`plans/*-plan.md` 的 YAML `change-name`
 3. **frontmatter 缺失时兼容旧格式** — 从路径推断，标记 `🟡 legacy-plan`，不失败
@@ -143,6 +144,13 @@ disallowed-tools:
 
 `execute` 内部运行自动门禁。实际计划最后阶段已终态、边界快照存在且 `status.archivable=true` 时直接执行；未满足时返回阻断且不移动原目录。用户取消后不得重跑。
 
+### 二·A、两个常见阻断的正规出路（不要自己拼 python -c）
+
+| 阻断 | 出路 |
+|------|------|
+| `SENSITIVE_EVIDENCE_UNQUARANTINED` | `python <skills-root>/scripts/harness_runtime.py quarantine-evidence --project . --change-dir ".harness/changes/<cn>" --file "<相对 change-dir 的路径>" --reason "<为什么是敏感证据>" --json`（`--file` 可重复）。私有根默认已与项目同盘、且在项目根之外——**不要**手工指定项目内的路径，归档的密钥扫描会以 `SECRET_SCAN_PRIVATE_PATH_IN_COPY_ROOT` 拒绝 |
+| `DIFF_ZERO_WITH_NONEMPTY_COMMIT`（提交范围非空但 filesChanged=0） | 契约缺 `ownership.productPaths`，全部改动被判为 `foreignPaths`。用 `python <skills-root>/scripts/harness_change.py declare-ownership --change <cn> --product-path "<目录前缀或精确文件>" --json` 按计划的实际改动范围声明（可重复；只收精确路径，不支持通配）。**不要**手改 `change-context.json` |
+
 ### 三、文件移动只用内置工具或 PowerShell
 
 移动用 Read+Write+验证 或 PowerShell；**禁止 Bash mv/cp/rm**。移动失败时不删除原目录，报错退出让用户手动处理。
@@ -204,6 +212,23 @@ git 命令通过 `powershell.exe -Command "..."` 执行；archive-meta.md 和 su
 - `.harness/archive/YYYY-MM-DD-<change-name>/events.ndjson` — 结构化事件层（新流程推荐；旧 archive 可缺失）
 - `.harness/archive/YYYY-MM-DD-<change-name>/reports/final/summary-data.json` — 最终报告数据源
 - `.harness/archive/YYYY-MM-DD-<change-name>/evidence/archive-manifest-before.json` / `archive-manifest-after.json` — 归档前后 manifest/checksum
+- `.harness/state/local/archive-packages/<change-name>.remote.json` — 远端上传回执（`archiveId`/`archiveStatus`/`knowledgeStatus`/`uploadStatus`/`fileCount`）
+
+### 结束报告必须回显两条上传结果 ⚠️
+
+归档会做**两次**独立上传，二者成败无关，必须分别如实回显：
+
+| 上传 | 载什么 | 结果在哪 |
+|------|--------|---------|
+| `steps.archive_push` | 归档 ZIP（核心产物） | `archiveId`/`archiveStatus`/`uploadStatus`/`knowledgeStatus`，同时落盘 `state/local/archive-packages/<cn>.remote.json` |
+| `steps.managed_snapshot_push` | **plan/spec 文档、`.harness/codebase` 架构地图、`.harness/rules`**（push 会 walk 每个归档目录的 `spec/` 与 `plans/`） | `ok`/`reasonCode`/`exitCode`/`cliCode`/`detail` |
+
+```
+远端归档：arc_3ff325bb…（archiveStatus=durable，uploadStatus=ready，knowledgeStatus=ready，8 文件）
+受管快照：❌ MANAGED_SNAPSHOT_UPLOAD_FAILED（exitCode=1，detail=…）→ plan/spec 与规则/架构地图未上平台，需 npx hunter-harness push --yes --non-interactive 重试
+```
+
+**第二条尤其不能省**：它是 best-effort，失败不阻断归档，于是最容易被淹没成一句警告——而平台上"分支文件里没有 plan/spec"正是它失败的后果。成功时也要写明 `submitted` 数量；`ok=false` 时必须带上 `reasonCode` 与 `detail`，不得省略或写成"已完成"。
 
 ## 渐进披露
 

package/harness/bundles/general/claude-code/harness-codebase-map/SKILL.md

@@ -20,7 +20,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-codebase-map — 代码库地图
 
 ## Purpose

package/harness/bundles/general/claude-code/harness-knowledge-ingest/SKILL.md

@@ -8,7 +8,7 @@ disallowed-tools:
   - Bash(git *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-knowledge-ingest
 
 知识 ingest 完全由 Hunter Platform 负责。归档完成时，客户端生成一个确定性 ZIP；

package/harness/bundles/general/claude-code/harness-knowledge-query/SKILL.md

@@ -8,7 +8,7 @@ disallowed-tools:
   - Bash(git *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-knowledge-query
 
 项目知识以 Hunter Platform 的服务端索引为唯一真源。客户端只提交查询并消费结果：

package/harness/bundles/general/claude-code/harness-plan/SKILL.md

@@ -21,7 +21,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-plan — 需求规划
 
 ## Purpose
@@ -38,6 +38,7 @@ disallowed-tools:
 
 ## 统一读取协议
 
+0. **脚本在 `<skills-root>/scripts/` 共享，不在每个 skill 子目录下** — 实际形态是 `.codebuddy/skills/scripts/harness_*.py`（`.claude`/`.cursor`/`.codex` 同理），**没有** `.../skills/harness-<phase>/scripts/`。plan、run/test、archive 三份执行日志里都先猜成后者、报 `No such file` 再靠 Search 找回来；照第一种写法直接用
 1. **`.harness/changes/<change-name>/` 是唯一真相源** — 所有输入从该目录读取，产物写入对应子目录
 2. **change-name 优先从 frontmatter 读取** — `plans/*-design.md`、`spec/*-design.md`、`plans/*-plan.md` 的 YAML `change-name`
 3. **frontmatter 缺失时兼容旧格式** — 从路径推断，标记 `🟡 legacy-plan`，不失败

package/harness/bundles/general/claude-code/harness-pull/SKILL.md

@@ -21,7 +21,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-pull — 从 Hunter Platform 下拉与恢复
 
 ## Purpose

package/harness/bundles/general/claude-code/harness-push/SKILL.md

@@ -21,7 +21,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-push — 上传到 Hunter Platform
 
 ## Purpose

package/harness/bundles/general/claude-code/harness-review/SKILL.md

@@ -22,7 +22,7 @@ disallowed-tools:
   - Bash(curl *)
   - Bash(codegraph *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-review — 代码审查
 
 ## Purpose
@@ -48,6 +48,7 @@ disallowed-tools:
 
 ## 统一读取协议
 
+0. **脚本在 `<skills-root>/scripts/` 共享，不在每个 skill 子目录下** — 实际形态是 `.codebuddy/skills/scripts/harness_*.py`（`.claude`/`.cursor`/`.codex` 同理），**没有** `.../skills/harness-<phase>/scripts/`。plan、run/test、archive 三份执行日志里都先猜成后者、报 `No such file` 再靠 Search 找回来；照第一种写法直接用
 1. **`.harness/changes/<change-name>/` 是唯一真相源** — 所有输入从该目录读取，产物写入对应子目录
 2. **change-name 优先从 frontmatter 读取** — `plans/*-design.md`、`spec/*-design.md`、`plans/*-plan.md` 的 YAML `change-name`
 3. **frontmatter 缺失时兼容旧格式** — 从路径推断，标记 `🟡 legacy-plan`，不失败

package/harness/bundles/general/claude-code/harness-run/SKILL.md

@@ -22,7 +22,7 @@ disallowed-tools:
   - Bash(curl *)
   - Bash(codegraph *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-run — 需求编码
 
 ## Purpose
@@ -59,6 +59,7 @@ disallowed-tools:
 
 ## 统一读取协议
 
+0. **脚本在 `<skills-root>/scripts/` 共享，不在每个 skill 子目录下** — 实际形态是 `.codebuddy/skills/scripts/harness_*.py`（`.claude`/`.cursor`/`.codex` 同理），**没有** `.../skills/harness-<phase>/scripts/`。plan、run/test、archive 三份执行日志里都先猜成后者、报 `No such file` 再靠 Search 找回来；照第一种写法直接用
 1. **`.harness/changes/<change-name>/` 是唯一真相源** — 所有输入从该目录读取，产物写入对应子目录
 2. **change-name 优先从 frontmatter 读取** — `plans/*-design.md`、`spec/*-design.md`、`plans/*-plan.md` 的 YAML `change-name`
 3. **frontmatter 缺失时兼容旧格式** — 从路径推断，标记 `🟡 legacy-plan`，不失败

package/harness/bundles/general/claude-code/harness-submit/SKILL.md

@@ -21,7 +21,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-submit — 最终提交（含 worktree 合并）
 
 ## Purpose
@@ -47,6 +47,7 @@ disallowed-tools:
 
 ## 统一读取协议
 
+0. **脚本在 `<skills-root>/scripts/` 共享，不在每个 skill 子目录下** — 实际形态是 `.codebuddy/skills/scripts/harness_*.py`（`.claude`/`.cursor`/`.codex` 同理），**没有** `.../skills/harness-<phase>/scripts/`。plan、run/test、archive 三份执行日志里都先猜成后者、报 `No such file` 再靠 Search 找回来；照第一种写法直接用
 1. **`.harness/changes/<change-name>/` 是唯一真相源** — 所有输入从该目录读取，产物写入对应子目录
 2. **change-name 优先从 frontmatter 读取** — `plans/*-design.md`、`spec/*-design.md`、`plans/*-plan.md` 的 YAML `change-name`
 3. **frontmatter 缺失时兼容旧格式** — 从路径推断，标记 `🟡 legacy-plan`，不失败

package/harness/bundles/general/claude-code/harness-sync/SKILL.md

@@ -19,7 +19,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-sync
 
 ## Purpose

package/harness/bundles/general/claude-code/harness-test/SKILL.md

@@ -23,7 +23,7 @@ disallowed-tools:
   - Bash(node *)
   - Bash(codegraph *)
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=claude-code; do not edit -->
 # harness-test — 测试执行
 
 ## Purpose
@@ -51,6 +51,7 @@ disallowed-tools:
 
 ## 统一读取协议
 
+0. **脚本在 `<skills-root>/scripts/` 共享，不在每个 skill 子目录下** — 实际形态是 `.codebuddy/skills/scripts/harness_*.py`（`.claude`/`.cursor`/`.codex` 同理），**没有** `.../skills/harness-<phase>/scripts/`。plan、run/test、archive 三份执行日志里都先猜成后者、报 `No such file` 再靠 Search 找回来；照第一种写法直接用
 1. **`.harness/changes/<change-name>/` 是唯一真相源** — 所有输入从该目录读取，产物写入对应子目录
 2. **change-name 优先从 frontmatter 读取** — `plans/*-design.md`、`spec/*-design.md`、`plans/*-plan.md` 的 YAML `change-name`
 3. **frontmatter 缺失时兼容旧格式** — 从路径推断，标记 `🟡 legacy-plan`，不失败

package/harness/bundles/general/claude-code/scripts/harness_archive.py

@@ -8552,8 +8552,17 @@ def cmd_finalize(
     payload["knowledgeMaintenance"] = _knowledge_maintenance_from_archive_push(
         push_result
     )
-    if push_result.get("archiveStatus") == "durable":
-        payload["archiveDurability"] = "ARCHIVED_REMOTE_DURABLE"
+    remote_durability = remote_durable_archive_durability(
+        payload.get("archiveDurability"), push_result
+    )
+    if remote_durability is not None:
+        payload["archiveDurability"] = remote_durability
+        # 报告必须跟着改口：上传发生在 summary 落盘之后，不回写就会出现
+        # "回执 durable / 报告 local-only" 的自相矛盾
+        if not persist_archive_durability(summary_path, remote_durability):
+            warnings.append(
+                "远端归档已持久化，但 summary-data.json 的 archiveDurability 回写失败"
+            )
     if push_result.get("warning"):
         warnings.append(str(push_result["warning"]))
 
@@ -9121,6 +9130,50 @@ def build_archive_package(
     }
 
 
+def remote_durable_archive_durability(
+    current: Any, push_result: Mapping[str, Any]
+) -> dict[str, Any] | None:
+    """远端上传成功后的耐久性投影；未 durable 时返回 None。
+
+    summary-data.json 在归档流程早期就以 ARCHIVED_LOCAL_ONLY 写盘，而 ZIP 上传在
+    那之后才发生。此前上传成功只改内存里的 payload、还把对象覆盖成裸字符串，落盘
+    报告从没跟着改——于是同一次归档，回执说 durable、报告说 local-only，平台和用户
+    读到的是后者。这里保持对象形状并带上回执标识，供调用方同时更新 payload 与文件。
+    """
+    if str(push_result.get("archiveStatus") or "") != "durable":
+        return None
+    projected = dict(current) if isinstance(current, dict) else {}
+    projected.update({
+        "status": "ARCHIVED_REMOTE_DURABLE",
+        # 已远端持久化：不再声称"只存在于本地、可能随工作区丢失"
+        "risk": None,
+        "archiveId": push_result.get("archiveId"),
+        "uploadStatus": push_result.get("uploadStatus"),
+        "knowledgeStatus": push_result.get("knowledgeStatus"),
+    })
+    return projected
+
+
+def persist_archive_durability(summary_path: Path, durability: dict[str, Any]) -> bool:
+    """把耐久性结论回写到已落盘的 summary，其余字段原样保留。
+
+    summary-data.json 本就被排除在归档校验和覆盖之外（它在覆盖快照之后才写），
+    所以这次回写不会破坏 manifest 对账。
+    """
+    try:
+        summary = json.loads(Path(summary_path).read_text(encoding="utf-8-sig"))
+    except (OSError, json.JSONDecodeError):
+        return False
+    if not isinstance(summary, dict):
+        return False
+    summary["archiveDurability"] = durability
+    try:
+        write_json(Path(summary_path), summary)
+    except OSError:
+        return False
+    return True
+
+
 def auto_push_managed_snapshot(project_root: Path) -> dict[str, Any]:
     """Best-effort upload of rules and Codebase Map through the normal push protocol."""
     project_root = project_root.resolve()
@@ -9176,16 +9229,25 @@ def auto_push_managed_snapshot(project_root: Path) -> dict[str, Any]:
     except (json.JSONDecodeError, TypeError):
         output = None
     if completed.returncode != 0 or not isinstance(output, dict):
-        return {
+        # 失败时丢掉 stdout/stderr 等于把线索一起丢了：plan/spec 与规则、架构地图
+        # 全靠这条推送上平台，用户在平台上只会看到"东西没上去"，却无从查为什么。
+        # 保留有界的诊断片段（push 本身拒绝上传 secret，这里再截断兜底）。
+        detail = (completed.stderr or completed.stdout or "").strip()
+        failure: dict[str, Any] = {
             "ok": False,
             "skipped": False,
             "exitCode": completed.returncode,
             "reasonCode": "MANAGED_SNAPSHOT_UPLOAD_FAILED",
+            "detail": detail[-2_048:],
             "warning": (
-                "项目规则与架构地图未能同步到平台；归档不受影响，"
-                "稍后可运行 npx hunter-harness push --yes --non-interactive 重试。"
+                "项目规则与架构地图未能同步到平台（plan/spec 也随这条推送上传）；"
+                "归档不受影响，稍后可运行 npx hunter-harness push --yes --non-interactive 重试。"
             ),
         }
+        cli_code = output.get("code") or output.get("reason_code") if isinstance(output, dict) else None
+        if isinstance(cli_code, str) and cli_code:
+            failure["cliCode"] = cli_code
+        return failure
     summary = output.get("summary")
     submitted = summary.get("submitted", 0) if isinstance(summary, dict) else 0
     return {

package/harness/bundles/general/claude-code/scripts/harness_change.py

@@ -1081,6 +1081,90 @@ def cmd_resolve(args: argparse.Namespace) -> int:
     )
 
 
+def declare_product_ownership(
+    project_root: Path, change_id: str, *, product_paths: list[str]
+) -> dict[str, Any]:
+    """把 `ownership.productPaths` 写进 change 契约。
+
+    这个字段此前没有任何写入方：plan 的 validate_product_ownership 只校验、缺失时
+    软放行，而归档的 compute_ownership_diff 会把全部改动判成 foreignPaths，
+    filesChanged=0 直接触发 DIFF_ZERO_WITH_NONEMPTY_COMMIT。两端口径不一致，中间
+    没工具能补——只能手改契约。这里给出正规入口。
+
+    规则与 plan 校验一致：只收精确文件或目录前缀，不接受通配。
+    """
+    resolved = resolve_change(project_root, change_id)
+    if not resolved.get("ok"):
+        return resolved
+    change_dir = Path(resolved["changeDir"])
+    normalized = sorted({
+        str(item).strip().replace("\\", "/").removeprefix("./")
+        for item in product_paths
+        if isinstance(item, str) and item.strip()
+    })
+    if not normalized:
+        return {
+            "ok": False,
+            "code": "PLAN_PRODUCT_PATHS_REQUIRED",
+            "message": "至少声明一条 productPaths（精确文件或目录前缀）",
+        }
+    unsupported = sorted(p for p in normalized if any(ch in p for ch in "*?[]"))
+    if unsupported:
+        return {
+            "ok": False,
+            "code": "PLAN_PRODUCT_PATHS_GLOB_UNSUPPORTED",
+            "message": "productPaths 只接受精确文件或目录前缀，不支持通配：" + ", ".join(unsupported),
+            "unsupportedPaths": unsupported,
+        }
+
+    context_path = change_dir / CHANGE_CONTEXT_REL
+    try:
+        context = _read_json(context_path)
+    except (OSError, json.JSONDecodeError) as exc:
+        return {"ok": False, "code": "CHANGE_CONTEXT_INVALID", "message": str(exc)}
+    if not isinstance(context, dict):
+        return {"ok": False, "code": "CHANGE_CONTEXT_INVALID", "message": "change-context.json 不是对象"}
+
+    ownership = context.get("ownership")
+    ownership = dict(ownership) if isinstance(ownership, dict) else {}
+    if ownership.get("productPaths") == normalized:
+        return {
+            "ok": True,
+            "code": "PRODUCT_OWNERSHIP_DECLARED",
+            "idempotent": True,
+            "changeId": change_id,
+            "productPaths": normalized,
+            "path": str(context_path),
+        }
+    ownership["productPaths"] = normalized
+    context["ownership"] = ownership
+    _write_json(context_path, context)
+    return {
+        "ok": True,
+        "code": "PRODUCT_OWNERSHIP_DECLARED",
+        "idempotent": False,
+        "changeId": change_id,
+        "productPaths": normalized,
+        "path": str(context_path),
+    }
+
+
+def cmd_declare_ownership(args: argparse.Namespace) -> int:
+    project = resolve_main_project_root()
+    payload = declare_product_ownership(
+        project, args.change, product_paths=list(args.product_path)
+    )
+    if payload.get("ok"):
+        emit(payload, as_json=bool(args.json))
+        return 0
+    return emit_error(
+        str(payload.get("code", "PRODUCT_OWNERSHIP_FAILED")),
+        str(payload.get("message", "declare ownership failed")),
+        as_json=bool(args.json),
+        extra={k: v for k, v in payload.items() if k not in {"ok", "message"}},
+    )
+
+
 def cmd_migrate(args: argparse.Namespace) -> int:
     project = resolve_main_project_root()
     if not args.change:
@@ -1451,6 +1535,17 @@ def build_parser() -> argparse.ArgumentParser:
     p_migrate.add_argument("--change", required=True)
     p_migrate.set_defaults(func=cmd_migrate)
 
+    p_ownership = sub.add_parser(
+        "declare-ownership", parents=[shared],
+        help="declare ownership.productPaths so archive can project the real diff",
+    )
+    p_ownership.add_argument("--change", required=True)
+    p_ownership.add_argument(
+        "--product-path", required=True, action="append",
+        help="exact file or directory prefix (no globs); repeatable",
+    )
+    p_ownership.set_defaults(func=cmd_declare_ownership)
+
     p_claim = sub.add_parser("claim", parents=[shared])
     p_claim.add_argument("--change", required=True)
     p_claim.add_argument("--phase", required=True)

package/harness/bundles/general/claude-code/scripts/harness_runtime.py

@@ -157,6 +157,35 @@ def _private_evidence_root(explicit: Path | None = None) -> Path:
             Path.home() / ".harness" / "private-evidence").expanduser().resolve()
 
 
+def private_evidence_root_for(source: Path, explicit: Path | None = None) -> Path:
+    """私有隔离根：必须与源同一驱动器。
+
+    `os.replace` 跨驱动器会直接失败（Windows 上是 WinError 17）。默认根
+    `~/.harness/private-evidence` 在 Windows 落 C 盘，项目在别的盘时隔离必然失败
+    ——而隔离是归档的硬前置，等于整条归档路被堵死。同盘时沿用配置/默认值；不同盘
+    时退到源所在驱动器根下的 `.harness-private-evidence`（天然在任何项目根之外）。
+    POSIX 上 drive 恒为空串，行为不变。
+    """
+    source = source.expanduser().resolve()
+    preferred = _private_evidence_root(explicit)
+    if preferred.drive.lower() == source.drive.lower():
+        return preferred
+    return (Path(source.anchor) / ".harness-private-evidence").resolve()
+
+
+def _infer_project_root(change_root: Path) -> Path | None:
+    """change 目录形如 `<project>/.harness/changes/<name>`：取路径里 `.harness` 段的父目录。
+
+    不做"向上找存在 .harness 的目录"式搜索——用户 HOME 下通常也有 `.harness`，
+    那样会把 HOME 误判成项目根，把合法的临时隔离位置一并拒掉。
+    """
+    parts = change_root.parts
+    for index in range(len(parts) - 1, 0, -1):
+        if parts[index] == ".harness":
+            return Path(*parts[:index])
+    return None
+
+
 def _secure_private_path(path: Path, *, directory: bool) -> str:
     """Best-effort owner-only permissions, with an explicit ACL result on Windows."""
     mode = 0o700 if directory else 0o600
@@ -288,11 +317,12 @@ def quarantine_sensitive_evidence(
     change_root: Path,
     reason: str = "sensitive evidence",
     private_root: Path | None = None,
+    project_root: Path | None = None,
 ) -> dict[str, Any]:
     """Atomically move legacy plaintext evidence outside any publishable tree."""
     source = source.expanduser().resolve()
     change_root = change_root.expanduser().resolve()
-    private = _private_evidence_root(private_root)
+    private = private_evidence_root_for(source, private_root)
     if not source.is_file():
         return {"ok": False, "reasonCode": "SENSITIVE_EVIDENCE_SOURCE_MISSING", "sourcePath": str(source)}
     if private == change_root or private.is_relative_to(change_root):
@@ -301,6 +331,25 @@ def quarantine_sensitive_evidence(
             "reasonCode": "SENSITIVE_EVIDENCE_QUARANTINE_FAILED",
             "error": "private quarantine root must be outside the publishable change root",
         }
+    # 归档的密钥扫描门禁按**项目根**判定（SECRET_SCAN_PRIVATE_PATH_IN_COPY_ROOT）。
+    # 这里此前只看 change_root，比门禁宽——于是隔离"成功"了，门禁再拒一次，调用方
+    # 得多试一轮才找到合法位置。对齐到同一条边界，错就错在当场。
+    resolved_project = (
+        project_root.expanduser().resolve()
+        if project_root is not None
+        else _infer_project_root(change_root)
+    )
+    if resolved_project is not None and (
+        private == resolved_project or private.is_relative_to(resolved_project)
+    ):
+        return {
+            "ok": False,
+            "reasonCode": "SENSITIVE_EVIDENCE_QUARANTINE_FAILED",
+            "error": (
+                "private quarantine root must be outside the project root "
+                f"({resolved_project}); archive's secret scan rejects paths inside it"
+            ),
+        }
     try:
         raw_digest = "sha256:" + hashlib.sha256(source.read_bytes()).hexdigest()
         quarantine_dir = private / uuid.uuid4().hex
@@ -1850,6 +1899,37 @@ def doctor(project: Path, change_dir: Path, *, agent: str) -> dict[str, Any]:
     return {"ok": True, "action": "doctor", **payload}
 
 
+def cmd_quarantine_evidence(args: argparse.Namespace) -> dict[str, Any]:
+    """隔离命令：把明文敏感证据原子移出可发布树，逐条返回结果。
+
+    单条失败不吞掉其余条目——归档阻断项常常一次报多个文件，逐条报告才能一轮修完。
+    """
+    project = Path(args.project).expanduser().resolve()
+    change_root = Path(args.change_dir).expanduser().resolve()
+    private_root = Path(args.private_root) if args.private_root else None
+    entries: list[dict[str, Any]] = []
+    for raw in args.file:
+        candidate = Path(raw)
+        source = candidate if candidate.is_absolute() else change_root / candidate
+        outcome = quarantine_sensitive_evidence(
+            source,
+            change_root=change_root,
+            reason=args.reason,
+            private_root=private_root,
+            project_root=project,
+        )
+        entries.append({"file": raw, **outcome})
+    failed = [item for item in entries if not item.get("ok")]
+    return {
+        "ok": not failed,
+        "action": "quarantine-evidence",
+        "code": "SENSITIVE_EVIDENCE_QUARANTINED" if not failed else "SENSITIVE_EVIDENCE_QUARANTINE_FAILED",
+        "quarantined": len(entries) - len(failed),
+        "failed": len(failed),
+        "entries": entries,
+    }
+
+
 def build_parser() -> argparse.ArgumentParser:
     parser = argparse.ArgumentParser(prog="harness_runtime.py")
     sub = parser.add_subparsers(dest="command", required=True)
@@ -1858,6 +1938,24 @@ def build_parser() -> argparse.ArgumentParser:
     p_doctor.add_argument("--change-dir", required=True)
     p_doctor.add_argument("--agent", choices=sorted(_ADAPTERS), required=True)
     p_doctor.add_argument("--json", action="store_true")
+    # 归档的 SENSITIVE_EVIDENCE_UNQUARANTINED 是硬阻断，此前却没有任何命令行入口
+    # ——调用方只能写 python -c + sys.path hack 去调内部函数。
+    p_quarantine = sub.add_parser(
+        "quarantine-evidence",
+        help="move plaintext sensitive evidence outside the publishable tree",
+    )
+    p_quarantine.add_argument("--project", required=True)
+    p_quarantine.add_argument("--change-dir", required=True)
+    p_quarantine.add_argument(
+        "--file", required=True, action="append",
+        help="path to quarantine, relative to --change-dir or absolute; repeatable",
+    )
+    p_quarantine.add_argument("--reason", default="sensitive evidence")
+    p_quarantine.add_argument(
+        "--private-root", default=None,
+        help="override the private root; must be outside the project root and on its drive",
+    )
+    p_quarantine.add_argument("--json", action="store_true")
     p_adapter = sub.add_parser("adapter")
     p_adapter.add_argument("--agent", choices=sorted(_ADAPTERS), required=True)
     p_adapter.add_argument("--change", required=True)
@@ -1899,6 +1997,8 @@ def main(argv: list[str] | None = None) -> int:
     try:
         if args.command == "doctor":
             result = doctor(Path(args.project), Path(args.change_dir), agent=args.agent)
+        elif args.command == "quarantine-evidence":
+            result = cmd_quarantine_evidence(args)
         elif args.command == "adapter":
             result = {"ok": True, "action": "adapter", **adapter_worktree(args.agent, args.change)}
         elif args.command == "_worker":

package/harness/bundles/general/codebuddy/.harness-build.json

@@ -2,5 +2,5 @@
   "schemaVersion": 1,
   "overlay": "none",
   "agent": "codebuddy",
-  "coreHash": "d0ad43fe132b6817"
+  "coreHash": "24b43afeb4dc4c52"
 }

package/harness/bundles/general/codebuddy/harness-archive/SKILL.md

@@ -3,7 +3,7 @@ name: harness-archive
 description: 归档所有变更产出（计划/测试报告/审查/SQL/API文档）到 .harness/archive/，含归档元数据。仅当用户显式调用
   /harness-archive 时使用；不得被其他阶段 skill 自动接续触发。
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=codebuddy; do not edit -->
 # harness-archive — 变更归档
 
 ## Purpose
@@ -38,6 +38,7 @@ description: 归档所有变更产出（计划/测试报告/审查/SQL/API文档
 
 ## 统一读取协议
 
+0. **脚本在 `<skills-root>/scripts/` 共享，不在每个 skill 子目录下** — 实际形态是 `.codebuddy/skills/scripts/harness_*.py`（`.claude`/`.cursor`/`.codex` 同理），**没有** `.../skills/harness-<phase>/scripts/`。plan、run/test、archive 三份执行日志里都先猜成后者、报 `No such file` 再靠 Search 找回来；照第一种写法直接用
 1. **`.harness/changes/<change-name>/` 是唯一真相源** — 所有输入从该目录读取，产物写入对应子目录
 2. **change-name 优先从 frontmatter 读取** — `plans/*-design.md`、`spec/*-design.md`、`plans/*-plan.md` 的 YAML `change-name`
 3. **frontmatter 缺失时兼容旧格式** — 从路径推断，标记 `🟡 legacy-plan`，不失败
@@ -125,6 +126,13 @@ description: 归档所有变更产出（计划/测试报告/审查/SQL/API文档
 
 `execute` 内部运行自动门禁。实际计划最后阶段已终态、边界快照存在且 `status.archivable=true` 时直接执行；未满足时返回阻断且不移动原目录。用户取消后不得重跑。
 
+### 二·A、两个常见阻断的正规出路（不要自己拼 python -c）
+
+| 阻断 | 出路 |
+|------|------|
+| `SENSITIVE_EVIDENCE_UNQUARANTINED` | `python <skills-root>/scripts/harness_runtime.py quarantine-evidence --project . --change-dir ".harness/changes/<cn>" --file "<相对 change-dir 的路径>" --reason "<为什么是敏感证据>" --json`（`--file` 可重复）。私有根默认已与项目同盘、且在项目根之外——**不要**手工指定项目内的路径，归档的密钥扫描会以 `SECRET_SCAN_PRIVATE_PATH_IN_COPY_ROOT` 拒绝 |
+| `DIFF_ZERO_WITH_NONEMPTY_COMMIT`（提交范围非空但 filesChanged=0） | 契约缺 `ownership.productPaths`，全部改动被判为 `foreignPaths`。用 `python <skills-root>/scripts/harness_change.py declare-ownership --change <cn> --product-path "<目录前缀或精确文件>" --json` 按计划的实际改动范围声明（可重复；只收精确路径，不支持通配）。**不要**手改 `change-context.json` |
+
 ### 三、文件移动只用内置工具或 PowerShell
 
 移动用 Read+Write+验证 或 PowerShell；**禁止 Bash mv/cp/rm**。移动失败时不删除原目录，报错退出让用户手动处理。
@@ -186,6 +194,23 @@ git 命令通过 `powershell.exe -Command "..."` 执行；archive-meta.md 和 su
 - `.harness/archive/YYYY-MM-DD-<change-name>/events.ndjson` — 结构化事件层（新流程推荐；旧 archive 可缺失）
 - `.harness/archive/YYYY-MM-DD-<change-name>/reports/final/summary-data.json` — 最终报告数据源
 - `.harness/archive/YYYY-MM-DD-<change-name>/evidence/archive-manifest-before.json` / `archive-manifest-after.json` — 归档前后 manifest/checksum
+- `.harness/state/local/archive-packages/<change-name>.remote.json` — 远端上传回执（`archiveId`/`archiveStatus`/`knowledgeStatus`/`uploadStatus`/`fileCount`）
+
+### 结束报告必须回显两条上传结果 ⚠️
+
+归档会做**两次**独立上传，二者成败无关，必须分别如实回显：
+
+| 上传 | 载什么 | 结果在哪 |
+|------|--------|---------|
+| `steps.archive_push` | 归档 ZIP（核心产物） | `archiveId`/`archiveStatus`/`uploadStatus`/`knowledgeStatus`，同时落盘 `state/local/archive-packages/<cn>.remote.json` |
+| `steps.managed_snapshot_push` | **plan/spec 文档、`.harness/codebase` 架构地图、`.harness/rules`**（push 会 walk 每个归档目录的 `spec/` 与 `plans/`） | `ok`/`reasonCode`/`exitCode`/`cliCode`/`detail` |
+
+```
+远端归档：arc_3ff325bb…（archiveStatus=durable，uploadStatus=ready，knowledgeStatus=ready，8 文件）
+受管快照：❌ MANAGED_SNAPSHOT_UPLOAD_FAILED（exitCode=1，detail=…）→ plan/spec 与规则/架构地图未上平台，需 npx hunter-harness push --yes --non-interactive 重试
+```
+
+**第二条尤其不能省**：它是 best-effort，失败不阻断归档，于是最容易被淹没成一句警告——而平台上"分支文件里没有 plan/spec"正是它失败的后果。成功时也要写明 `submitted` 数量；`ok=false` 时必须带上 `reasonCode` 与 `detail`，不得省略或写成"已完成"。
 
 ## 渐进披露
 

package/harness/bundles/general/codebuddy/harness-codebase-map/SKILL.md

@@ -3,7 +3,7 @@ name: harness-codebase-map
 description: 分析现有代码库并生成 .harness/codebase/map/
   下的结构化代码库地图。用于陌生项目理解、重大改造前梳理、harness-sync 提示 map 过期后的人工刷新。
 ---
-<!-- generated by harness_deploy.py; core=d0ad43fe132b6817; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=24b43afeb4dc4c52; overlay=none; agent=codebuddy; do not edit -->
 # harness-codebase-map — 代码库地图
 
 ## Purpose