@hunter-harness/workflow-harness 0.2.51 → 0.2.53

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

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

package/harness/bundles/java/cursor/harness-package/SKILL.md

@@ -2,7 +2,7 @@
 name: harness-package
 description: 增量模块打包：拉取最新→编译验证→mvn package→汇总 jar/war。仅当用户显式调用 /harness-package 时使用，不得自动触发。
 ---
-<!-- generated by harness_deploy.py; core=617d20b1a361f77b; overlay=java; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=653b0a7def92393b; overlay=java; agent=cursor; do not edit -->
 # harness-package — 增量模块打包（Java overlay）
 
 ## Purpose

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

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

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

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

package/harness/bundles/java/cursor/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=617d20b1a361f77b; overlay=java; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=653b0a7def92393b; overlay=java; agent=cursor; do not edit -->
 # harness-run — 需求编码
 
 ## Purpose

package/harness/bundles/java/cursor/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=617d20b1a361f77b; overlay=java; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=653b0a7def92393b; overlay=java; agent=cursor; do not edit -->
 # harness-submit — 最终提交（含 worktree 合并）
 
 ## Purpose

package/harness/bundles/java/cursor/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=617d20b1a361f77b; overlay=java; agent=cursor; do not edit -->
+<!-- generated by harness_deploy.py; core=653b0a7def92393b; overlay=java; agent=cursor; do not edit -->
 # harness-sync
 
 ## Purpose

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

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

package/harness/bundles/java/cursor/scripts/harness_events.py

@@ -33,6 +33,28 @@ if str(SCRIPTS_DIR) not in sys.path:
 import harness_paths  # noqa: E402
 
 
+def _project_root_for_change(change_dir: Path) -> Path | None:
+    resolved = change_dir.resolve()
+    for candidate in (resolved, *resolved.parents):
+        if candidate.name == "changes" and candidate.parent.name == ".harness":
+            return candidate.parent.parent
+    return None
+
+
+def _nudge_remote_sync(change_dir: Path) -> None:
+    """Best-effort wake-up after the event append has been flushed to disk."""
+    project_root = _project_root_for_change(change_dir)
+    if project_root is None:
+        return
+    try:
+        from harness_events_sync import schedule_events_sync
+
+        schedule_events_sync(project_root, change_dir)
+    except Exception:
+        # Local event durability is authoritative; remote outages never roll it back.
+        return
+
+
 if hasattr(sys.stdout, "reconfigure"):
     sys.stdout.reconfigure(encoding="utf-8")
 if hasattr(sys.stderr, "reconfigure"):
@@ -623,6 +645,7 @@ def append_event(
             "event": event,
             "autoSealed": result.get("autoSealed") or [],
         }
+    _nudge_remote_sync(change_dir)
     return {
         "ok": True,
         "event": event,
@@ -748,6 +771,7 @@ def batch_append_events(
             atomic_append_line(
                 events_path_obj, json.dumps(event, ensure_ascii=False, separators=(",", ":"))
             )
+    _nudge_remote_sync(change_dir)
     return {
         "ok": True,
         "action": "batch-append",
@@ -1796,6 +1820,8 @@ def cmd_append(args: argparse.Namespace) -> int:
             error_code=error_code,
         )
 
+    _nudge_remote_sync(change_dir)
+
     # §6.1: phase.end append（或写路径产生了 auto-seal）-> 追加成功后执行一次
     # render（从完整 events 重建 log）。普通 command/issue 等 append 不渲染
     # （O(1)）；显式 `render` 子命令随时重建。