@hunter-harness/workflow-harness 0.2.2 → 0.2.3

package/harness/bundles/general/codex/scripts/harness_check_gate.py

@@ -1,14 +1,15 @@
 #!/usr/bin/env python3
 """Pre-push gate: skip `npm run check` when a recent check-ok marker matches
-the current HEAD.
+the tree of the commit being pushed.
 
 Triple check (all must pass to skip, else exit 1 → hook runs npm run check):
   1. marker exists and its `ts` is within MAX_AGE_S (10 min) of now
   2. marker `command` == EXPECTED_CMD ("npm run check")
-  3. current `git rev-parse HEAD` == marker `commitHash`
+  3. current `git rev-parse HEAD^{tree}` == marker `treeHash`
 
-The marker is written by harness-submit M5 right after a green `npm run check`.
-Any mismatch (no marker, stale, different command, HEAD moved since the check)
+The marker is written by harness-submit M5 after a green `npm run check` and
+records `git write-tree`. This remains valid after commit because the new HEAD
+has the same tree. Any mismatch (no marker, stale, command or tree changed)
 forces a full re-run — the safe default. This is a local convenience only;
 non-harness pushes have no marker and always run the check.
 
@@ -28,10 +29,10 @@ MAX_AGE_S = 600  # 10 minutes
 EXPECTED_CMD = "npm run check"
 
 
-def _current_head() -> str | None:
+def _git_output(args: list[str]) -> str | None:
     try:
         r = subprocess.run(
-            ["git", "rev-parse", "HEAD"],
+            ["git", *args],
             cwd=str(ROOT),
             capture_output=True,
             text=True,
@@ -42,20 +43,27 @@ def _current_head() -> str | None:
     return r.stdout.strip() if r.returncode == 0 else None
 
 
+def _current_index_tree() -> str | None:
+    return _git_output(["write-tree"])
+
+
+def _current_head_tree() -> str | None:
+    return _git_output(["rev-parse", "HEAD^{tree}"])
+
+
 def write_marker() -> int:
-    """Write a check-ok marker for the current HEAD (called by harness-submit M5
-    after a green npm run check). Pre-push gate reads it to skip a re-run."""
-    head = _current_head()
-    if head is None:
+    """Record the verified index tree so the marker survives the next commit."""
+    tree = _current_index_tree()
+    if tree is None:
         return 1
     MARKER.parent.mkdir(parents=True, exist_ok=True)
-    payload = {"ts": time.time(), "commitHash": head, "command": EXPECTED_CMD}
+    payload = {"ts": time.time(), "treeHash": tree, "command": EXPECTED_CMD}
     MARKER.write_text(
         json.dumps(payload, ensure_ascii=False) + "\n",
         encoding="utf-8",
         newline="\n",
     )
-    print(f"check-ok marker written for HEAD {head[:7]}")
+    print(f"check-ok marker written for tree {tree[:7]}")
     return 0
 
 
@@ -84,17 +92,17 @@ def main(argv: list[str] | None = None) -> int:
         return 1
     if data.get("command") != EXPECTED_CMD:
         return 1
-    marker_commit = data.get("commitHash")
-    if not isinstance(marker_commit, str):
+    marker_tree = data.get("treeHash")
+    if not isinstance(marker_tree, str):
         return 1
-    head = _current_head()
-    if head is None or head != marker_commit:
+    tree = _current_head_tree()
+    if tree is None or tree != marker_tree:
         return 1
     # All three checks passed: a green npm run check ran on this exact HEAD
     # within the last 10 minutes. Safe to skip.
     print(
         f"pre-push: skipping npm run check (verified {int(time.time() - ts)}s ago "
-        f"at HEAD {head[:7]})"
+        f"for tree {tree[:7]})"
     )
     return 0
 

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

@@ -2,5 +2,5 @@
   "schemaVersion": 1,
   "overlay": "none",
   "agent": "cursor",
-  "coreHash": "507d66eba1aaf00e"
+  "coreHash": "bcff8a45420f1380"
 }

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

@@ -3,7 +3,7 @@ name: harness-archive
 description: 归档所有变更产出（计划/测试报告/审查/SQL/API文档）到
   .harness/archive/，含归档元数据和可视化最终总结。使用场景：归档、完成归档、收尾、打包产出物
 ---
-<!-- generated by harness_deploy.py; core=507d66eba1aaf00e; overlay=none; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=bcff8a45420f1380; overlay=none; agent=cursor; do not edit -->
 # harness-archive — 变更归档
 
 ## Purpose

package/harness/bundles/general/cursor/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=507d66eba1aaf00e; overlay=none; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=bcff8a45420f1380; overlay=none; agent=cursor; do not edit -->
 # harness-codebase-map — 代码库地图
 
 ## Purpose

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

@@ -3,7 +3,7 @@ name: harness-knowledge-ingest
 description: 从 .harness/archive 归档整理、同步和维护项目知识索引。适用场景：ingest knowledge、sync
   knowledge、rebuild knowledge index、promote knowledge、确认知识条目、检查知识库是否过期。
 ---
-<!-- generated by harness_deploy.py; core=507d66eba1aaf00e; overlay=none; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=bcff8a45420f1380; overlay=none; agent=cursor; do not edit -->
 # harness-knowledge-ingest
 
 从 `.harness/archive/**/reports/final/summary-data.json` 抽取项目知识，生成并维护本地 `.harness/knowledge/` 索引。

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

@@ -3,7 +3,7 @@ name: harness-knowledge-query
 description: 根据新需求、设计任务、代码修改请求或问题排查，在规划和编码前查询 .harness/knowledge
   历史上下文。适用场景：query knowledge、查找历史需求、根据归档理解需求、继续之前类似开发、生成需求上下文包。
 ---
-<!-- generated by harness_deploy.py; core=507d66eba1aaf00e; overlay=none; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=bcff8a45420f1380; overlay=none; agent=cursor; do not edit -->
 # harness-knowledge-query
 
 根据用户的新需求或排查问题，从项目本地 `.harness/knowledge` 中检索历史需求、决策、实现、风险和测试证据，并生成 AI 可读的 context pack。

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

@@ -2,7 +2,7 @@
 name: harness-plan
 description: 将需求转化为设计文档+实施计划+完整测试场景表，必须在编码前完成。使用场景：需求分析、feature plan、技术方案设计、实现方案规划
 ---
-<!-- generated by harness_deploy.py; core=507d66eba1aaf00e; overlay=none; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=bcff8a45420f1380; overlay=none; agent=cursor; do not edit -->
 # harness-plan — 需求规划
 
 ## Purpose

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

@@ -3,7 +3,7 @@ name: harness-review
 description: 6维度代码审查（架构/安全/规范/兼容/测试/性能），对照项目规则（见
   .harness/context-index.json）和测试场景表，在隔离上下文运行。使用场景：代码审查、提交前检查、合并评审
 ---
-<!-- generated by harness_deploy.py; core=507d66eba1aaf00e; overlay=none; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=bcff8a45420f1380; overlay=none; agent=cursor; do not edit -->
 # harness-review — 代码审查
 
 ## Purpose

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

@@ -2,7 +2,7 @@
 name: harness-run
 description: 按变更簇执行 TDD 编码循环（RED→GREEN→REFACTOR→编译验证），逐变更簇实现计划中的任务。使用场景：开始编码、实现功能、写代码、TDD 编码
 ---
-<!-- generated by harness_deploy.py; core=507d66eba1aaf00e; overlay=none; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=bcff8a45420f1380; overlay=none; agent=cursor; do not edit -->
 # harness-run — 需求编码
 
 ## Purpose

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

@@ -3,7 +3,7 @@ name: harness-submit
 description: 最终提交封装：验证→中文 commit→提交/推送；worktree 模式含 --no-ff
   合并回主分支。使用场景：提交代码、commit、push、合并分支、merge to main、完成开发
 ---
-<!-- generated by harness_deploy.py; core=507d66eba1aaf00e; overlay=none; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=bcff8a45420f1380; overlay=none; agent=cursor; do not edit -->
 # harness-submit — 最终提交（含 worktree 合并）
 
 ## Purpose

package/harness/bundles/general/cursor/harness-submit/checklist.md

@@ -380,14 +380,14 @@ powershell.exe -Command "git -C '<项目路径>' diff --name-only --diff-filter=
 
 重跑后写回 ledger 的 `compile`/`unitTest`，更新 `diffHash`/`currentHead`。
 
-**写 check-ok marker**（npm run check exit 0 后强制）：让 pre-push hook 跳过重复 check（省 ~350s）。三重校验（marker ts<10min + command + HEAD），任一不满足照跑。
+**写 check-ok marker**（npm run check exit 0 后强制）：让 pre-push hook 跳过重复 check。三重校验（marker ts<10min + command + commit tree），任一不满足照跑。marker 写入时记录 `git write-tree`，因此验证后创建 commit 不会仅因 HEAD 前移而使缓存失效。
 
 ```powershell
 # npm run check exit 0 后立即写 marker（M5 或 REUSED 后均可）
 powershell.exe -Command "python harness/scripts/harness_check_gate.py --write"
 ```
 
-> marker 写入 `.harness/check-ok.marker`（gitignored，本地）。push 时 pre-push hook 读 marker：HEAD 自写 marker 后未变 + ts<10min + command 匹配 → 跳过 npm run check；否则照跑（安全默认）。
+> marker 写入 `.harness/check-ok.marker`（gitignored，本地）。push 时 pre-push hook 比较 `HEAD^{tree}` 与 marker 的 `treeHash`，再校验 ts<10min + command；commit tree 未变化即可跳过，任何内容变化都照跑（安全默认）。
 
 ### 步骤 M6：push 主分支
 

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

@@ -2,7 +2,7 @@
 name: harness-sync
 description: 检查并更新项目AI元数据（CodeGraph索引、harness-codebase-map分析、CLAUDE.md、AGENTS.md、.harness/完整性），确保Claude对代码库的理解与最新代码一致。当用户说'同步/更新索引/刷新元数据/检查一致性'时使用
 ---
-<!-- generated by harness_deploy.py; core=507d66eba1aaf00e; overlay=none; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=bcff8a45420f1380; overlay=none; agent=cursor; do not edit -->
 # harness-sync — 元数据同步
 
 ## Purpose

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

@@ -2,7 +2,7 @@
 name: harness-test
 description: 测试执行：读取场景表，执行单元测试+API接口测试+数据兼容验证，输出测试报告。当用户说'跑测试/验证/跑用例/接口测试/单元测试'时使用
 ---
-<!-- generated by harness_deploy.py; core=507d66eba1aaf00e; overlay=none; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=bcff8a45420f1380; overlay=none; agent=cursor; do not edit -->
 # harness-test — 测试执行
 
 ## Purpose

package/harness/bundles/general/cursor/scripts/harness_check_gate.py

@@ -1,14 +1,15 @@
 #!/usr/bin/env python3
 """Pre-push gate: skip `npm run check` when a recent check-ok marker matches
-the current HEAD.
+the tree of the commit being pushed.
 
 Triple check (all must pass to skip, else exit 1 → hook runs npm run check):
   1. marker exists and its `ts` is within MAX_AGE_S (10 min) of now
   2. marker `command` == EXPECTED_CMD ("npm run check")
-  3. current `git rev-parse HEAD` == marker `commitHash`
+  3. current `git rev-parse HEAD^{tree}` == marker `treeHash`
 
-The marker is written by harness-submit M5 right after a green `npm run check`.
-Any mismatch (no marker, stale, different command, HEAD moved since the check)
+The marker is written by harness-submit M5 after a green `npm run check` and
+records `git write-tree`. This remains valid after commit because the new HEAD
+has the same tree. Any mismatch (no marker, stale, command or tree changed)
 forces a full re-run — the safe default. This is a local convenience only;
 non-harness pushes have no marker and always run the check.
 
@@ -28,10 +29,10 @@ MAX_AGE_S = 600  # 10 minutes
 EXPECTED_CMD = "npm run check"
 
 
-def _current_head() -> str | None:
+def _git_output(args: list[str]) -> str | None:
     try:
         r = subprocess.run(
-            ["git", "rev-parse", "HEAD"],
+            ["git", *args],
             cwd=str(ROOT),
             capture_output=True,
             text=True,
@@ -42,20 +43,27 @@ def _current_head() -> str | None:
     return r.stdout.strip() if r.returncode == 0 else None
 
 
+def _current_index_tree() -> str | None:
+    return _git_output(["write-tree"])
+
+
+def _current_head_tree() -> str | None:
+    return _git_output(["rev-parse", "HEAD^{tree}"])
+
+
 def write_marker() -> int:
-    """Write a check-ok marker for the current HEAD (called by harness-submit M5
-    after a green npm run check). Pre-push gate reads it to skip a re-run."""
-    head = _current_head()
-    if head is None:
+    """Record the verified index tree so the marker survives the next commit."""
+    tree = _current_index_tree()
+    if tree is None:
         return 1
     MARKER.parent.mkdir(parents=True, exist_ok=True)
-    payload = {"ts": time.time(), "commitHash": head, "command": EXPECTED_CMD}
+    payload = {"ts": time.time(), "treeHash": tree, "command": EXPECTED_CMD}
     MARKER.write_text(
         json.dumps(payload, ensure_ascii=False) + "\n",
         encoding="utf-8",
         newline="\n",
     )
-    print(f"check-ok marker written for HEAD {head[:7]}")
+    print(f"check-ok marker written for tree {tree[:7]}")
     return 0
 
 
@@ -84,17 +92,17 @@ def main(argv: list[str] | None = None) -> int:
         return 1
     if data.get("command") != EXPECTED_CMD:
         return 1
-    marker_commit = data.get("commitHash")
-    if not isinstance(marker_commit, str):
+    marker_tree = data.get("treeHash")
+    if not isinstance(marker_tree, str):
         return 1
-    head = _current_head()
-    if head is None or head != marker_commit:
+    tree = _current_head_tree()
+    if tree is None or tree != marker_tree:
         return 1
     # All three checks passed: a green npm run check ran on this exact HEAD
     # within the last 10 minutes. Safe to skip.
     print(
         f"pre-push: skipping npm run check (verified {int(time.time() - ts)}s ago "
-        f"at HEAD {head[:7]})"
+        f"for tree {tree[:7]})"
     )
     return 0
 

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

@@ -2,5 +2,5 @@
   "schemaVersion": 1,
   "overlay": "java",
   "agent": "claude-code",
-  "coreHash": "37b62b2fa19bf00f"
+  "coreHash": "959b22fdc1e7af33"
 }

package/harness/bundles/java/claude-code/harness-apidoc/SKILL.md

@@ -20,7 +20,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=claude-code; do not edit -->
 # harness-apidoc — 前端接口文档（Java overlay）
 
 ## Purpose

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

@@ -20,7 +20,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=claude-code; do not edit -->
 # harness-archive — 变更归档
 
 ## Purpose

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

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

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

@@ -20,7 +20,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=claude-code; do not edit -->
 # harness-knowledge-ingest
 
 从 `.harness/archive/**/reports/final/summary-data.json` 抽取项目知识，生成并维护本地 `.harness/knowledge/` 索引。

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

@@ -20,7 +20,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=claude-code; do not edit -->
 # harness-knowledge-query
 
 根据用户的新需求或排查问题，从项目本地 `.harness/knowledge` 中检索历史需求、决策、实现、风险和测试证据，并生成 AI 可读的 context pack。

package/harness/bundles/java/claude-code/harness-package/SKILL.md

@@ -20,7 +20,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=claude-code; do not edit -->
 # harness-package — 增量模块打包（Java overlay）
 
 ## Purpose

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

@@ -20,7 +20,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=claude-code; do not edit -->
 # harness-plan — 需求规划
 
 ## Purpose

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

@@ -21,7 +21,7 @@ disallowed-tools:
   - Bash(curl *)
   - Bash(codegraph *)
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=claude-code; do not edit -->
 # harness-review — 代码审查
 
 ## Purpose

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

@@ -21,7 +21,7 @@ disallowed-tools:
   - Bash(curl *)
   - Bash(codegraph *)
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=claude-code; do not edit -->
 # harness-run — 需求编码
 
 ## Purpose

package/harness/bundles/java/claude-code/harness-run/checklist.md

@@ -30,6 +30,8 @@
 - [ ] **读取任务状态**：`.harness/changes/<change>/run-task-status.md`（如存在）— 恢复上次运行状态
 - [ ] 确认 `项目规则（见 .harness/context-index.json）/` 规则已加载
 - [ ] 检查构建配置完整性（worktree 中确认 `.mvn/maven.config`、`settings.xml` 等存在）
+- [ ] 读取 `.mvn/maven.config`，确认命令没有重复或覆盖项目已有的 `-s` / `-o` / 仓库设置
+- [ ] 离线依赖缺失时仅在项目规则允许联网的前提下执行至多一次非离线 `-nsu` 恢复；禁止离线/联网循环重试
 - [ ] 依赖模块预安装（worktree 中检查上游模块是否已 `mvn install`）
 - [ ] 代码探索优先用 `codegraph_explore`，仅在返回不完整时补充 Read
 - [ ] append `phase.start`（`note` 含测试基础设施 CHECKING 直至探测完成）

package/harness/bundles/java/claude-code/harness-run/reference.md

@@ -97,6 +97,12 @@ powershell.exe -NoProfile -Command "Test-Path '.claude/worktrees/<change-name>/.
 13. **依赖模块预安装**：如果在 worktree 中执行，检查上游依赖模块是否已 `mvn install` 到本地仓库。缺失时先执行 `powershell.exe -Command "mvn install -pl <upstream-modules> -am -DskipTests -nsu"`
 14. **代码探索优先用 codegraph_explore**：一次调用可获取多个相关符号的源码，替代逐个 Read 文件。违反 `项目 codegraph 规则` 规则逐个 Read 会浪费 3-5 分钟。仅在 codegraph 返回结果不完整时补充 Read
 
+### Maven 项目配置与重试预算
+
+- 运行 Maven 前先读取项目已有的 `.mvn/maven.config`；其中的 `-s`、`-o`、镜像和仓库设置视为项目契约，不在命令行重复追加或覆盖。
+- 若项目配置已启用离线模式，依赖缺失只允许一次有明确原因的恢复尝试：仅在项目规则允许联网时临时执行非离线的 `-nsu` 命令；随后继续遵循项目配置，不得在离线/联网命令之间循环试错。
+- 同一失败命令不得无分析地重复执行。先按“配置/依赖缺失、编译、测试、业务断言”分类，再决定修复或停止；每个变更簇仍遵守一次 RED、一次 GREEN 的 Maven 预算。
+
 ### 步骤 0.1：执行模式（默认 Inline）
 
 默认 **Inline Execution**；仅 `--subagent` 强制 Subagent-Driven。**不询问**任务数/模块数（P1-5）。

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

@@ -20,7 +20,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=claude-code; do not edit -->
 # harness-submit — 最终提交（含 worktree 合并）
 
 ## Purpose

package/harness/bundles/java/claude-code/harness-submit/checklist.md

@@ -380,14 +380,14 @@ powershell.exe -Command "git -C '<项目路径>' diff --name-only --diff-filter=
 
 重跑后写回 ledger 的 `compile`/`unitTest`，更新 `diffHash`/`currentHead`。
 
-**写 check-ok marker**（npm run check exit 0 后强制）：让 pre-push hook 跳过重复 check（省 ~350s）。三重校验（marker ts<10min + command + HEAD），任一不满足照跑。
+**写 check-ok marker**（npm run check exit 0 后强制）：让 pre-push hook 跳过重复 check。三重校验（marker ts<10min + command + commit tree），任一不满足照跑。marker 写入时记录 `git write-tree`，因此验证后创建 commit 不会仅因 HEAD 前移而使缓存失效。
 
 ```powershell
 # npm run check exit 0 后立即写 marker（M5 或 REUSED 后均可）
 powershell.exe -Command "python harness/scripts/harness_check_gate.py --write"
 ```
 
-> marker 写入 `.harness/check-ok.marker`（gitignored，本地）。push 时 pre-push hook 读 marker：HEAD 自写 marker 后未变 + ts<10min + command 匹配 → 跳过 npm run check；否则照跑（安全默认）。
+> marker 写入 `.harness/check-ok.marker`（gitignored，本地）。push 时 pre-push hook 比较 `HEAD^{tree}` 与 marker 的 `treeHash`，再校验 ts<10min + command；commit tree 未变化即可跳过，任何内容变化都照跑（安全默认）。
 
 ### 步骤 M6：push 主分支
 

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

@@ -19,7 +19,7 @@ disallowed-tools:
   - Bash(awk *)
   - Bash(curl *)
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=claude-code; do not edit -->
 # harness-sync — 元数据同步
 
 ## Purpose

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

@@ -22,7 +22,7 @@ disallowed-tools:
   - Bash(node *)
   - Bash(codegraph *)
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=claude-code; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=claude-code; do not edit -->
 # harness-test — 测试执行
 
 ## Purpose

package/harness/bundles/java/claude-code/harness-test/checklist.md

@@ -37,6 +37,8 @@ description: harness-test 的 Phase 0 环境准备 + Playwright 探测 + 关门
 - [ ] 检查 PowerShell 基础命令：`powershell.exe -NoProfile -Command "$PSVersionTable.PSVersion"` 返回 exitCode=0
 - [ ] 检查 Node 绝对路径：`powershell.exe -NoProfile -Command "& 'C:\nvm4w\nodejs\node.exe' --version"` 返回 exitCode=0
 - [ ] 检查 Maven 可用性：`powershell.exe -NoProfile -Command "mvn -version"` 返回 exitCode=0
+- [ ] 读取 `.mvn/maven.config`，Maven 命令不重复或覆盖已有 `-s` / `-o` / 仓库设置
+- [ ] 离线依赖缺失时仅在项目规则允许联网时执行至多一次非离线 `-nsu` 恢复；失败后停止，禁止切换参数反复重试
 - [ ] 检查安全分类器：上述任一命令是否返回"安全分类器暂时不可用" / Auto mode 拦截 → **不应出现**
 - [ ] 将通过的 `nodeAbsolutePath` / `powershellVersion` / `mvnVersion` 写入 `.harness/changes/<change-name>/runtime/preflight.json`
 - [ ] **任一情况触发硬停**：原文输出"❌ 命令执行模式不可用：PowerShell/Node runner 无法稳定执行..."，**不得继续编译/启动服务/生成 runner，不得长时间等待，不得盲目降级到 Playwright MCP**
@@ -314,4 +316,4 @@ powershell.exe -Command "Copy-Item '<main-dir>/<module>/src/main/resources/appli
 - 请求执行器必须在报告中明确记录（四种执行器，含降级原因）
 - 请求耗时统计必须包含在报告中
 - 服务由 AI 启动的情况，测试结束默认 Stop-Process；**即使测试失败也要进入 finally 清理**
-- final-summary 的 apiTest 状态必须用 OK/PARTIAL/BLOCKED/NOT_RUN/FAIL（不得把 PARTIAL 写成 NOT_RUN）
+- final-summary 的 apiTest 状态必须用 OK/PARTIAL/BLOCKED/NOT_RUN/FAIL（不得把 PARTIAL 写成 NOT_RUN）

package/harness/bundles/java/claude-code/harness-test/reference.md

@@ -6,6 +6,8 @@ description: harness-test 的 API 测试执行细节、批量 runner、token 缓
 
 ## 命令执行模式 preflight（0.0y）
 
+执行 Maven 前必须读取 `.mvn/maven.config`。项目已声明的 `-s`、`-o`、镜像和仓库设置不得被测试命令重复追加或覆盖。离线依赖缺失时，只有在项目规则允许联网的情况下，才可临时执行至多一次非离线 `-nsu` 恢复；失败后停止并报告缺失依赖，不得在多套 Maven 参数间反复试跑。
+
 `/harness-test` 高度依赖 PowerShell 与 Node。在编译/启动服务/生成 runner **之前**
 必须执行 4 项执行模式检查：
 

package/harness/bundles/java/claude-code/scripts/harness_check_gate.py

@@ -1,14 +1,15 @@
 #!/usr/bin/env python3
 """Pre-push gate: skip `npm run check` when a recent check-ok marker matches
-the current HEAD.
+the tree of the commit being pushed.
 
 Triple check (all must pass to skip, else exit 1 → hook runs npm run check):
   1. marker exists and its `ts` is within MAX_AGE_S (10 min) of now
   2. marker `command` == EXPECTED_CMD ("npm run check")
-  3. current `git rev-parse HEAD` == marker `commitHash`
+  3. current `git rev-parse HEAD^{tree}` == marker `treeHash`
 
-The marker is written by harness-submit M5 right after a green `npm run check`.
-Any mismatch (no marker, stale, different command, HEAD moved since the check)
+The marker is written by harness-submit M5 after a green `npm run check` and
+records `git write-tree`. This remains valid after commit because the new HEAD
+has the same tree. Any mismatch (no marker, stale, command or tree changed)
 forces a full re-run — the safe default. This is a local convenience only;
 non-harness pushes have no marker and always run the check.
 
@@ -28,10 +29,10 @@ MAX_AGE_S = 600  # 10 minutes
 EXPECTED_CMD = "npm run check"
 
 
-def _current_head() -> str | None:
+def _git_output(args: list[str]) -> str | None:
     try:
         r = subprocess.run(
-            ["git", "rev-parse", "HEAD"],
+            ["git", *args],
             cwd=str(ROOT),
             capture_output=True,
             text=True,
@@ -42,20 +43,27 @@ def _current_head() -> str | None:
     return r.stdout.strip() if r.returncode == 0 else None
 
 
+def _current_index_tree() -> str | None:
+    return _git_output(["write-tree"])
+
+
+def _current_head_tree() -> str | None:
+    return _git_output(["rev-parse", "HEAD^{tree}"])
+
+
 def write_marker() -> int:
-    """Write a check-ok marker for the current HEAD (called by harness-submit M5
-    after a green npm run check). Pre-push gate reads it to skip a re-run."""
-    head = _current_head()
-    if head is None:
+    """Record the verified index tree so the marker survives the next commit."""
+    tree = _current_index_tree()
+    if tree is None:
         return 1
     MARKER.parent.mkdir(parents=True, exist_ok=True)
-    payload = {"ts": time.time(), "commitHash": head, "command": EXPECTED_CMD}
+    payload = {"ts": time.time(), "treeHash": tree, "command": EXPECTED_CMD}
     MARKER.write_text(
         json.dumps(payload, ensure_ascii=False) + "\n",
         encoding="utf-8",
         newline="\n",
     )
-    print(f"check-ok marker written for HEAD {head[:7]}")
+    print(f"check-ok marker written for tree {tree[:7]}")
     return 0
 
 
@@ -84,17 +92,17 @@ def main(argv: list[str] | None = None) -> int:
         return 1
     if data.get("command") != EXPECTED_CMD:
         return 1
-    marker_commit = data.get("commitHash")
-    if not isinstance(marker_commit, str):
+    marker_tree = data.get("treeHash")
+    if not isinstance(marker_tree, str):
         return 1
-    head = _current_head()
-    if head is None or head != marker_commit:
+    tree = _current_head_tree()
+    if tree is None or tree != marker_tree:
         return 1
     # All three checks passed: a green npm run check ran on this exact HEAD
     # within the last 10 minutes. Safe to skip.
     print(
         f"pre-push: skipping npm run check (verified {int(time.time() - ts)}s ago "
-        f"at HEAD {head[:7]})"
+        f"for tree {tree[:7]})"
     )
     return 0
 

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

@@ -2,5 +2,5 @@
   "schemaVersion": 1,
   "overlay": "java",
   "agent": "codebuddy",
-  "coreHash": "37b62b2fa19bf00f"
+  "coreHash": "959b22fdc1e7af33"
 }

package/harness/bundles/java/codebuddy/harness-apidoc/SKILL.md

@@ -2,7 +2,7 @@
 name: harness-apidoc
 description: 从 Java 后端代码生成结构化前端 API 文档（Controller/VO/ErrorCode）。使用场景：接口文档、前端接口文档、API 文档生成
 ---
-<!-- generated by harness_deploy.py; core=37b62b2fa19bf00f; overlay=java; agent=codebuddy; do not edit -->
+<!-- generated by harness_deploy.py; core=959b22fdc1e7af33; overlay=java; agent=codebuddy; do not edit -->
 # harness-apidoc — 前端接口文档（Java overlay）
 
 ## Purpose