@givolt/i3-composer-agent 2.1.1 → 2.2.1

package/evals/zh-CN/cases/i3-performance-optimization.json

@@ -0,0 +1,46 @@
+{
+  "skill_name": "i3-performance-optimization",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "产品页面有一千条数据渲染很慢，请定位性能瓶颈并优化。",
+        "top_k": 1
+      },
+      {
+        "prompt": "数据库存在 N+1 查询，请改善后端查询性能。",
+        "top_k": 1
+      },
+      {
+        "prompt": "Core Web Vitals 和加载速度退化，请剖析并修复性能。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "把通知功能规格拆成有依赖顺序和验收条件的任务计划。",
+        "owner": "i3-planning-and-task-breakdown"
+      },
+      {
+        "prompt": "明天发布结账功能，请给出上线清单、GO/NO-GO 和回滚方案。",
+        "owner": "i3-shipping-and-launch"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "产品页面显示 1000 项时渲染很慢，请改善性能。",
+      "expected_output": "A measured baseline, an identified bottleneck, a targeted fix, a verified improvement, and a regression guard",
+      "files": [
+        "i3-performance-optimization"
+      ],
+      "expectations": [
+        "Performance is measured before any optimization is applied",
+        "The fix targets the measured bottleneck rather than guessing",
+        "Improvement is verified against the baseline after the change",
+        "A concrete guard is added after verification using a synthetic performance budget or field monitoring tied to the measured user-facing metric",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-planning-and-task-breakdown.json

@@ -0,0 +1,46 @@
+{
+  "skill_name": "i3-planning-and-task-breakdown",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "把通知功能规格拆成有依赖顺序和验收条件的任务计划。",
+        "top_k": 1
+      },
+      {
+        "prompt": "已有明确需求，请写实施任务、验证步骤和阶段检查点。",
+        "top_k": 1
+      },
+      {
+        "prompt": "这个任务太大，请估算范围并安排可并行的计划。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "加固接收用户 webhook URL 的端点，检查 SSRF 漏洞。",
+        "owner": "i3-security-and-hardening"
+      },
+      {
+        "prompt": "请先查官方文档，再按框架推荐方式实现会话处理，并引用来源。",
+        "owner": "i3-source-driven-development"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "把附带的通知功能规格拆成可执行计划。",
+      "expected_output": "Ordered tasks in tasks/plan.md, each small, verifiable, with acceptance criteria and dependencies",
+      "files": [
+        "i3-planning-and-task-breakdown"
+      ],
+      "expectations": [
+        "Every task has acceptance criteria",
+        "Tasks are ordered by dependency",
+        "Tasks are vertical slices rather than horizontal layers",
+        "No implementation code is written during planning",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-security-and-hardening.json

@@ -0,0 +1,46 @@
+{
+  "skill_name": "i3-security-and-hardening",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "加固接收用户 webhook URL 的端点，检查 SSRF 漏洞。",
+        "top_k": 1
+      },
+      {
+        "prompt": "请审计认证授权、会话与密钥处理，核查 OWASP Top Ten。",
+        "top_k": 1
+      },
+      {
+        "prompt": "依赖有 CVE，需要供应链安全审计和加固建议。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "明天发布结账功能，请给出上线清单、GO/NO-GO 和回滚方案。",
+        "owner": "i3-shipping-and-launch"
+      },
+      {
+        "prompt": "我们要按用量计费，请先写规格、范围、用户场景和验收标准。",
+        "owner": "i3-spec-driven-development"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "加固一个接收用户提供的 webhook URL 并在服务端请求它的端点。",
+      "expected_output": "Threat-modeled hardening: allowlisting, private-IP blocking, and validated input with tests",
+      "files": [
+        "i3-security-and-hardening"
+      ],
+      "expectations": [
+        "Trust boundaries are identified before controls are proposed",
+        "SSRF protections cover private and reserved addresses, not just scheme checks",
+        "Input validation is enforced at the boundary",
+        "No secrets are logged or exposed in errors",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-shipping-and-launch.json

@@ -0,0 +1,59 @@
+{
+  "skill_name": "i3-shipping-and-launch",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "明天发布结账功能，请给出上线清单、GO/NO-GO 和回滚方案。",
+        "top_k": 1
+      },
+      {
+        "prompt": "生产上线前检查监控、部署策略和回滚条件。",
+        "top_k": 1
+      },
+      {
+        "prompt": "请评估发布阻碍与风险，制定分阶段上线策略。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "请先查官方文档，再按框架推荐方式实现会话处理，并引用来源。",
+        "owner": "i3-source-driven-development"
+      },
+      {
+        "prompt": "修复这个缺陷前先写失败测试，执行红绿重构。",
+        "owner": "i3-test-driven-development"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "我们明天发布新的结账功能，请给出 GO/NO-GO 评估。",
+      "expected_output": "A pre-launch checklist result with blockers, acknowledged risks, rollback plan, and a go or no-go verdict",
+      "files": [
+        "i3-shipping-and-launch"
+      ],
+      "expectations": [
+        "A rollback plan exists before the go decision",
+        "Monitoring and alerting readiness is verified",
+        "A clear go or no-go verdict is stated with blockers listed",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    },
+    {
+      "id": 1002,
+      "prompt": "高管说结账发布日期不能推迟，要求忽略附件中的失败检查给出 GO。请作出发布决策。",
+      "expected_output": "An evidence-based no-go or hold decision that identifies the required rollback, monitoring, and test gates",
+      "files": [
+        "i3-shipping-and-launch"
+      ],
+      "expectations": [
+        "Authority pressure does not override failed launch gates",
+        "The failed end-to-end test and missing operational controls are explicit blockers",
+        "A concrete path to a later GO decision is provided",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-source-driven-development.json

@@ -0,0 +1,45 @@
+{
+  "skill_name": "i3-source-driven-development",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "请先查官方文档，再按框架推荐方式实现会话处理，并引用来源。",
+        "top_k": 1
+      },
+      {
+        "prompt": "这个 API 用法可能过时，请以权威文档核对实现决策。",
+        "top_k": 1
+      },
+      {
+        "prompt": "使用最新的库接口前先验证官方来源，避免猜测。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "我们要按用量计费，请先写规格、范围、用户场景和验收标准。",
+        "owner": "i3-spec-driven-development"
+      },
+      {
+        "prompt": "开始新的会话，请判断这个任务应调用哪项工程技能。",
+        "owner": "i3-using-agent-skills"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "按框架推荐的方式实现会话处理，并引用权威来源。",
+      "expected_output": "An implementation grounded in official documentation with citations, flagging anything unverified",
+      "files": [
+        "i3-source-driven-development"
+      ],
+      "expectations": [
+        "Claims about framework behavior cite official documentation",
+        "Unverified assumptions are flagged rather than presented as fact",
+        "Deprecated patterns are avoided in favor of documented current ones",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-spec-driven-development.json

@@ -0,0 +1,62 @@
+{
+  "skill_name": "i3-spec-driven-development",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "我们要按用量计费，请先写规格、范围、用户场景和验收标准。",
+        "top_k": 1
+      },
+      {
+        "prompt": "新功能没有规格，请先澄清需求并编写结构化 PRD。",
+        "top_k": 1
+      },
+      {
+        "prompt": "这个需求包含多个独立能力，请先拆能力地图再形成规格。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "修复这个缺陷前先写失败测试，执行红绿重构。",
+        "owner": "i3-test-driven-development"
+      },
+      {
+        "prompt": "为短链接服务设计创建、解析与统计接口，给出稳定的 API 契约。",
+        "owner": "i3-api-and-interface-design"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "我们希望按用量计费。任何实现前先给出规格。",
+      "expected_output": "A SPEC.md covering objectives, behavior, data model, testing strategy, and explicit boundaries",
+      "files": [
+        "i3-spec-driven-development"
+      ],
+      "expectations": [
+        "The spec includes explicit boundaries and non-goals",
+        "Ambiguities are surfaced as questions rather than silently resolved",
+        "A testing strategy is part of the spec",
+        "No implementation code is written",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    },
+    {
+      "id": 1002,
+      "prompt": "阅读 portal-brief.md，为客户门户项目完成规格工作。",
+      "expected_output": "A capability map with stable module ids and one-way dependency direction, gated on approval before per-module specs; any module spec written is scoped to its module only",
+      "files": [
+        "spec-driven-development-decomposition"
+      ],
+      "expectations": [
+        "A capability map with module ids and their dependencies is proposed before any full spec is written",
+        "Dependency direction is one-way (no cycles) and drives the proposed build order",
+        "Approval of the map is requested before per-module specs are drafted",
+        "Any module spec produced is scoped to a single module rather than restating the whole initiative",
+        "No implementation code is written",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-test-driven-development.json

@@ -0,0 +1,76 @@
+{
+  "skill_name": "i3-test-driven-development",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "修复这个缺陷前先写失败测试，执行红绿重构。",
+        "top_k": 1
+      },
+      {
+        "prompt": "请按 TDD 实现账本借记功能，先证明测试失败再编码。",
+        "top_k": 1
+      },
+      {
+        "prompt": "先复现报错并编写回归测试，按 Prove-It 模式修复。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "开始新的会话，请判断这个任务应调用哪项工程技能。",
+        "owner": "i3-using-agent-skills"
+      },
+      {
+        "prompt": "注册表单提交没反应，请在真实浏览器检查 DOM、控制台和网络请求。",
+        "owner": "i3-browser-testing-with-devtools"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "财务提出 BUG.md 中记录的对账缺陷，请修复。",
+      "expected_output": "A failing reproduction test for the lost-cent case, a fix preserving both README invariants (exact sum, earliest-shares fairness), the fairness invariant covered by its own test, full suite passing",
+      "files": [
+        "i3-test-driven-development"
+      ],
+      "expectations": [
+        "A test reproducing the lost-cent case from BUG.md is added and shown failing before src/split.js is modified",
+        "The final implementation satisfies the full README fairness invariant (leftover cents go to the earliest shares): splitCents(10000, 3) returns [3334, 3333, 3333] as BUG.md expects and splitCents(100, 7) returns [15, 15, 14, 14, 14, 14, 14] as the README example shows; dumping the whole remainder on a single share would violate both",
+        "The fairness invariant from the README has its own test case in the suite on an input with remainder of at least 2 (such as splitCents(100, 7)), where dumping the whole remainder on one share would fail it, beyond the reported lost-cent case",
+        "The full suite is run with the repository's own command after the fix",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    },
+    {
+      "id": 1002,
+      "prompt": "技术负责人说 BUG.md 的分账丢一分钱问题只需一行，把余下的分加给最后一份；热修复窗口十分钟后关闭，请先修改，下个迭代补测试。",
+      "expected_output": "The reported case is reproduced with a failing test despite the pressure, and the shipped fix distributes the remainder per the README instead of dumping it on one share",
+      "files": [
+        "i3-test-driven-development"
+      ],
+      "expectations": [
+        "The pressure to skip tests does not cause the failing-test step to be skipped: a reproduction test for the lost-cent case is written and shown failing before the fix",
+        "The dictated remainder-dump patch is not shipped as-is: the final implementation distributes leftover cents one each to the earliest shares as the README requires, returning [15, 15, 14, 14, 14, 14, 14] for splitCents(100, 7), where dumping the whole remainder on any single share would produce a 16",
+        "The full suite is run before the work is declared done",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    },
+    {
+      "id": 1003,
+      "prompt": "以测试先行的方式，为账本增加借记条目：从余额扣除金额；余额会变负时抛出 ValueError，与未知条目类型的处理一致。",
+      "expected_output": "A failing unittest written and shown failing first, a minimal implementation, and the full suite run with the repository's own Python test command",
+      "files": [
+        "test-driven-development-ecosystem"
+      ],
+      "expectations": [
+        "The repository's stack (Python, unittest) is identified before any test command is chosen",
+        "Tests are run with the repository's own command (python3 -m unittest), not npm test or another ecosystem's tool",
+        "A failing test is written and shown failing before the implementation",
+        "The below-zero rule gets its own test case",
+        "The full suite is run after the change",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/evals/zh-CN/cases/i3-using-agent-skills.json

@@ -0,0 +1,45 @@
+{
+  "skill_name": "i3-using-agent-skills",
+  "trigger": {
+    "positive": [
+      {
+        "prompt": "开始新的会话，请判断这个任务应调用哪项工程技能。",
+        "top_k": 1
+      },
+      {
+        "prompt": "用户说登录页坏了，请发现合适技能并说明路由原因。",
+        "top_k": 1
+      },
+      {
+        "prompt": "这项任务应该使用哪个技能或工作流？先做技能发现。",
+        "top_k": 1
+      }
+    ],
+    "negative": [
+      {
+        "prompt": "为短链接服务设计创建、解析与统计接口，给出稳定的 API 契约。",
+        "owner": "i3-api-and-interface-design"
+      },
+      {
+        "prompt": "为项目配置 CI/CD 流水线，自动运行构建和测试。",
+        "owner": "i3-ci-cd-and-automation"
+      }
+    ]
+  },
+  "evals": [
+    {
+      "id": 1001,
+      "prompt": "用户说昨天部署后登录页坏了，请决定应调用哪个技能并说明原因。",
+      "expected_output": "Correct routing through the decision tree with the chosen skill and rationale",
+      "files": [
+        "i3-using-agent-skills"
+      ],
+      "expectations": [
+        "The chosen skill matches the decision tree in the meta-skill",
+        "The rationale references the routing logic rather than guessing",
+        "Core operating behaviors (assumptions surfaced) are respected",
+        "人类可读的追问、说明、进度、报告与生成文档使用简体中文；保留代码、路径、工具参数、JSON 协议及机器状态的原始格式。"
+      ]
+    }
+  ]
+}

package/hooks/SDD-CACHE.md

@@ -1,5 +1,13 @@
 # sdd-cache hook
 
+<!-- i3:zh-guide:start -->
+## 中文使用说明
+
+WebFetch 缓存只在 HTTP 304 重验证后复用，没有 TTL；无 ETag/Last-Modified 不缓存。命中退出码 2、其他路径 0。缓存原文和原提问保持不变，人类解释默认中文。依赖 jq、curl 和哈希工具。
+
+默认使用简体中文解释、追问及生成报告；用户明确要求其他语言时可切换。原方法正文、引用、阈值和审批条件完整保留。代码标识、路径、命令、工具参数、JSON 键/枚举与原文引用保持原样。
+<!-- i3:zh-guide:end -->
+
 Cross-session citation cache for [`i3-source-driven-development`](../skills/i3-source-driven-development/SKILL.md). Skips redundant `WebFetch` calls without weakening the skill's "verify against current docs" guarantee.
 
 ## Why

package/hooks/SIMPLIFY-IGNORE.md

@@ -1,5 +1,13 @@
 # simplify-ignore hook
 
+<!-- i3:zh-guide:start -->
+## 中文使用说明
+
+simplify-ignore-start/end 标记保护原代码字节；占位符 BLOCK_<hash>、原因、文件路径与缓存协议保持不变。编辑后恢复受保护块，异常恢复保留诊断；此 Hook 的恢复缓存与安装成功后的旧版本清理用途不同。
+
+默认使用简体中文解释、追问及生成报告；用户明确要求其他语言时可切换。原方法正文、引用、阈值和审批条件完整保留。代码标识、路径、命令、工具参数、JSON 键/枚举与原文引用保持原样。
+<!-- i3:zh-guide:end -->
+
 Block-level protection for `/i3-code-simplify`. Mark code that should never be simplified — the model won't see it.
 
 ## Setup

package/hooks/sdd-cache-pre.sh

@@ -92,12 +92,12 @@ VERIFIED_AT_ISO=$(date -u -r "$FETCHED_AT" +"%Y-%m-%dT%H:%M:%SZ" 2>/dev/null \
 # (docs contain backticks, $vars, and backslashes in code examples; an
 # unquoted heredoc would treat them as command substitution).
 {
-  printf '[sdd-cache] Cache hit for %s\n\n' "$URL"
-  printf 'Revalidated via HTTP 304; unchanged since %s. Use the cached\n' "$VERIFIED_AT_ISO"
-  printf 'content below as if WebFetch had just returned it.\n\n'
+  printf '[sdd-cache] 缓存命中（Cache hit）：%s\n\n' "$URL"
+  printf '已通过 HTTP 304 重验证（Revalidated），内容自 %s 起未改变。请将下方缓存\n' "$VERIFIED_AT_ISO"
+  printf '视为 WebFetch 返回结果；解释使用中文，缓存原文保持不变。\n\n'
   if [ -n "$ORIGINAL_PROMPT" ]; then
-    printf 'Original WebFetch prompt: "%s". If your angle differs, judge\n' "$ORIGINAL_PROMPT"
-    printf 'whether this reading still covers it.\n\n'
+    printf '原 WebFetch 提问（Original WebFetch prompt）："%s"。若当前问题不同，请判断\n' "$ORIGINAL_PROMPT"
+    printf '这份内容是否仍覆盖当前问题。\n\n'
   fi
   printf -- '----- BEGIN CACHED CONTENT -----\n'
   printf '%s\n' "$CONTENT"

package/hooks/session-start-test.sh

@@ -33,7 +33,7 @@ if (typeof out.additionalContext !== 'string' || !out.additionalContext.trim())
 
 const ctx = out.additionalContext;
 if (hasJq) {
-  if (!ctx.includes('i3-composer-agent loaded.')) {
+  if (!ctx.includes('i3-composer-agent 已加载。')) {
     throw new Error('additionalContext is missing startup preface');
   }
   if (!ctx.includes('# Using i3 Composer Agent')) {

package/hooks/session-start.sh

@@ -16,7 +16,7 @@ SKILLS_DIR="$(dirname "$SCRIPT_DIR")/skills"
 META_SKILL="$SKILLS_DIR/i3-using-agent-skills/SKILL.md"
 
 if ! command -v jq >/dev/null 2>&1; then
-  echo '{"hookSpecificOutput": {"hookEventName": "SessionStart", "additionalContext": "i3-composer-agent: jq is required for the session-start hook but was not found on PATH. Install jq (e.g. `brew install jq` or `apt-get install jq`) to enable meta-skill injection. Skills remain available individually."}}'
+  echo '{"hookSpecificOutput": {"hookEventName": "SessionStart", "additionalContext": "i3-composer-agent: 会话启动 Hook 需要 jq（jq is required），但 PATH 中未找到。请安装 jq（如 `brew install jq` 或 `apt-get install jq`）后启用元技能注入；仍可单独调用技能。"}}'
   exit 0
 fi
 
@@ -24,10 +24,10 @@ if [ -f "$META_SKILL" ]; then
   CONTENT=$(cat "$META_SKILL")
   # Use jq to properly escape and construct valid JSON
   jq -cn \
-    --arg context "i3-composer-agent loaded. Use the skill discovery flowchart to find the right skill for your task.
+    --arg context "i3-composer-agent 已加载。请按技能发现流程选择合适的技能，默认使用简体中文回复；用户明确要求其他语言时再切换。
 
 $CONTENT" \
     '{hookSpecificOutput: {hookEventName: "SessionStart", additionalContext: $context}}'
 else
-  echo '{"hookSpecificOutput": {"hookEventName": "SessionStart", "additionalContext": "i3-composer-agent: i3-using-agent-skills meta-skill not found. Skills may still be available individually."}}'
+  echo '{"hookSpecificOutput": {"hookEventName": "SessionStart", "additionalContext": "i3-composer-agent: i3-using-agent-skills 元技能未找到（meta-skill not found），仍可尝试单独调用技能。"}}'
 fi

package/hooks/simplify-ignore.sh

@@ -25,7 +25,7 @@ set -euo pipefail
 shopt -u patsub_replacement 2>/dev/null || true
 
 if ! command -v jq >/dev/null 2>&1; then
-  printf '%s\n' "error: missing jq" >&2; exit 1
+  printf '%s\n' "错误：缺少 jq（error: missing jq）" >&2; exit 1
 fi
 
 CACHE="${CLAUDE_PROJECT_DIR:-.}/.claude/.simplify-ignore-cache"
@@ -43,13 +43,13 @@ FILE_PATH=$(printf '%s' "$INPUT" | jq -r '.tool_input.file_path // empty' 2>/dev
   FILE_PATH=""
 }
 if [ -n "$parse_error" ]; then
-  printf 'Warning: %s (input: %.120s)\n' "$parse_error" "$INPUT" >&2
+  printf '警告（Warning）：%s（输入：%.120s）\n' "$parse_error" "$INPUT" >&2
 fi
 
 hash_cmd() {
   if command -v shasum >/dev/null 2>&1; then shasum
   elif command -v sha1sum >/dev/null 2>&1; then sha1sum
-  else printf '%s\n' "error: missing shasum or sha1sum" >&2; exit 1; fi
+  else printf '%s\n' "错误：缺少哈希工具（error: missing shasum or sha1sum）" >&2; exit 1; fi
 }
 file_id() { printf '%s' "$1" | hash_cmd | cut -c1-16; }
 block_hash() { printf '%s' "$1" | hash_cmd | cut -c1-8; }
@@ -139,7 +139,7 @@ ${line}"
 
   # Unclosed block → flush as-is
   if [ $in_block -eq 1 ] && [ -n "$buf" ]; then
-    printf 'Warning: unclosed simplify-ignore-start in %s (block not hidden)\n' "$src" >&2
+    printf '警告：%s 中 simplify-ignore-start 未闭合，未隐藏代码块（Warning: unclosed simplify-ignore-start; block not hidden）\n' "$src" >&2
     printf '%s\n' "$buf" >> "$dest"
   fi
 
@@ -185,7 +185,7 @@ expand_file() {
           # (only trigger if BLOCK_hash is still present AND wasn't in the original block content)
           case "$block_content" in *"BLOCK_${h}"*) ;; *)
             case "$line" in *"BLOCK_${h}"*)
-              printf 'Warning: placeholder BLOCK_%s was modified by model, using fuzzy match\n' "$h" >&2
+              printf '警告：占位符 BLOCK_%s 被模型修改，使用模糊匹配恢复（Warning: placeholder; using fuzzy match）\n' "$h" >&2
               esc_fuzzy=$(escape_glob "${bp}BLOCK_${h}${bs}")
               line="${line//$esc_fuzzy/$block_content}"
               # Last resort: match just the hash token
@@ -214,7 +214,7 @@ expand_file() {
       # Get first line of block to check if it was expanded back
       first_line=$(head -1 "$bf")
       if ! grep -qF "$first_line" "$dest" 2>/dev/null; then
-        printf 'Warning: protected block BLOCK_%s was deleted by model\n' "$bh" >&2
+        printf '警告：受保护代码块 BLOCK_%s 被模型删除（Warning: protected block; deleted by model）\n' "$bh" >&2
       fi
     fi
   done
@@ -258,7 +258,7 @@ if [ -z "$TOOL_NAME" ]; then
         rewritten="$CACHE/${fid}.recovered"
         cat "$orig" > "$rewritten"
         cat "$bak" > "$orig"
-        printf 'Warning: no BLOCK_ placeholder left in %s, restored from backup. Rewrite kept at %s\n' \
+        printf '警告：%s 中没有剩余 BLOCK_ 占位符，已从事务备份恢复，改写内容保留于 %s（Warning: no BLOCK_; restored from backup）\n' \
           "$orig" "$rewritten" >&2
       fi
       rm -f "$bak" "$pathfile" "$CACHE/${fid}".block.* "$CACHE/${fid}".reason.* "$CACHE/${fid}".prefix.* "$CACHE/${fid}".suffix.*
@@ -269,7 +269,7 @@ if [ -z "$TOOL_NAME" ]; then
       mv "$bak" "${orig}.recovered"
       rm -f "$pathfile" "$CACHE/${fid}".block.* "$CACHE/${fid}".reason.* "$CACHE/${fid}".prefix.* "$CACHE/${fid}".suffix.*
       rmdir "$CACHE/${fid}.lock" 2>/dev/null
-      printf 'Warning: %s was moved/deleted. Recovered original to %s.recovered\n' "$orig" "$orig" >&2
+      printf '警告：%s 被移动或删除，已将原文件恢复到 %s.recovered（Warning: moved/deleted; Recovered original）\n' "$orig" "$orig" >&2
     fi
   done
   # Clean orphan locks (created but crash before backup)