@fitlab-ai/agent-infra 0.11.6 → 0.11.8

package/lib/task/verification.ts

@@ -134,46 +134,42 @@ function statusLabel(status: unknown): string {
   return status === 'fail' ? 'FAIL' : status === 'blocked' ? 'BLOCKED' : 'pass';
 }
 
-function renderPayload(payload: Record<string, unknown>): string {
-  const lines: string[] = [];
-  if (Array.isArray(payload.checks)) {
-    const gateMode = typeof payload.gate === 'string';
-    lines.push(gateMode
-      ? `Verification: ${payload.gate} | Skill: ${payload.skill}`
-      : `Check: ${payload.status} | Skill: ${payload.skill} | Type: ${payload.type}`, '');
-    for (const check of payload.checks as Array<Record<string, unknown>>) {
-      const raw = statusLabel(check.status);
-      const effective = statusLabel(check.effectiveStatus ?? check.status);
-      const reason = check.reason ?? 'CHECK_FAILED';
-      const message = check.message ?? reason;
-      lines.push(`  [${effective}] ${check.checkId ?? check.type} (${check.classification ?? 'hard'}; raw ${raw}; reason ${reason}) - ${message}; ${check.action ?? 'Review validation output'}`);
-    }
-    const summary = payload.summary ?? (() => {
-      const checks = payload.checks as Array<Record<string, unknown>>;
-      const statuses = checks.map((check) => check.effectiveStatus ?? check.status);
-      return `${statuses.filter((status) => status === 'pass').length} passed, ${statuses.filter((status) => status === 'fail').length} failed${statuses.includes('blocked') ? `, ${statuses.filter((status) => status === 'blocked').length} blocked` : ''}`;
-    })();
-    lines.push('', `Result: ${summary} - ${payload.action}`);
-  } else {
-    lines.push(`Check: ${payload.status} | Skill: ${payload.skill} | Type: ${payload.type}`, '');
-    const raw = statusLabel(payload.status);
-    const effective = statusLabel(payload.effectiveStatus ?? payload.status);
-    const reason = payload.reason ?? 'CHECK_FAILED';
-    lines.push(`  [${effective}] ${payload.checkId ?? payload.type} (${payload.classification ?? 'hard'}; raw ${raw}; reason ${reason}) - ${payload.message ?? reason}; ${payload.action ?? 'Review validation output'}`);
-    const status = payload.effectiveStatus ?? payload.status;
-    const summary = status === 'pass' ? '1 passed, 0 failed'
-      : status === 'blocked' ? '0 passed, 0 failed, 1 blocked' : '0 passed, 1 failed';
-    const action = status === 'pass' ? 'Requested check passed'
-      : status === 'blocked' ? `Resolve blocked ${payload.type} check and re-run check`
-        : `Fix ${payload.type} issues and re-run check`;
-    lines.push('', `Result: ${summary} - ${action}`);
-  }
-  return `${lines.join('\n')}\n`;
-}
-
 function renderTaskVerification(result: TaskVerificationResult): string {
   if (result.status === 'failed') return `Verification failed: ${result.error?.code ?? 'VERIFY_FAILED'} - ${result.error?.message ?? 'unknown error'}\n`;
-  return result.invocations.map((invocation) => renderPayload(invocation.payload)).join('');
+  const target = `${result.event}${result.artifact ? ` (${result.artifact})` : ''}`;
+  const lines = [`Verification: ${result.status} | Target: ${target} | Skill: ${result.skill}`];
+  const checks = result.invocations.flatMap(({ payload }) => {
+    if (Array.isArray(payload.checks)) return payload.checks as Array<Record<string, unknown>>;
+    return [payload];
+  });
+  const counts = {
+    pass: checks.filter((check) => (check.effectiveStatus ?? check.status) === 'pass').length,
+    fail: checks.filter((check) => (check.effectiveStatus ?? check.status) === 'fail').length,
+    blocked: checks.filter((check) => (check.effectiveStatus ?? check.status) === 'blocked').length
+  };
+  const summary = `${counts.pass} passed, ${counts.fail} failed${counts.blocked > 0 ? `, ${counts.blocked} blocked` : ''}`;
+  lines.push('', `Result: ${summary}`);
+
+  for (const check of checks) {
+    const rawStatus = check.status;
+    const effectiveStatus = check.effectiveStatus ?? rawStatus;
+    const isSoftWarning = (rawStatus === 'fail' || rawStatus === 'blocked') && effectiveStatus === 'pass';
+    const reason = check.reason ?? 'CHECK_FAILED';
+    const message = check.message ?? reason;
+    const action = check.action ?? 'Review validation output';
+    const id = check.checkId ?? check.type;
+    const isHumanExemptionNotice = id === 'post-review-commit'
+      && typeof message === 'string'
+      && /\bhuman-decided (?:post-review )?exemption\b/i.test(message)
+      && /\bPRC-\d+\s*:/.test(message);
+    if (effectiveStatus === 'pass' && !isSoftWarning && !isHumanExemptionNotice) continue;
+    lines.push(isSoftWarning
+      ? `Warning: ${id} (${rawStatus === 'blocked' ? `raw BLOCKED; ` : ''}${reason}) - ${message}; ${action}`
+      : isHumanExemptionNotice
+        ? `Notice: ${id} - ${message}; ${action}`
+        : `  [${statusLabel(effectiveStatus)}] ${id} (${reason}) - ${message}; ${action}`);
+  }
+  return `${lines.join('\n')}\n`;
 }
 
 export { VERIFICATION_CATALOG, renderTaskVerification, verifyTaskEvent };

package/lib/task/workflow-warning-intents.ts

@@ -1,4 +1,5 @@
 import fs from 'node:fs';
+import path from 'node:path';
 
 import { resolveTaskRef } from './resolve-ref.ts';
 import { parseTaskFrontmatter } from './frontmatter.ts';
@@ -142,7 +143,14 @@ function projectFinalizationWarning(
   if (!resolved.ok) return { status: 'failed', changed: false, error: { code: resolved.code, message: resolved.message } };
   let prepared = resolved.state === 'completed';
   if (!prepared && resolved.state === 'active') {
-    try { prepared = parseTaskFrontmatter(fs.readFileSync(resolved.taskMdPath, 'utf8')).status === 'completed'; }
+    try {
+      const taskContent = fs.readFileSync(resolved.taskMdPath, 'utf8');
+      prepared = parseTaskFrontmatter(taskContent).status === 'completed';
+      if (!prepared) {
+        const lifecycle = JSON.parse(fs.readFileSync(path.join(resolved.taskDir, '.task-lifecycle.json'), 'utf8')) as Record<string, unknown>;
+        prepared = lifecycle.taskId === resolved.taskId && lifecycle.intent === 'complete';
+      }
+    }
     catch { prepared = false; }
   }
   if (!prepared) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fitlab-ai/agent-infra",
-  "version": "0.11.6",
+  "version": "0.11.8",
   "description": "Bootstrap tool for AI multi-tool collaboration infrastructure — works with Claude Code, Codex, Antigravity CLI, and OpenCode",
   "license": "MIT",
   "type": "module",

package/templates/.agents/README.en.md

@@ -252,7 +252,7 @@ ai agent-client configure
 
 TraeCode CLI uses `.agents/skills/` as the canonical Skill source. agent-infra generates lightweight slash-command wrappers under `.traecli/commands/`; each wrapper reads the corresponding shared Skill and forwards `$ARGUMENTS` when that Skill declares arguments. It does not mirror Skill packages into `.trae/skills/`, which remains user-owned for intentional Trae-specific overrides.
 
-`agentClients` is the sole source of truth for built-in client state. The top-level array must contain all five built-in clients in the fixed canonical order; `sandbox.tools` lists only non-client tools such as `agent-infra` and custom tools. A legacy `tuis` field or a built-in client id in `sandbox.tools` is rejected, and configuration is never rewritten automatically.
+`agentClients` is the sole source of truth for built-in client state. The top-level array must contain all five built-in clients in the fixed canonical order; `sandbox.tools.ids` lists non-client tools such as `agent-infra` and custom tools, while `sandbox.tools.definitions` maps custom tool IDs to their definitions. A legacy `tuis` field or a built-in client id in `sandbox.tools.ids` is rejected, and configuration is never rewritten automatically.
 
 ### Side effects of disabling an Agent Client
 
@@ -260,7 +260,7 @@ When you disable a built-in client, reconciliation stops maintaining its seed co
 
 ### Relation to other config fields
 
-- `sandbox.tools` now lists non-client tools such as `agent-infra` and custom tools. Built-in client installation belongs in `agentClients[].installInSandbox`.
+- `sandbox.tools.ids` lists non-client tools such as `agent-infra` and custom tools; custom definitions belong in `sandbox.tools.definitions`. Built-in client installation belongs in `agentClients[].installInSandbox`.
 - `agentClients` is independent from `customTUIs` (see below). Custom TUI command files are preserved even when their directory is under a disabled built-in client's path prefix.
 
 ## Custom TUI Configuration
@@ -313,13 +313,13 @@ Namespaced custom TUI:
 
 ## Sandbox Custom Tools
 
-`customTUIs` generates slash-command files but does not change the sandbox image. To install a non-npm CLI or tool (pip / cargo / curl-based / pre-built binary) into the sandbox image and live-mount its credentials, declare it under `sandbox.customTools` in `.agents/.airc.json`. Built-in Agent Clients are installed according to `agentClients[].installInSandbox`; `agent-infra` remains a non-client entry in `sandbox.tools` and only provides the in-sandbox `ai` / `agent-infra` CLI.
+`customTUIs` generates slash-command files but does not change the sandbox image. To install a non-npm CLI or tool (pip / cargo / curl-based / pre-built binary) into the sandbox image and live-mount its credentials, declare it under an ID key in `sandbox.tools.definitions` in `.agents/.airc.json`. Built-in Agent Clients are installed according to `agentClients[].installInSandbox`; `agent-infra` remains a non-client entry in `sandbox.tools.ids` and only provides the in-sandbox `ai` / `agent-infra` CLI.
 
 ### Required fields
 
 | Field | Meaning |
 |-------|---------|
-| `id` | Lowercase id matching `^[a-z0-9][a-z0-9-]*$`. Referenced from `sandbox.tools`. Must not collide with a built-in id. |
+| Definition object key | Lowercase tool ID matching `^[a-z0-9][a-z0-9-]*$`. Every selected custom tool in `sandbox.tools.ids` needs a matching definition. Definitions not listed in `ids` may remain unused. Keys must not collide with a built-in id. |
 | `install` | Install descriptor. `{ "type": "npm", "cmd": "<npm package spec>" }` runs `npm install -g <cmd>`. `{ "type": "shell", "cmd": "<shell>" }` runs the shell command(s) as `devuser` during image build. `cmd` must be non-empty. |
 
 Minimal entry — the contract for getting a tool into the image is just these two fields:
@@ -327,13 +327,14 @@ Minimal entry — the contract for getting a tool into the image is just these t
 ```json
 {
   "sandbox": {
-    "tools": ["my-shell-tool"],
-    "customTools": [
-      {
-        "id": "my-shell-tool",
-        "install": { "type": "shell", "cmd": "curl -fsSL https://example.com/install.sh | bash" }
+    "tools": {
+      "ids": ["my-shell-tool"],
+      "definitions": {
+        "my-shell-tool": {
+          "install": { "type": "shell", "cmd": "curl -fsSL https://example.com/install.sh | bash" }
+        }
       }
-    ]
+    }
   }
 }
 ```
@@ -354,24 +355,25 @@ Add only the fields your tool actually needs. Omit them and the loader fills sen
 | `hostLiveMounts` | (none) | Share host credentials live (e.g. OAuth tokens) with the container. Read-write. |
 | `postSetupCmds` | (none) | Run commands inside the container after first setup (e.g. symlinks). |
 
-> **`sandboxBase` is not user-configurable.** The loader always assigns `~/.agent-infra/sandboxes/<id>` so `ai sandbox rm` / `prune` can find tool state. Any `sandboxBase` value in `customTools` entries is silently ignored.
+> **`sandboxBase` is not user-configurable.** The loader always assigns `~/.agent-infra/sandboxes/<id>` so `ai sandbox rm` / `prune` can find tool state. Any `sandboxBase` value in a definition is silently ignored.
 
 Real-world example — `anthropic-claude` as a user-defined id with binary name `claude` and host credential live-mount:
 
 ```json
 {
   "sandbox": {
-    "tools": ["claude-code", "anthropic-claude"],
-    "customTools": [
-      {
-        "id": "anthropic-claude",
+    "tools": {
+      "ids": ["anthropic-claude"],
+      "definitions": {
+        "anthropic-claude": {
         "install": { "type": "npm", "cmd": "@anthropic-ai/claude-code@stable" },
         "versionCmd": "claude --version",
         "hostLiveMounts": [
           { "hostPath": "~/.claude/.credentials.json", "containerSubpath": ".credentials.json" }
         ]
+        }
       }
-    ]
+    }
   }
 }
 ```
@@ -386,7 +388,7 @@ Real-world example — `anthropic-claude` as a user-defined id with binary name
 
 ### Interaction with `sandbox.dockerfile`
 
-When you set `sandbox.dockerfile` to point at your own Dockerfile, agent-infra still passes both `AI_TOOL_PACKAGES` (space-separated npm package specs) and `AI_TOOLS_SHELL_INSTALL_B64` (base64-encoded shell install script) as `--build-arg`. Your custom Dockerfile decides whether to consume them; if it does not declare the matching `ARG`, the shell installs for `customTools` are silently skipped — taking over the Dockerfile means taking over the install path.
+When you set `sandbox.dockerfile` to point at your own Dockerfile, agent-infra still passes both `AI_TOOL_PACKAGES` (space-separated npm package specs) and `AI_TOOLS_SHELL_INSTALL_B64` (base64-encoded shell install script) as `--build-arg`. Your custom Dockerfile decides whether to consume them; if it does not declare the matching `ARG`, the shell installs declared in `sandbox.tools.definitions` are silently skipped — taking over the Dockerfile means taking over the install path.
 
 ## Skill Authoring Conventions
 

package/templates/.agents/README.zh-CN.md

@@ -250,7 +250,7 @@ ai agent-client configure
 
 TraeCode CLI 以 `.agents/skills/` 作为 Skill 的唯一权威源。agent-infra 仅在 `.traecli/commands/` 下生成轻量 slash-command 包装文件；每个包装文件读取对应的共享 Skill，并在该 Skill 声明参数时转发 `$ARGUMENTS`。它不会把 Skill 包镜像到 `.trae/skills/`；该目录继续由用户所有，仅用于有意添加的 Trae 专属覆盖。
 
-`agentClients` 是内建客户端状态的唯一配置来源。顶层数组必须按固定规范顺序包含全部五个内建客户端；`sandbox.tools` 只列出 `agent-infra` 和自定义工具等非客户端工具。旧 `tuis` 字段或 `sandbox.tools` 中的内建客户端 id 会被拒绝，配置不会被自动改写。
+`agentClients` 是内建客户端状态的唯一配置来源。顶层数组必须按固定规范顺序包含全部五个内建客户端；`sandbox.tools.ids` 按顺序列出 `agent-infra` 和自定义工具等非客户端工具，`sandbox.tools.definitions` 用工具 ID 键控自定义工具定义。旧 `tuis` 字段或 `sandbox.tools.ids` 中的内建客户端 id 会被拒绝，配置不会被自动改写。
 
 ### 取消 Agent Client 的副作用
 
@@ -258,7 +258,7 @@ TraeCode CLI 以 `.agents/skills/` 作为 Skill 的唯一权威源。agent-infra
 
 ### 与其他配置字段的关系
 
-- `sandbox.tools` 现在只列出 `agent-infra` 和自定义工具等非客户端工具。内建客户端的安装状态由 `agentClients[].installInSandbox` 表达。
+- `sandbox.tools.ids` 只列出 `agent-infra` 和自定义工具等非客户端工具；自定义定义放在 `sandbox.tools.definitions`。内建客户端的安装状态由 `agentClients[].installInSandbox` 表达。
 - `agentClients` 与 `customTUIs`（见下）相互独立。即使自定义 TUI 目录落在已取消的内建客户端路径前缀下，其命令文件也会被保留。
 
 ## 自定义 TUI 配置
@@ -311,13 +311,13 @@ TraeCode CLI 以 `.agents/skills/` 作为 Skill 的唯一权威源。agent-infra
 
 ## 沙箱自定义工具（Sandbox Custom Tools）
 
-`customTUIs` 只负责生成 slash-command 文件，**不影响沙箱镜像**。如果要把一个非 npm 分发的 CLI 或工具（pip / cargo / curl 脚本 / 裸二进制）装进沙箱镜像、并 live-mount 它的凭证目录，需要在 `.agents/.airc.json` 的 `sandbox.customTools` 中声明。内建 Agent Client 按 `agentClients[].installInSandbox` 安装；`agent-infra` 仍是 `sandbox.tools` 中的非客户端条目，只提供沙箱内的 `ai` / `agent-infra` CLI。
+`customTUIs` 只负责生成 slash-command 文件，**不影响沙箱镜像**。如果要把一个非 npm 分发的 CLI 或工具（pip / cargo / curl 脚本 / 裸二进制）装进沙箱镜像、并 live-mount 它的凭证目录，需要在 `.agents/.airc.json` 的 `sandbox.tools.definitions` 中按工具 ID 声明。内建 Agent Client 按 `agentClients[].installInSandbox` 安装；`agent-infra` 仍是 `sandbox.tools.ids` 中的非客户端条目，只提供沙箱内的 `ai` / `agent-infra` CLI。
 
 ### 必填字段
 
 | 字段 | 含义 |
 |------|------|
-| `id` | 小写 id，匹配 `^[a-z0-9][a-z0-9-]*$`；由 `sandbox.tools` 引用；不可与内建 id 冲突。 |
+| 定义对象的键 | 小写工具 ID，匹配 `^[a-z0-9][a-z0-9-]*$`；`ids` 中选用的自定义工具必须有对应定义；未列入 `ids` 的定义可以保留为未启用工具；不可与内建 id 冲突。 |
 | `install` | 安装描述符。`{ "type": "npm", "cmd": "<npm 包规范>" }` 执行 `npm install -g <cmd>`；`{ "type": "shell", "cmd": "<shell>" }` 在镜像构建阶段以 `devuser` 执行 shell。`cmd` 必须非空。 |
 
 最小入口——把一个工具装进镜像所需的契约只有这两个字段：
@@ -325,13 +325,14 @@ TraeCode CLI 以 `.agents/skills/` 作为 Skill 的唯一权威源。agent-infra
 ```json
 {
   "sandbox": {
-    "tools": ["my-shell-tool"],
-    "customTools": [
-      {
-        "id": "my-shell-tool",
-        "install": { "type": "shell", "cmd": "curl -fsSL https://example.com/install.sh | bash" }
+    "tools": {
+      "ids": ["my-shell-tool"],
+      "definitions": {
+        "my-shell-tool": {
+          "install": { "type": "shell", "cmd": "curl -fsSL https://example.com/install.sh | bash" }
+        }
       }
-    ]
+    }
   }
 }
 ```
@@ -352,24 +353,25 @@ TraeCode CLI 以 `.agents/skills/` 作为 Skill 的唯一权威源。agent-infra
 | `hostLiveMounts` | （无） | 把宿主凭证（如 OAuth token）实时挂进容器，读写共享。 |
 | `postSetupCmds` | （无） | 首次安装完成后在容器内执行命令（如建符号链接）。 |
 
-> **`sandboxBase` 不由用户配置。** loader 永远使用 `~/.agent-infra/sandboxes/<id>`，这样 `ai sandbox rm` / `prune` 才能找到工具状态目录。`customTools` 条目里写的任何 `sandboxBase` 都会被静默忽略。
+> **`sandboxBase` 不由用户配置。** loader 永远使用 `~/.agent-infra/sandboxes/<id>`，这样 `ai sandbox rm` / `prune` 才能找到工具状态目录。定义对象里写的任何 `sandboxBase` 都会被静默忽略。
 
 实际场景示例——`anthropic-claude` 作为用户自定义 id，二进制名是 `claude`，并把宿主凭证 live-mount 进来：
 
 ```json
 {
   "sandbox": {
-    "tools": ["claude-code", "anthropic-claude"],
-    "customTools": [
-      {
-        "id": "anthropic-claude",
+    "tools": {
+      "ids": ["anthropic-claude"],
+      "definitions": {
+        "anthropic-claude": {
         "install": { "type": "npm", "cmd": "@anthropic-ai/claude-code@stable" },
         "versionCmd": "claude --version",
         "hostLiveMounts": [
           { "hostPath": "~/.claude/.credentials.json", "containerSubpath": ".credentials.json" }
         ]
+        }
       }
-    ]
+    }
   }
 }
 ```

package/templates/.agents/rules/README.en.md

@@ -14,6 +14,7 @@ so you can quickly find "which ones to read" without opening each file.
 - [`debugging-guide.md`](debugging-guide.md) — Structured debugging flow: gather evidence → form hypothesis → verify hypothesis → fix the root cause; no blind patch-and-retry.
 - [`compatibility-policy.md`](compatibility-policy.md) — Compatibility by exception: admission evidence, implementation boundaries, exit conditions, and lifecycle review requirements.
 - [`evidence-reporting.md`](evidence-reporting.md) — Minimum evidence semantics for state checks, successful summaries, exceptional results, identity fields, and sensitive data boundaries.
+- [`validation-output.md`](validation-output.md) — User-facing validation summaries, failure diagnostics, soft warnings, and consumer boundaries.
 - [`sync-content-generation.md`](sync-content-generation.md) — Producer-side Markdown constraints for task and lifecycle content synchronized to Issues.
 - [`decision-qualification.md`](decision-qualification.md) — Constraint, candidate, human-confirmation, and six-artifact qualification-audit contract.
 
@@ -28,7 +29,7 @@ so you can quickly find "which ones to read" without opening each file.
 
 ## Task Workflow
 
-- [`task-management.md`](task-management.md) — Task intent detection and workflow-command mapping.
+- [`task-management.md`](task-management.md) — Task intent detection, workflow-command mapping, and skill blocking boundaries.
 - [`lifecycle-orchestration.md`](lifecycle-orchestration.md) — Fresh executor/reviewer, one-use receipt, pause/recovery, and safe endpoint rules for `run-task`.
 - [`review-handshake.md`](review-handshake.md) — Three-stage bidirectional review handshake: four-state disposition, symmetric evidence, disagreement ledger, convergence and post-review commit gate.
 - [`review-method.md`](review-method.md) — Shared three-stage review method: multi-pass review, risk lenses, traceability, and finding evidence.

package/templates/.agents/rules/README.zh-CN.md

@@ -13,6 +13,7 @@
 - [`debugging-guide.md`](debugging-guide.md) — 结构化调试流程：收集证据→形成假设→验证假设→修复根因，禁止盲目改代码重试。
 - [`compatibility-policy.md`](compatibility-policy.md) — 兼容性默认关闭：准入证据、实现边界、退出条件与生命周期审查要求。
 - [`evidence-reporting.md`](evidence-reporting.md) — 生命周期报告的状态核对、成功摘要、异常证据、身份字段和敏感信息边界。
+- [`validation-output.md`](validation-output.md) — 面向用户的校验状态摘要、失败诊断、软警告及消费边界。
 - [`sync-content-generation.md`](sync-content-generation.md) — 同步到 Issue 的任务和生命周期 Markdown 生成约束。
 - [`decision-qualification.md`](decision-qualification.md) — 约束、候选、人工确认和六类 artifact 资格审计契约。
 
@@ -27,7 +28,7 @@
 
 ## 任务工作流
 
-- [`task-management.md`](task-management.md) — 任务语义识别与工作流命令映射。
+- [`task-management.md`](task-management.md) — 任务语义识别、工作流命令映射与技能阻塞边界。
 - [`lifecycle-orchestration.md`](lifecycle-orchestration.md) — `run-task` 的 fresh executor/reviewer、一次性 receipt、暂停恢复与安全终点规则。
 - [`review-handshake.md`](review-handshake.md) — 三阶段双向审查握手协议：四态处置、对称证据、分歧账本、收敛与 post-review commit 门禁。
 - [`review-method.md`](review-method.md) — 三阶段共享检视方法：多遍检视、风险镜头、追踪与 finding 证据契约。

package/templates/.agents/rules/decision-qualification.en.md

@@ -6,7 +6,8 @@ Any analysis, plan, implementation, or review that decides whether a human decis
 
 - The `### Constraints` and `### Candidate and Rejected Options` tables in `task.md` are the only constraint and candidate fact source.
 - The constraint table uses `constraint_id`, `statement`, `status`, `authority`, `source`, `evidence`, `derived_from`, and `approval_evidence`; the candidate table uses `candidate_id`, `statement`, `status`, `constraint_ids`, `impact`, and `evidence`.
-- All six artifact families must include `## Qualification Audit` with actual constraint dependencies, candidate qualification, classification results, upstream relations, and a dependency snapshot. Each upstream relation records family, file name, round, and SHA-256.
+- Qualification audits are optional in all six lifecycle artifact families. When `## Qualification Audit` is present, it must contain three decision tables (constraint dependencies, candidate qualification, classification results) and one snapshot row (`task_input_digest`, `non_constraint_input_digest`). Candidate qualification must cover the complete candidate set in the task.
+- Lifecycle input relationships belong in the `Artifact Lifecycle Receipts` section of `task.md`. Freeze each stage's actual artifact inputs and SHA-256 values at stage start, then verify and record each input edge at completion. Do not duplicate lifecycle edges in qualification audits.
 
 ## Status and confirmation
 
@@ -17,6 +18,6 @@ Any analysis, plan, implementation, or review that decides whether a human decis
 
 ## Invalidation and review
 
-When a constraint changes, only artifacts declaring the affected `C-N` can be direct invalidation seeds; the change then follows the real downstream closure. All six families, including reviews, are symmetric. If snapshots, relations, or change classification cannot prove a pure constraint change, use the existing full invalidation path. The newly completed source artifact, its receipt, and its derived snapshot are excluded from the old target graph.
+When a lifecycle artifact is replaced, start from the old artifact and follow verified input edges in the task receipts to find and invalidate every downstream consumer. Exclude the new artifact from the old graph. If any relation is missing, identity or SHA-256 does not match, or the graph cannot be verified, use the existing static downstream invalidation scope.
 
-Missing or unknown references, digest mismatches, dangling relations, and cycles fail closed. Formatting-only changes must not change semantic digests; changes to meaning, provenance, status, candidates, or upstream identity require a new audit.
+When a qualification audit is present, missing or unknown references and digest mismatches block finalization. Audits in the old format with an upstream-relations table must be regenerated in the current format. Formatting-only changes must not change semantic digests; changes to meaning, provenance, status, or candidates require a new audit.

package/templates/.agents/rules/decision-qualification.zh-CN.md

@@ -6,7 +6,8 @@
 
 - `task.md` 的 `### 约束` 和 `### 候选与否决方案` 是唯一约束/候选事实源。
 - 约束表必须使用 `constraint_id`、`statement`、`status`、`authority`、`source`、`evidence`、`derived_from`、`approval_evidence`；候选表必须使用 `candidate_id`、`statement`、`status`、`constraint_ids`、`impact`、`evidence`。
-- 六类阶段产物都要在 `## 资格审计` 中声明实际约束依赖、候选资格、分类结果、上游关系和依赖快照。上游关系必须保存 artifact 的 family、文件名、round 和 SHA-256。
+- 六类阶段产物可以省略资格审计。若填写 `## 资格审计`，必须包含约束依赖、候选资格、分类结果三张决策表，以及一行资格快照（`task_input_digest`、`non_constraint_input_digest`）。候选资格必须覆盖任务中的完整候选集合。
+- 生命周期输入关系由 `task.md` 的“产物生命周期收据”记录；阶段开始时冻结实际输入 artifact 和 SHA-256，完成时验证后写入每条输入边。不要在资格审计中复制生命周期关系。
 
 ## 状态与确认
 
@@ -17,6 +18,6 @@
 
 ## 失效与审查
 
-约束变化时，只有声明受影响 `C-N` 的 artifact 才能成为直接失效种子，并沿真实上游关系的下游闭包传播；六类 artifact（含 review）对等处理。快照、关系图或变化分类无法证明为纯约束变化时，回退既有全量失效路径。新完成的 source artifact、自身 receipt 和派生快照不作为旧图目标。
+替换某个阶段产物时，系统从被替换的旧 artifact 出发，沿任务收据中验证过的输入边计算所有下游消费者，并使旧消费者失效；新产物不进入旧图。若任一关系缺失、身份不匹配、SHA-256 不匹配或图无法验证，则使用既有静态下游失效范围。
 
-缺失、未知引用、digest 不匹配、悬空关系或环都必须 fail closed。排版变化不应改变语义 digest；语义、来源、状态、候选或上游 identity 变化必须触发重新审计。
+资格审计存在时，缺失、未知引用或 digest 不匹配都必须拒绝收尾。旧版包含“上游关系”表的资格审计不再读取，应按当前格式重新生成。排版变化不应改变语义 digest；语义、来源、状态或候选变化必须触发重新审计。

package/templates/.agents/rules/task-management.en.md

@@ -36,6 +36,18 @@ The seven internal commands (`task-event` / `task-lifecycle` / `task-finalizatio
 - `task-verify` executes the typed catalog/check registry in-process; skills declare business events only.
 - Both entrypoints are read-only. Verification exits remain `0=pass`, `1=fail`, and `2=blocked`; network or platform blocking must never be downgraded to success.
 
+## Platform Results and Skill Blocking Boundaries
+
+A `blocked` platform write means only that the operation is unfinished. Whether the skill stops depends on its delivery goal. The typed core handles write queuing, recovery, and idempotency; skills consume structured results and do not replay writes themselves.
+
+- `import-issue`: stop importing when the source Issue cannot be read.
+- `create-pr`: stop the creation flow when the PR was not created or its identity cannot be confirmed.
+- `review-pr`: stop reviewing when the PR or reviewed head cannot be read. After local review is complete, record recoverable comment or formal Review write failures as the skill specifies without blocking the completed local review.
+- `cancel-task`: apply the skill's full cancellation criteria; do not claim full cancellation when required Issue synchronization fails.
+- `complete-task`: apply the skill's full completion criteria; resolve pending recoverable operations before archiving and do not claim completion while required remote facts remain unconfirmed.
+
+Other skills continue past deferrable writes according to their local delivery goals. If `create-task` has created the local task but creation of the associated Issue fails, retain the local task and record the failure so independent subsequent work can continue.
+
 ## Required State Updates by Command
 
 - `create-task`: create `branch`, `workflow`, `status`, `created_at`, `updated_at`, `assigned_to`, `agent_infra_version`

package/templates/.agents/rules/task-management.zh-CN.md

@@ -36,6 +36,18 @@
 - `task-verify` 在进程内执行 typed catalog/check registry；SKILL 只声明业务事件，不传 task-dir、skill 名或特殊 check 序列。
 - 两个入口均保持只读；验证退出码固定为 `0=pass`、`1=fail`、`2=blocked`，网络或平台阻塞不得降格为成功。
 
+## 平台结果与技能阻塞边界
+
+平台写入返回 `blocked` 只表示该操作尚未完成；技能是否停止由当前技能的交付目标决定。平台写入的排队、恢复和幂等由 typed core 执行，技能只消费结构化结果，不自行重放。
+
+- `import-issue`：源 Issue 读取失败时停止导入。
+- `create-pr`：PR 未创建或无法确认其身份时停止创建流程。
+- `review-pr`：PR 或被审 head 无法读取时停止审查；本地审查完成后，评论或正式 Review 写入失败按技能记录待恢复事实，不阻断已完成的本地审查。
+- `cancel-task`：按技能的完整取消标准判断；必要的 Issue 同步失败时不得宣称取消全部完成。
+- `complete-task`：按技能的完整完成标准判断；归档前收敛待恢复操作，必要的远端事实未确认时不得宣称任务完成。
+
+其他技能按各自的本地交付目标继续处理可延后写入。`create-task` 已在本地创建任务、但伴生 Issue 创建失败时，保留本地任务并记录失败，不停止后续可独立执行的工作。
+
 ## 常见命令的状态更新要求
 
 - `create-task`：创建 `branch`、`workflow`、`status`、`created_at`、`updated_at`、`assigned_to`、`agent_infra_version`

package/templates/.agents/rules/validation-output.en.md

@@ -0,0 +1,19 @@
+# Validation Output Summary
+
+This rule governs how `task-verify --format text` and lifecycle skills present validation results to users. It does not change validation logic, structured results, or persisted evidence requirements.
+
+## Overall Summary
+
+- Show the overall status, validation target, and pass, fail, and blocked counts.
+- For successful results, show only the summary; do not list passing check names.
+- Keep failure and blocked states distinct. List only effective failed or blocked checks, with a stable identifier, concise reason, and actionable step.
+- A soft check whose raw status is failed but effective status is pass must not count as a failure. When a user-facing notice is needed, show a concise warning with the necessary reason and action.
+- A soft check whose raw status is blocked but effective status is pass must also show a concise warning that preserves the raw blocked state, necessary reason, and action.
+- If a passing result carries a consumed human exemption or other required exception evidence, show a concise notice that preserves the exception evidence; continue to count the check by its effective status.
+
+## Consumer Boundaries
+
+- Do not copy complete successful stdout into the final response. Read structured details or rerun the command when passing check details are needed.
+- Consume structured host finalization results through their status, receipt, and warning projection; do not present receipt contents as the user summary.
+- Persisted lifecycle reports continue to follow `evidence-reporting.md`, recording reproducible scope, status, and necessary evidence. Issue artifact comments continue to sync the required report content.
+- JSON payloads, check order, check set, effective-status decisions, and exit codes remain unchanged.

package/templates/.agents/rules/validation-output.zh-CN.md

@@ -0,0 +1,19 @@
+# 校验输出摘要规则
+
+本规则约束 `task-verify --format text` 及生命周期技能向用户展示校验结果的方式。它不改变校验逻辑、结构化结果或持久化证据要求。
+
+## 总体摘要
+
+- 展示总体状态、校验目标，以及通过、失败和阻塞计数。
+- 成功结果只展示摘要，不列出通过项名称。
+- 失败与阻塞保持不同状态；只列出有效失败或阻塞项的稳定标识、简明原因和可执行动作。
+- raw 状态失败但 effective 状态通过的软检查，不得计入失败；需要提醒用户时用简短警告及必要原因和动作说明。
+- raw 状态阻塞但 effective 状态通过的软检查，也必须显示简短警告，并保留 raw 阻塞状态、必要原因和动作说明。
+- 通过结果若包含已消费的人工作出豁免或其他必须保留的例外证据，应显示简短提示并保留例外证据；该检查仍按 effective 状态计数。
+
+## 消费边界
+
+- 不把完整成功 stdout 复制到最终回复。需要检查通过项明细时，按需读取结构化结果或重新运行命令。
+- 宿主 finalization 等结构化结果按其状态、receipt 和 warning projection 消费；不要将 receipt 原文当作用户摘要。
+- 持久化生命周期报告继续遵循 `evidence-reporting.md`，记录可复现范围、状态和必要证据；Issue artifact 评论继续同步所需报告内容。
+- JSON payload、检查顺序、检查集合、effective status 判定和退出码均不受本规则影响。

package/templates/.agents/skills/analyze-task/SKILL.en.md

@@ -21,7 +21,7 @@ The analysis artifact must record `Path`, `Basis`, `Unmet Higher-path Conditions
 
 Before generating the analysis report, read `.agents/rules/evidence-reporting.md`. Record the command, target scope, status or structured result, actual result, and uncovered parts for state checks and successful checks; include decisive raw excerpts only for failures, blocking conditions, or disputes.
 
-- When evaluating candidate qualification or `HD-N`, read `.agents/rules/decision-qualification.md`, audit normalized task constraints/candidates, and record the five qualification-audit tables in the analysis artifact; unknown or unconfirmed constraints must not automatically exclude a candidate
+- When evaluating candidate qualification or `HD-N`, read `.agents/rules/decision-qualification.md`, audit normalized task constraints/candidates, and record the three qualification-audit decision tables and snapshot in the analysis artifact; unknown or unconfirmed constraints must not automatically exclude a candidate
 - This skill only outputs a requirements analysis document (`analysis.md` or `analysis-r{N}.md`) and does not modify any business code
 - Base the analysis strictly on the existing task input, requirements, context, and source information in `task.md`
 - Before generating task or lifecycle Markdown that will be synchronized to an Issue, read `.agents/rules/sync-content-generation.md` and apply its producer-side constraints; the sync path does not parse or rewrite the body
@@ -258,6 +258,8 @@ Run the verification gate to confirm the task artifact and sync state are valid:
 agent-infra-internal task-verify {task-id} analyze.completed --artifact {analysis-artifact} --format text
 ```
 
+Present the verification summary per `.agents/rules/validation-output.md`, retaining necessary failure, blocked, and soft-warning diagnostics.
+
 Handle the result as follows:
 - exit code 0 (all checks passed) -> continue to the "Inform User" step
 - exit code 1 (validation failed) -> fix the reported issues and run the gate again

package/templates/.agents/skills/analyze-task/SKILL.zh-CN.md

@@ -21,7 +21,7 @@ description: >
 
 生成分析报告时，先读取 `.agents/rules/evidence-reporting.md`。状态核对和成功检查记录命令、目标范围、状态/结构化结果、实际结果和未覆盖部分；失败、阻塞或争议才附决定性原文摘录。
 
-- 涉及候选资格或 `HD-N` 判断时，先读取 `.agents/rules/decision-qualification.md`，基于 task.md 规范化约束/候选完成资格审计，并在分析产物记录五张资格审计表；不得把来源不明或未确认约束自动升级为排除条件
+- 涉及候选资格或 `HD-N` 判断时，先读取 `.agents/rules/decision-qualification.md`，基于 task.md 规范化约束/候选完成资格审计，并在分析产物记录三张资格审计决策表和资格快照；不得把来源不明或未确认约束自动升级为排除条件
 - 本技能仅产出需求分析文档（`analysis.md` 或 `analysis-r{N}.md`）—— 不修改任何业务代码
 - 严格基于 `task.md` 中已有的任务输入、需求、上下文和来源信息展开分析
 - 生成会同步到 Issue 的任务或生命周期 Markdown 前，先读取 `.agents/rules/sync-content-generation.md` 并遵循其中的生成端约束；同步端不解析或改写正文
@@ -201,7 +201,7 @@ agent-infra-internal task-artifact {task-id} init --family analysis --artifact {
 
 ## 资格审计
 
-> 按 `.agents/rules/decision-qualification.md` 填写约束依赖、候选资格、分类结果、上游关系、依赖快照五张表；没有 artifact 上游时保留空表头，不虚构关系。
+> 仅当本阶段实际判断候选资格、约束依赖或人工裁决资格时填写本节，并按 `.agents/rules/decision-qualification.md` 完整记录三张决策表和资格快照；否则删除整个审计段。
 
 ## 假设
 
@@ -263,7 +263,7 @@ agent-infra-internal task-verify {task-id} analyze.completed --artifact {analysi
 - 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
 - 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
 
-将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+按 `.agents/rules/validation-output.md` 展示当次校验摘要；没有当次校验输出，不得声明完成。
 
 ### 9. 告知用户
 

package/templates/.agents/skills/block-task/SKILL.en.md

@@ -86,6 +86,8 @@ Run the verification gate to confirm the task artifact and sync state are valid:
 agent-infra-internal task-verify {task-id} block-task.completed --format text
 ```
 
+Present the verification summary per `.agents/rules/validation-output.md`, retaining necessary failure, blocked, and soft-warning diagnostics.
+
 Handle the result as follows:
 - exit code 0 (all checks passed) -> continue to the "Inform User" step
 - exit code 1 (validation failed) -> fix the reported issues and run the gate again

package/templates/.agents/skills/block-task/SKILL.zh-CN.md

@@ -92,7 +92,7 @@ agent-infra-internal task-verify {task-id} block-task.completed --format text
 - 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
 - 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
 
-将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+按 `.agents/rules/validation-output.md` 展示当次校验摘要；没有当次校验输出，不得声明完成。
 
 ### 8. 告知用户
 

package/templates/.agents/skills/cancel-task/SKILL.en.md

@@ -39,11 +39,13 @@ Check these directories in order:
 
 Handling rules:
 - If found in `active/` or `blocked/`: continue
-- If found only in `completed/`: inform the user the task is already moved and stop
+- If found only in `completed/` with valid `cancelled_at` and `cancel_reason`, reuse the recorded reason, skip Steps 3-5, and continue at Step 6 to recover Issue closure and comments; stop for other completed tasks
 - If not found anywhere: prompt `Task {task-id} not found`
 
 ### 2. Choose the Cancellation Label
 
+When retrying a completed task, use only the `cancel_reason` already recorded in `task.md`; do not replace it with new input.
+
 Infer the Issue closing label from the cancellation reason:
 - `status: superseded`: reason implies duplicate, replaced, merged into, or already covered by another Issue or PR
 - `status: invalid`: reason implies invalid report, no real problem, cannot reproduce, or no issue after investigation
@@ -76,7 +78,7 @@ Confirm the task directory was moved successfully.
 
 Check whether `task.md` contains a valid `platform_issue_identity`. If not, skip this step.
 
-If a valid `platform_issue_identity` exists:
+If a valid `platform_issue_identity` exists, require `applied` / `no-op` without an error for every operation before declaring cancellation fully complete. On failure, retain the local terminal state and recovery record, then retry this skill for the same task after repair:
 - Run `agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --status {reason} --in-labels none --assignees none --milestone none --state closed --close-reason not_planned`
 - Write the cancellation body to a temporary file and run `agent-infra-internal platform-comment sync {task-id} --kind cancel --body-file {path} --agent {standard-agent-token}`
 - Run `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`
@@ -93,6 +95,8 @@ Run the verification gate to confirm the moved task and sync state are valid:
 agent-infra-internal task-verify {task-id} cancel-task.completed --format text
 ```
 
+Present the verification summary per `.agents/rules/validation-output.md`, retaining necessary failure, blocked, and soft-warning diagnostics.
+
 Handle the result as follows:
 - exit code 0 (all checks passed) -> continue to the "Inform User" step
 - exit code 1 (validation failed) -> fix the reported issues and run the gate again

package/templates/.agents/skills/cancel-task/SKILL.zh-CN.md

@@ -38,11 +38,13 @@ description: >
 
 处理规则：
 - 如果在 `active/` 或 `blocked/` 中找到：继续
-- 如果只在 `completed/` 中找到：告知用户任务已转移，停止
+- 如果只在 `completed/` 中找到且 `cancelled_at` 与 `cancel_reason` 有效：复用已记录的取消原因，跳过步骤 3-5，继续步骤 6 补齐 Issue 关闭与评论；其他 completed 任务停止
 - 如果都不存在：提示 `Task {task-id} not found`
 
 ### 2. 判断取消标签
 
+从 completed 任务重试时，只使用 `task.md` 已记录的 `cancel_reason`，不得采用本次输入改写取消原因。
+
 根据取消原因推断 Issue 关闭标签：
 - `status: superseded`：原因包含“重复”、“替代”、“合并到”、“已由 #123 / PR 替代”等语义
 - `status: invalid`：原因包含“误报”、“不存在”、“无法复现”、“排查后无问题”等语义
@@ -75,7 +77,7 @@ ls .agents/workspace/completed/{task-id}/task.md
 
 检查 `task.md` 中是否存在有效的 `platform_issue_identity`。如果没有，跳过此步骤。
 
-如果存在有效的 `platform_issue_identity`：
+如果存在有效的 `platform_issue_identity`，以下操作均须取得 `applied` / `no-op` 且无错误后才能宣称取消全部完成；失败时保留本地终态和待恢复记录，修复后以同一任务重试本技能：
 - 调用 `agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --status {reason} --in-labels none --assignees none --milestone none --state closed --close-reason not_planned`
 - 将取消正文写入临时文件，调用 `agent-infra-internal platform-comment sync {task-id} --kind cancel --body-file {path} --agent {standard-agent-token}`
 - 调用 `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}`
@@ -97,7 +99,7 @@ agent-infra-internal task-verify {task-id} cancel-task.completed --format text
 - 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
 - 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
 
-将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+按 `.agents/rules/validation-output.md` 展示当次校验摘要；没有当次校验输出，不得声明完成。
 
 ### 8. 告知用户