@hunter-harness/workflow-harness 0.2.79 → 0.2.80

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

@@ -2,5 +2,5 @@
   "schemaVersion": 1,
   "overlay": "none",
   "agent": "claude-code",
-  "coreHash": "ef40ffbb4f999ea0"
+  "coreHash": "5fadb6520fbfa2c3"
 }

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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=claude-code; do not edit -->
 # harness-archive — 变更归档
 
 ## Purpose
@@ -162,10 +162,21 @@ python <skills-root>/scripts/harness_archive.py republish --change <change-key>
 python <skills-root>/scripts/harness_archive.py republish --change <change-key> --json             # 重建并上传
 ```
 
+脚本在 `<skills-root>/scripts/` 共享，**不在 `harness-archive/scripts/`**（见 read-protocol 第 0 条）。
+
+在项目根内任意目录直接跑即可，**不需要** `--project`。
+
 归档目录是封存的（after-manifest 覆盖其每个字节），因此 `republish` **不写回**归档目录：
 缺失的 `candidates/knowledge.json` 只在内存中按已归档 summary 生成并放进包里。平台的知识
 条目只来自这个包；`--scope all` 走的是 branch_file 通道，不进知识管道。
 
+**服务端一个 change key 只存一个不可变包**，所以补传只适用于「从未成功上传」与「字节完全一致的
+重试」。已 durable 的 change 会在本地就判出结果：字节一致 → `ARCHIVE_ALREADY_PUBLISHED`
+（exit 0，不重传）；字节不同 → `ARCHIVE_REMOTE_IMMUTABLE_CONFLICT`（exit 1，**不发起上传**）。
+**已发布归档无法从客户端补知识条目**——注入候选必然改变字节，服务端拒绝替换；要补需要平台侧
+提供重新索引或归档版本化能力。
+只想重试**同一个包**（例如知识索引失败）时加 `--no-knowledge-injection`，它按封存目录原样重建，字节与已存包一致。
+
 ### 三、文件移动只用内置工具或 PowerShell
 
 移动用 Read+Write+验证 或 PowerShell；**禁止 Bash mv/cp/rm**。移动失败时不删除原目录，报错退出让用户手动处理。

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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; 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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; 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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; 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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=claude-code; do not edit -->
 # harness-plan — 需求规划
 
 ## Purpose

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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; 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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=claude-code; do not edit -->
 # harness-push — 上传到 Hunter Platform
 
 ## Purpose
@@ -57,8 +57,22 @@ npx hunter-harness harness-push --scope archive --change <change-key> --json
 python <skills-root>/scripts/harness_archive.py republish --change <change-key> --json
 ```
 
+`<skills-root>` 是已部署 skills 的根目录，实际形态是 `.codebuddy/skills/`（`.claude`、`.cursor`、
+`.codex` 同理）。**脚本在它下面的 `scripts/` 里共享，不在 `harness-push/scripts/`** —— 已有四份
+执行日志先猜成后者、报 `No such file` 再回头找。
+
 `--scope archive` 没有待发布 claim 时返回 `PUSH_PULL_ARCHIVE_NO_PENDING_CLAIM`（exit 5），
 stderr 里直接给出上面的 republish 命令；`--dry-run` 会列出本地可补传的归档目录，不取租约。
+`republish` 在项目根内任意目录直接跑即可，**不需要** `--project`。
+
+**补传能做什么、不能做什么**：服务端对同一 change key 只保存**一个不可变包**。所以补传只适用于
+「从未成功上传」与「字节完全一致的重试」两种情况。若该 change 已是 durable，`republish` 会读
+`.harness/state/local/archive-packages/<key>.remote.json` 在**本地就判定**并返回：
+字节一致 → `ARCHIVE_ALREADY_PUBLISHED`（exit 0，不重传）；字节不同 →
+`ARCHIVE_REMOTE_IMMUTABLE_CONFLICT`（exit 1，**不发起上传**）。
+**已发布的归档无法从客户端补上知识条目**——注入 `candidates/knowledge.json` 必然改变字节，
+服务端拒绝替换。要让旧归档产生知识条目，需要平台侧提供重新索引或归档版本化能力。
+只想重试**同一个包**（例如知识索引失败）时加 `--no-knowledge-injection`，它按封存目录原样重建，字节与已存包一致。
 
 ## 关键规则
 

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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=claude-code; do not edit -->
 # harness-review — 代码审查
 
 ## Purpose

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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=claude-code; do not edit -->
 # harness-run — 需求编码
 
 ## Purpose

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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=claude-code; do not edit -->
 # harness-submit — 最终提交（含 worktree 合并）
 
 ## Purpose

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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; 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=ef40ffbb4f999ea0; overlay=none; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=claude-code; do not edit -->
 # harness-test — 测试执行
 
 ## Purpose

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

@@ -10232,6 +10232,42 @@ def cmd_repair_cli(args: argparse.Namespace) -> int:
     return code
 
 
+def resolve_republish_project_root(explicit: Path | None, archive_dir: Path | None) -> Path:
+    """Locate the project root for a republish without requiring --project.
+
+    ``find_project_root`` walks ``p.parents``, which excludes ``p`` itself; it is
+    built for a change/archive subdirectory. Handing it the cwd therefore skips
+    the very directory the operator is standing in and keeps climbing — in a real
+    run that resolved ``E:/WorkProject/kb-sdd`` to its parent and made the command
+    look for archives that were never there.
+
+    Order: explicit flag, then the archive's own location, then cwd and its
+    parents (cwd included), then the deployed script's location — the script
+    lives at ``<project>/.claude|.codebuddy/skills/scripts/`` after install.
+    """
+    if explicit is not None:
+        return explicit.resolve()
+    if archive_dir is not None:
+        return find_project_root(archive_dir)
+
+    def first_with_archive(start: Path) -> Path | None:
+        start = start.resolve()
+        for candidate in (start, *start.parents):
+            if (candidate / ".harness" / "archive").is_dir():
+                return candidate
+        return None
+
+    found = first_with_archive(Path.cwd())
+    if found is not None:
+        return found
+    found = first_with_archive(Path(__file__).resolve().parent)
+    if found is not None:
+        return found
+    # Nothing carries an archive directory; report against cwd so the error names
+    # a path the operator recognises instead of some ancestor.
+    return Path.cwd().resolve()
+
+
 def resolve_archive_dir_for_change(
     project_root: Path,
     change_key: str,
@@ -10272,7 +10308,10 @@ def _republish_knowledge_entry(archive_dir: Path) -> dict[str, tuple[str, str, b
         change_key=str(summary.get("changeName") or archive_dir.name),
         archive_id=archive_dir.name,
         producer_version=SCHEMA_VERSION,
-        created_at=now_iso(),
+        # Derived from the archive, never wall-clock: `now_iso()` here made every
+        # rebuild produce different bytes, so a package could never be compared
+        # against a stored one and the "deterministic package" claim was false.
+        created_at=_archive_created_at(summary_path),
     )
     if not candidates:
         return {}
@@ -10285,12 +10324,28 @@ def _republish_knowledge_entry(archive_dir: Path) -> dict[str, tuple[str, str, b
     }
 
 
+def read_durable_archive_receipt(project_root: Path, change_key: str) -> dict[str, Any] | None:
+    """The `<key>.remote.json` written after a confirmed durable upload, if any."""
+    receipt_path = (
+        project_root / ".harness" / "state" / "local" / "archive-packages"
+        / f"{change_key}.remote.json"
+    )
+    if not receipt_path.is_file():
+        return None
+    try:
+        receipt = read_json(receipt_path)
+    except (OSError, json.JSONDecodeError, TypeError, ValueError):
+        return None
+    return receipt if isinstance(receipt, dict) else None
+
+
 def cmd_republish(
     *,
     change_key: str,
     archive_dir: Path | None,
     project_root: Path | None,
     dry_run: bool,
+    inject_knowledge: bool = True,
 ) -> tuple[int, dict[str, Any]]:
     """Rebuild and re-upload the core ZIP for an already sealed archive.
 
@@ -10311,7 +10366,7 @@ def cmd_republish(
         payload["reasonCode"] = "ARCHIVE_CHANGE_KEY_INVALID"
         return 2, payload
 
-    root = (project_root or find_project_root(archive_dir or Path.cwd())).resolve()
+    root = resolve_republish_project_root(project_root, archive_dir)
     payload["projectRoot"] = str(root)
     matches: list[str] = []
     if archive_dir is None:
@@ -10338,53 +10393,103 @@ def cmd_republish(
         payload["reasonCode"] = "ARCHIVE_SUMMARY_MISSING"
         return 1, payload
 
-    try:
-        extra_entries = _republish_knowledge_entry(archive_dir)
-    except (OSError, ValueError, json.JSONDecodeError) as exc:
-        # Knowledge is additive: never fail a re-delivery over it.
-        payload.setdefault("warnings", []).append(
-            f"knowledge candidate regeneration skipped: {exc}"
-        )
-        extra_entries = {}
+    extra_entries: dict[str, tuple[str, str, bytes]] = {}
+    if inject_knowledge:
+        try:
+            extra_entries = _republish_knowledge_entry(archive_dir)
+        except (OSError, ValueError, json.JSONDecodeError) as exc:
+            # Knowledge is additive: never fail a re-delivery over it.
+            payload.setdefault("warnings", []).append(
+                f"knowledge candidate regeneration skipped: {exc}"
+            )
+            extra_entries = {}
     payload["knowledgeCandidatesInjected"] = "candidates/knowledge.json" in extra_entries
 
-    if dry_run:
-        # The package builder refuses to write outside the project, so the
-        # preview lands beside the real packages under a distinct name and is
-        # removed again; it must never be mistaken for a pending upload.
-        preview_path = (
-            root / ".harness" / "state" / "local" / "archive-packages"
-            / f"{change_key}.preview.zip"
+    # Build once, into a preview path, so the bytes can be compared against any
+    # durable receipt before an upload is attempted. The builder refuses to write
+    # outside the project, so the preview lands beside the real packages under a
+    # distinct name; it must never be mistaken for a pending upload.
+    preview_path = (
+        root / ".harness" / "state" / "local" / "archive-packages"
+        / f"{change_key}.preview.zip"
+    )
+    try:
+        package = build_archive_package(
+            root,
+            archive_dir,
+            change_key,
+            output_path=preview_path,
+            extra_entries=extra_entries,
         )
+    except (OSError, ValueError, UnicodeDecodeError, json.JSONDecodeError) as exc:
+        payload["error"] = f"archive package build failed: {exc}"
+        payload["reasonCode"] = "ARCHIVE_PACKAGE_BUILD_FAILED"
+        return 1, payload
+    finally:
         try:
-            package = build_archive_package(
-                root,
-                archive_dir,
-                change_key,
-                output_path=preview_path,
-                extra_entries=extra_entries,
-            )
-        except (OSError, ValueError, UnicodeDecodeError, json.JSONDecodeError) as exc:
-            payload["error"] = f"archive package build failed: {exc}"
-            payload["reasonCode"] = "ARCHIVE_PACKAGE_BUILD_FAILED"
-            return 1, payload
-        finally:
-            try:
-                preview_path.unlink(missing_ok=True)
-            except OSError:
-                pass
-        payload.update(
-            {
+            preview_path.unlink(missing_ok=True)
+        except OSError:
+            pass
+
+    payload.update(
+        {
+            "fileCount": package["fileCount"],
+            "sizeBytes": package["sizeBytes"],
+            "knowledgeCandidateCount": package["knowledgeCandidateCount"],
+            "packageSha256": package["packageSha256"],
+            "manifestSha256": package["manifestSha256"],
+            "files": package["paths"],
+        }
+    )
+
+    # The platform stores exactly one immutable package per change key. A rebuild
+    # that differs by even one byte is refused server-side, so decide here rather
+    # than spending an upload to learn it.
+    durable = read_durable_archive_receipt(root, change_key)
+    stored_sha = str((durable or {}).get("packageSha256") or "")
+    if durable is not None and str(durable.get("archiveStatus") or "") == "durable":
+        payload["remoteReceipt"] = {
+            "archiveId": durable.get("archiveId"),
+            "archiveStatus": durable.get("archiveStatus"),
+            "knowledgeStatus": durable.get("knowledgeStatus"),
+            "packageSha256": stored_sha,
+            "recordedAt": durable.get("recordedAt"),
+        }
+        if stored_sha and stored_sha == package["packageSha256"]:
+            payload.update({
                 "ok": True,
-                "reasonCode": "ARCHIVE_REPUBLISH_PREVIEW",
-                "fileCount": package["fileCount"],
-                "sizeBytes": package["sizeBytes"],
-                "knowledgeCandidateCount": package["knowledgeCandidateCount"],
-                "packageSha256": package["packageSha256"],
-                "manifestSha256": package["manifestSha256"],
-                "files": package["paths"],
-            }
-        )
+                "reasonCode": "ARCHIVE_ALREADY_PUBLISHED",
+                "message": (
+                    "远端已存有字节一致的同一个包，无需重传"
+                    f"（archiveId={durable.get('archiveId')}）。"
+                ),
+            })
+            return 0, payload
+        payload.update({
+            "ok": False,
+            "reasonCode": "ARCHIVE_REMOTE_IMMUTABLE_CONFLICT",
+            "error": (
+                "该 change 在远端已是 durable 归档，服务端对同一 change key 只保存一个"
+                "不可变包，不接受不同字节的替换。"
+            ),
+            "nextAction": (
+                "补传只适用于『从未成功上传』或『字节完全一致的重试』。"
+                + (
+                    "本次重建注入了 "
+                    f"{package['knowledgeCandidateCount']} 条知识候选"
+                    "（原包上传时还没有 candidates/knowledge.json），因此字节必然不同——"
+                    "已发布归档无法从客户端追加知识条目，需要平台侧提供重新索引或归档版本化能力。"
+                    "若只是想重试同一个包（例如知识索引失败），加 --no-knowledge-injection "
+                    "可重建与封存目录完全一致的字节。"
+                    if payload.get("knowledgeCandidatesInjected")
+                    else "本地归档内容与已上传的包不一致，请先确认哪一份才是应保留的事实。"
+                )
+            ),
+        })
+        return 1, payload
+
+    if dry_run:
+        payload.update({"ok": True, "reasonCode": "ARCHIVE_REPUBLISH_PREVIEW"})
         return 0, payload
 
     result = auto_push_archive_core(
@@ -10407,6 +10512,7 @@ def cmd_republish_cli(args: argparse.Namespace) -> int:
         archive_dir=resolve_path(args.archive_dir) if args.archive_dir else None,
         project_root=resolve_path(args.project) if args.project else None,
         dry_run=bool(args.dry_run),
+        inject_knowledge=not bool(args.no_knowledge_injection),
     )
     emit_json(payload)
     return code
@@ -10590,6 +10696,14 @@ def build_parser() -> argparse.ArgumentParser:
         action="store_true",
         help="build the package and report its contents without uploading",
     )
+    p_republish.add_argument(
+        "--no-knowledge-injection",
+        action="store_true",
+        help=(
+            "rebuild exactly what the sealed archive holds; needed to retry the "
+            "same bytes the server already stored"
+        ),
+    )
     p_republish.add_argument("--json", action="store_true", default=True)
     p_republish.set_defaults(func=cmd_republish_cli)
 

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

@@ -2,5 +2,5 @@
   "schemaVersion": 1,
   "overlay": "none",
   "agent": "codebuddy",
-  "coreHash": "ef40ffbb4f999ea0"
+  "coreHash": "5fadb6520fbfa2c3"
 }

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=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-archive — 变更归档
 
 ## Purpose
@@ -144,10 +144,21 @@ python <skills-root>/scripts/harness_archive.py republish --change <change-key>
 python <skills-root>/scripts/harness_archive.py republish --change <change-key> --json             # 重建并上传
 ```
 
+脚本在 `<skills-root>/scripts/` 共享，**不在 `harness-archive/scripts/`**（见 read-protocol 第 0 条）。
+
+在项目根内任意目录直接跑即可，**不需要** `--project`。
+
 归档目录是封存的（after-manifest 覆盖其每个字节），因此 `republish` **不写回**归档目录：
 缺失的 `candidates/knowledge.json` 只在内存中按已归档 summary 生成并放进包里。平台的知识
 条目只来自这个包；`--scope all` 走的是 branch_file 通道，不进知识管道。
 
+**服务端一个 change key 只存一个不可变包**，所以补传只适用于「从未成功上传」与「字节完全一致的
+重试」。已 durable 的 change 会在本地就判出结果：字节一致 → `ARCHIVE_ALREADY_PUBLISHED`
+（exit 0，不重传）；字节不同 → `ARCHIVE_REMOTE_IMMUTABLE_CONFLICT`（exit 1，**不发起上传**）。
+**已发布归档无法从客户端补知识条目**——注入候选必然改变字节，服务端拒绝替换；要补需要平台侧
+提供重新索引或归档版本化能力。
+只想重试**同一个包**（例如知识索引失败）时加 `--no-knowledge-injection`，它按封存目录原样重建，字节与已存包一致。
+
 ### 三、文件移动只用内置工具或 PowerShell
 
 移动用 Read+Write+验证 或 PowerShell；**禁止 Bash mv/cp/rm**。移动失败时不删除原目录，报错退出让用户手动处理。

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=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-codebase-map — 代码库地图
 
 ## Purpose

package/harness/bundles/general/codebuddy/harness-knowledge-ingest/SKILL.md

@@ -2,7 +2,7 @@
 name: harness-knowledge-ingest
 description: 确认归档 ZIP 已上传并由 Hunter Platform 在服务端解包、校验和入库。客户端不再构建或维护本地知识索引。
 ---
-<!-- generated by harness_deploy.py; core=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-knowledge-ingest
 
 知识 ingest 完全由 Hunter Platform 负责。归档完成时，客户端生成一个确定性 ZIP；

package/harness/bundles/general/codebuddy/harness-knowledge-query/SKILL.md

@@ -2,7 +2,7 @@
 name: harness-knowledge-query
 description: 在规划、实现或排查前，通过 hunter-harness CLI 查询远端项目知识库。远端不可用时直接报告不可用，不建立本地索引或离线回退。
 ---
-<!-- generated by harness_deploy.py; core=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-knowledge-query
 
 项目知识以 Hunter Platform 的服务端索引为唯一真源。客户端只提交查询并消费结果：

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

@@ -3,7 +3,7 @@ name: harness-plan
 description: 将需求转化为设计文档+实施计划+完整测试场景表，必须在编码前完成。仅当用户显式调用 /harness-plan 或明确要求进入
   Harness 规划阶段时使用；不得因用户描述需求就自动触发。
 ---
-<!-- generated by harness_deploy.py; core=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-plan — 需求规划
 
 ## Purpose

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

@@ -3,7 +3,7 @@ name: harness-pull
 description: 从 Hunter Platform 下拉配置/规则/架构/指令（及显式来源分支的分支文件恢复）。仅当用户显式调用
   /harness-pull 或明确说'从平台拉取/恢复'时使用；不得自动触发。
 ---
-<!-- generated by harness_deploy.py; core=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-pull — 从 Hunter Platform 下拉与恢复
 
 ## Purpose

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

@@ -3,7 +3,7 @@ name: harness-push
 description: 上传本地配置/规则/架构/指令（及显式归档）到 Hunter Platform。仅当用户显式调用 /harness-push
   或明确说'上传到平台'时使用；不得因存在本地修改就自动触发。
 ---
-<!-- generated by harness_deploy.py; core=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-push — 上传到 Hunter Platform
 
 ## Purpose
@@ -39,8 +39,22 @@ npx hunter-harness harness-push --scope archive --change <change-key> --json
 python <skills-root>/scripts/harness_archive.py republish --change <change-key> --json
 ```
 
+`<skills-root>` 是已部署 skills 的根目录，实际形态是 `.codebuddy/skills/`（`.claude`、`.cursor`、
+`.codex` 同理）。**脚本在它下面的 `scripts/` 里共享，不在 `harness-push/scripts/`** —— 已有四份
+执行日志先猜成后者、报 `No such file` 再回头找。
+
 `--scope archive` 没有待发布 claim 时返回 `PUSH_PULL_ARCHIVE_NO_PENDING_CLAIM`（exit 5），
 stderr 里直接给出上面的 republish 命令；`--dry-run` 会列出本地可补传的归档目录，不取租约。
+`republish` 在项目根内任意目录直接跑即可，**不需要** `--project`。
+
+**补传能做什么、不能做什么**：服务端对同一 change key 只保存**一个不可变包**。所以补传只适用于
+「从未成功上传」与「字节完全一致的重试」两种情况。若该 change 已是 durable，`republish` 会读
+`.harness/state/local/archive-packages/<key>.remote.json` 在**本地就判定**并返回：
+字节一致 → `ARCHIVE_ALREADY_PUBLISHED`（exit 0，不重传）；字节不同 →
+`ARCHIVE_REMOTE_IMMUTABLE_CONFLICT`（exit 1，**不发起上传**）。
+**已发布的归档无法从客户端补上知识条目**——注入 `candidates/knowledge.json` 必然改变字节，
+服务端拒绝替换。要让旧归档产生知识条目，需要平台侧提供重新索引或归档版本化能力。
+只想重试**同一个包**（例如知识索引失败）时加 `--no-knowledge-injection`，它按封存目录原样重建，字节与已存包一致。
 
 ## 关键规则
 

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

@@ -4,7 +4,7 @@ description: 6维度代码审查（架构/安全/规范/兼容/测试/性能）
   .harness/context-index.json）和测试场景表，在隔离上下文运行。仅当用户显式调用 /harness-review 时使用；不得在
   test 结束后自动接续执行。
 ---
-<!-- generated by harness_deploy.py; core=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-review — 代码审查
 
 ## Purpose

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

@@ -3,7 +3,7 @@ name: harness-run
 description: 按变更簇执行 TDD 编码循环（RED→GREEN→REFACTOR→编译验证），逐变更簇实现计划中的任务。仅当用户显式调用
   /harness-run 时使用；不得因用户提到编码/实现就自动触发，也不得被其他阶段 skill 自动接续。
 ---
-<!-- generated by harness_deploy.py; core=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-run — 需求编码
 
 ## Purpose

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

@@ -3,7 +3,7 @@ name: harness-submit
 description: 最终提交封装：验证→中文 commit→提交/推送；worktree 模式含 --no-ff 合并回主分支。仅当用户显式调用
   /harness-submit（或 /harness-merge 重入合并段）时使用；用户口头说'提交/commit/push'时必须先确认，不得自动触发。
 ---
-<!-- generated by harness_deploy.py; core=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-submit — 最终提交（含 worktree 合并）
 
 ## Purpose

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

@@ -4,7 +4,7 @@ description: Use when the user asks to synchronize, refresh, or validate Harness
   metadata, adapters, remote knowledge ownership, instruction entrypoints,
   config origins, or CodeGraph status.
 ---
-<!-- generated by harness_deploy.py; core=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-sync
 
 ## Purpose

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

@@ -3,7 +3,7 @@ name: harness-test
 description: 测试执行：读取场景表，执行单元测试+API接口测试+数据兼容验证，输出测试报告。仅当用户显式调用 /harness-test
   时使用；不得在 run 结束后自动接续执行。
 ---
-<!-- generated by harness_deploy.py; core=ef40ffbb4f999ea0; overlay=none; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=5fadb6520fbfa2c3; overlay=none; agent=codebuddy; do not edit -->
 # harness-test — 测试执行
 
 ## Purpose