@fitlab-ai/agent-infra 0.11.6 → 0.11.7

package/lib/task/verification-engine.ts

@@ -6,12 +6,9 @@ import { execFileSync } from "node:child_process";
 import { fileURLToPath } from "node:url";
 
 import {
-  extractReviewBaseline,
   extractReviewTargetHead,
   extractReviewedHead,
   extractReviewDiffBase,
-  extractReviewDiffFingerprint,
-  extractReviewedSnapshotTree,
   findAuthoritativeReviewCodeArtifact,
   loadPostReviewConfig,
   parseReviewVerdict,
@@ -23,7 +20,6 @@ import { inspectPlatformPullRequest } from "../platform/pull-requests.ts";
 import { resolveMaterializedReviewedHeadRelation } from "../platform/change-request-git-evidence.ts";
 import { resolveReviewedHeadRelation } from "../platform/merged-pr-equivalence.ts";
 import { resolveLocalReviewedCommitRelation } from "../git/reviewed-commit-equivalence.ts";
-import { resolveBranchWorktree } from "../git/branch-worktree.ts";
 import { parseTypedTaskFrontmatter } from "./frontmatter.ts";
 import { LEDGER_TERMINAL, LEDGER_SECTION_MISSING_CODE, LEDGER_SECTION_MISSING_MESSAGE, parseLedgerDocument, summarizeLedgerStage, validateLedgerRows } from "./ledger.ts";
 import type { LedgerRow } from "./ledger.ts";
@@ -33,12 +29,10 @@ import { inspectDecisionDetailDuplicates } from "./decision-details.ts";
 import { parseImplementationInputs, type ImplementationInput } from "./implementation-inputs.ts";
 import { scanVisibleMarkdown } from "./markdown.ts";
 import { loadVerificationConfig } from "./verification-config.ts";
-import { snapshotReview } from "../git/review-snapshot.ts";
 import { inspectActivityLog } from "./activity-log.ts";
 import { parseWorkflowWarnings } from "./workflow-warnings.ts";
 import { OrchestrationStateError, readRun } from "./orchestration.ts";
 import type { OrchestrationRun } from "./orchestration.ts";
-import { resolveDeliveryTarget } from "./delivery-target.ts";
 import { readPrDeliveryFact } from "./pr-delivery-fact.ts";
 import { validateLocalArtifact } from "./local-artifact-finalization.ts";
 import { getArtifactSchema } from "./artifact-schema.ts";
@@ -50,6 +44,8 @@ import { readManualValidationCompletion } from "./manual-validation-completion.t
 import { sha256File } from "./artifact-receipts.ts";
 import { summaryCommentState } from "../platform/pr-summary.ts";
 import { taskIssueIdentity } from "../platform/task-identities.ts";
+import { hasArtifactCompletionFact, hasArtifactCompletionLog } from './completion-facts.ts';
+import { inspectReviewIdentity } from './review-identity.ts';
 
 const TASK_ENUMS = {
   type: ["feature", "bugfix", "refactor", "docs", "chore"],
@@ -1159,12 +1155,16 @@ function checkReviewFact({ taskDir, artifactFile, repositoryRoot }: any): any {
   }
 
   const content = fs.readFileSync(resolvedArtifact.path, "utf8");
+  if (!hasArtifactCompletionFact(task.content, resolvedArtifact.path, 'review-code.completed')) {
+    return failResult("review-fact", `Review Code completion fact does not match ${path.basename(resolvedArtifact.path)}`);
+  }
+  if (!hasArtifactCompletionLog(task.content, path.basename(resolvedArtifact.path), 'review-code.completed')) {
+    return failResult("review-fact", `Review Code completion entry does not reference ${path.basename(resolvedArtifact.path)}`);
+  }
   const verdict = parseReviewVerdict(content);
   const reviewTargetHead = extractReviewTargetHead(content);
   const reviewReviewedHead = extractReviewedHead(content);
   const reviewDiffBase = extractReviewDiffBase(content);
-  const reviewedFingerprint = extractReviewDiffFingerprint(content);
-  const reviewedTree = extractReviewedSnapshotTree(content);
 
   if (!["通过", "需要修改", "拒绝", "Approved", "Changes Requested", "Rejected"].includes(verdict)) {
     return failResult("review-fact", `Unsupported review verdict '${verdict}'`);
@@ -1179,86 +1179,20 @@ function checkReviewFact({ taskDir, artifactFile, repositoryRoot }: any): any {
     return failResult("review-fact", "Review fact must record target head, reviewed head, and diff base");
   }
 
-  let gitRoot;
-  let head;
-  let baseline;
-  let targetHead;
-  let diffBase;
-  try {
-    const taskRepositoryRoot = execFileSync("git", ["-C", taskDir, "rev-parse", "--show-toplevel"], { encoding: "utf8" }).trim();
-    gitRoot = reviewWorktreeForTask(taskRepositoryRoot, String(task.metadata.branch || "").trim()) ?? taskRepositoryRoot;
-    head = execFileSync("git", ["-C", gitRoot, "rev-parse", "HEAD"], { encoding: "utf8" }).trim();
-    const target = resolveDeliveryTarget(gitRoot, { remote: deliveryRemote, baseRef: deliveryBaseRef });
-    if (!target.ok) throw new Error(target.message);
-    const reviewedRef = reviewReviewedHead;
-    baseline = execFileSync("git", ["-C", gitRoot, "rev-parse", `${reviewedRef}^{commit}`], { encoding: "utf8" }).trim();
-    targetHead = execFileSync("git", ["-C", gitRoot, "rev-parse", `${reviewTargetHead}^{commit}`], { encoding: "utf8" }).trim();
-    const computed = execFileSync("git", ["-C", gitRoot, "merge-base", baseline, targetHead], { encoding: "utf8" }).trim();
-    diffBase = execFileSync("git", ["-C", gitRoot, "rev-parse", `${reviewDiffBase}^{commit}`], { encoding: "utf8" }).trim();
-    if (diffBase !== computed) throw new Error('saved review diff base does not match merge-base(reviewed head, target head)');
-  } catch {
-    return blockedResult(
-      "review-fact",
-      `Unable to resolve saved review commits in the task repository; re-run review-code`
-    );
-  }
-
-  if (baseline !== head) {
-    return failResult(
-      "review-fact",
-      `Reviewed head ${baseline.slice(0, 8)} does not match current HEAD ${head.slice(0, 8)}; re-run review-code`
-    );
-  }
-
-  let actualSnapshot;
-  try {
-    actualSnapshot = snapshotReview({
-      cwd: gitRoot,
-      mode: "worktree",
-      baseline,
-      diffBase,
-      globs: resolvePostReviewGlobs({}, loadPostReviewConfig(repositoryRoot))
-    });
-  } catch {
-    return blockedResult(
-      "review-fact",
-      `Unable to recompute reviewed diff fingerprint from baseline ${baseline.slice(0, 8)}; re-run review-code`
-    );
-  }
-
-  if (actualSnapshot.fingerprint !== reviewedFingerprint) {
-    return failResult(
-      "review-fact",
-      `Reviewed diff fingerprint does not match the current worktree for baseline ${baseline.slice(0, 8)}; re-run review-code`
-    );
-  }
-
-  if (!reviewedTree || actualSnapshot.tree !== reviewedTree) {
-    return failResult(
-      "review-fact",
-      `Reviewed snapshot tree does not match the current worktree for baseline ${baseline.slice(0, 8)}; re-run review-code`
-    );
+  const identity = inspectReviewIdentity(taskDir, content, repositoryRoot);
+  if (identity.status !== 'matched' || !identity.reviewedHead) {
+    return failResult('review-fact', `Review identity is ${identity.status}: ${identity.message}; re-run review-code`);
   }
+  const baseline = identity.reviewedHead;
 
   if (["通过", "Approved"].includes(verdict)) {
     const lastReviewedCommit = String(task.metadata.last_reviewed_commit || "").trim();
-    const cleanSnapshot = actualSnapshot.tree === execFileSync(
-      "git",
-      ["-C", gitRoot, "rev-parse", `${baseline}^{tree}`],
-      { encoding: "utf8" }
-    ).trim();
-    if (cleanSnapshot && lastReviewedCommit !== baseline) {
+    if (lastReviewedCommit !== baseline) {
       return failResult(
         "review-fact",
         `Approved clean review must set task last_reviewed_commit to reviewed head ${baseline.slice(0, 8)}`
       );
     }
-    if (!cleanSnapshot && lastReviewedCommit) {
-      return failResult(
-        "review-fact",
-        "Approved review with uncommitted changes must remain unanchored until commit"
-      );
-    }
   }
 
   return passResult(
@@ -1267,13 +1201,6 @@ function checkReviewFact({ taskDir, artifactFile, repositoryRoot }: any): any {
   );
 }
 
-function reviewWorktreeForTask(repositoryRoot: string, branch: string): string | null {
-  if (!branch) return null;
-  const worktree = resolveBranchWorktree(repositoryRoot, branch);
-  if (worktree) return worktree;
-  throw new Error(`Task branch '${branch}' is not checked out in a registered worktree`);
-}
-
 function resolvePostReviewBaseline({ gitRoot, lastReviewedCommit, reviewArtifact }: any): any {
   if (SHA_PATTERN.test(lastReviewedCommit) && gitCommitExists(gitRoot, lastReviewedCommit)) {
     return { ok: true, sha: lastReviewedCommit };

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/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fitlab-ai/agent-infra",
-  "version": "0.11.6",
+  "version": "0.11.7",
   "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/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.
 

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 资格审计契约。
 

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/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

@@ -93,6 +93,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

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

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

@@ -23,7 +23,7 @@ This stage consumes only the canonical path fact parsed by core from the latest
 
 Before generating the implementation report, read `.agents/rules/evidence-reporting.md`. Successful tests record the command, target scope, status or structured result, actual result, and uncovered parts; failures, blocking conditions, or disputes retain a reproducible entry point, exact location, and decisive excerpt instead of complete successful stdout.
 
-- 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 implementation report; 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 implementation report; unknown or unconfirmed constraints must not automatically exclude a candidate
 - Follow the lifecycle input selected by core: `analysis.md` / `analysis-r{N}.md` for the streamlined path, and `plan.md` / `plan-r{N}.md` for the standard or full path
 - 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
 - Read `.agents/rules/compatibility-policy.md` before implementation. Implement only the compatibility budget explicitly approved by the plan; never retain old branches, result contracts, or migration shims merely to be “safe”
@@ -165,6 +165,8 @@ If task.md has a valid `platform_issue_identity`, read `.agents/rules/issue-sync
 agent-infra-internal task-verify {task-id} code.completed --artifact {code-artifact} --format text
 ```
 
+Present the verification summary per `.agents/rules/validation-output.md`, retaining necessary failure, blocked, and soft-warning diagnostics.
+
 ### 13. Tell the User
 
 Use `reference/output-template.md` (or `reference/fix-mode.md` in fix mode) and render the selected next-step commands through the shared helper. Do not push, create a PR, or invoke the `commit` skill here.

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

@@ -23,7 +23,7 @@ description: >
 
 生成实现报告时，先读取 `.agents/rules/evidence-reporting.md`。成功测试记录命令、目标范围、状态/结构化结果、实际结果和未覆盖部分；失败、阻塞或争议保留复现入口、准确位置和决定性摘录，不默认粘贴完整成功 stdout。
 
-- 涉及候选资格或 `HD-N` 判断时，先读取 `.agents/rules/decision-qualification.md`，基于 task.md 规范化约束/候选完成资格审计，并在实现报告记录五张资格审计表；不得把来源不明或未确认约束自动升级为排除条件
+- 涉及候选资格或 `HD-N` 判断时，先读取 `.agents/rules/decision-qualification.md`，基于 task.md 规范化约束/候选完成资格审计，并在实现报告记录三张资格审计决策表和资格快照；不得把来源不明或未确认约束自动升级为排除条件
 - 严格遵循核心选择的最新生命周期输入：精简路径为 `analysis.md` / `analysis-r{N}.md`，标准或完整路径为 `plan.md` / `plan-r{N}.md`
 - 生成会同步到 Issue 的任务或生命周期 Markdown 前，先读取 `.agents/rules/sync-content-generation.md` 并遵循其中的生成端约束；同步端不解析或改写正文
 - 实现前读取 `.agents/rules/compatibility-policy.md`；只实现方案明确批准的兼容预算，不以“稳妥”为由保留旧分支、旧结果契约或迁移 shim
@@ -217,7 +217,7 @@ agent-infra-internal task-verify {task-id} code.completed --artifact {code-artif
 - 退出码 1（校验失败）-> 根据输出修复问题后重新运行校验
 - 退出码 2（网络中断）-> 停止执行并告知用户需要人工介入
 
-将校验输出保留在回复中作为当次验证输出。没有当次校验输出，不得声明完成。
+按 `.agents/rules/validation-output.md` 展示当次校验摘要；没有当次校验输出，不得声明完成。
 
 ### 13. 告知用户
 

package/templates/.agents/skills/code-task/reference/report-template.en.md

@@ -26,7 +26,7 @@ Use this structure when creating `code.md` or `code-r{N}.md`.
 
 ## Qualification Audit
 
-> Use `.agents/rules/decision-qualification.md` and fill these five tables.
+> Include this section only when this stage actually evaluates candidate qualification, constraint dependencies, or human-decision eligibility. In that case, record all three decision tables and the qualification snapshot per `.agents/rules/decision-qualification.md`; otherwise omit this section entirely.
 
 ### Constraint Dependencies
 | constraint_id | constraint_digest | role | evidence |
@@ -40,13 +40,9 @@ Use this structure when creating `code.md` or `code-r{N}.md`.
 | decision_id | classification | evidence |
 | --- | --- | --- |
 
-### Upstream Relations
-| upstream_family | upstream_artifact | upstream_round | upstream_sha256 | relation |
-| --- | --- | --- | --- | --- |
-
-### Dependency Snapshot
-| task_input_digest | non_constraint_input_digest | upstream_artifact_digest |
-| --- | --- | --- |
+### Qualification Snapshot
+| task_input_digest | non_constraint_input_digest |
+| --- | --- |
 
 ## Changed Files
 

package/templates/.agents/skills/code-task/reference/report-template.zh-CN.md

@@ -26,7 +26,7 @@
 
 ## 资格审计
 
-> 按 `.agents/rules/decision-qualification.md` 填写以下五张表。
+> 仅当本阶段实际判断候选资格、约束依赖或人工裁决资格时填写本节，并按 `.agents/rules/decision-qualification.md` 完整记录三张决策表和资格快照；否则删除整个审计段。
 
 ### 约束依赖
 | constraint_id | constraint_digest | role | evidence |
@@ -40,13 +40,9 @@
 | decision_id | classification | evidence |
 | --- | --- | --- |
 
-### 上游关系
-| upstream_family | upstream_artifact | upstream_round | upstream_sha256 | relation |
-| --- | --- | --- | --- | --- |
-
-### 依赖快照
-| task_input_digest | non_constraint_input_digest | upstream_artifact_digest |
-| --- | --- | --- |
+### 资格快照
+| task_input_digest | non_constraint_input_digest |
+| --- | --- |
 
 ## 变更文件
 

package/templates/.agents/skills/commit/SKILL.en.md

@@ -92,7 +92,7 @@ date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 agent-infra-internal task-verify {task-id} commit.completed --format text
 ```
 
-Do not claim task finalization without fresh verification output.
+Present the verification summary per `.agents/rules/validation-output.md`; do not claim task finalization without fresh verification output.
 
 ## 6. Render the next step
 

package/templates/.agents/skills/commit/SKILL.zh-CN.md

@@ -92,7 +92,7 @@ date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 agent-infra-internal task-verify {task-id} commit.completed --format text
 ```
 
-没有当次校验输出，不得声明任务收尾完成。
+按 `.agents/rules/validation-output.md` 展示校验摘要；没有当次校验输出，不得声明任务收尾完成。
 
 ## 6. 输出下一步
 

package/templates/.agents/skills/complete-manual-validation/SKILL.en.md

@@ -126,7 +126,7 @@ Handle the result:
 Report:
 - Artifact path
 - PR summary sync result
-- Current verification output
+- Present the completion verification summary per `.agents/rules/validation-output.md`
 - Suggested next step: enter the final closing flow and run /complete-task --task {task-ref}
 
 Before rendering the final output, read `.agents/rules/next-step-output.md` and append `Completed at: YYYY-MM-DD HH:mm:ss` as the absolute last line.

package/templates/.agents/skills/complete-manual-validation/SKILL.zh-CN.md

@@ -126,7 +126,7 @@ agent-infra-internal task-verify {task-id} manual-validation.completed --artifac
 输出：
 - 产物路径
 - PR 摘要同步结果
-- 当次完成校验输出
+- 按 `.agents/rules/validation-output.md` 展示当次完成校验摘要
 - 下一步建议：进入最终收尾流程，运行 /complete-task --task {task-ref}
 
 渲染最终输出前，先读取 `.agents/rules/next-step-output.md`，并在绝对最后一行追加 `Completed at: YYYY-MM-DD HH:mm:ss`。

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

@@ -164,6 +164,8 @@ After platform writes succeed and before moving the directory or releasing the s
 agent-infra-internal task-verify {task-id} complete-task.preflight --format text
 ```
 
+Present the verification summary per `.agents/rules/validation-output.md`, retaining necessary failure, blocked, and soft-warning diagnostics.
+
 This event runs only the required-PR delivery hard preflight; host finalization still enforces identity, concurrency, and local atomicity before lifecycle. Peripheral review/manual/platform checks run through `complete-task.completed` after lifecycle and are projected as warning/pending steps. On a hard-gate non-zero exit (fail/blocked), keep the task active, record the stable code/target, and stop.
 
 If a summary must mirror a human-decided `post-review-commit` exemption, make a best-effort sync in Step 4 with the original failure code/message, PRC id/evidence, and ruling details. A sync failure records `SUMMARY_SYNC_FAILED` and still allows lifecycle; terminal verification decides the final state.

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

@@ -163,6 +163,8 @@ agent-infra-internal task-warning {task-id} add --step complete-task --severity
 agent-infra-internal task-verify {task-id} complete-task.preflight --format text
 ```
 
+按 `.agents/rules/validation-output.md` 展示当次校验摘要；失败、阻塞和软警告保留必要诊断。
+
 该事件只执行 required-PR delivery hard preflight；身份、并发和本地原子性仍由宿主 finalization 强制执行。外围 review/manual/platform 检查在 lifecycle 后由 `complete-task.completed` 处理，并投影为 warning/pending steps。硬门禁退出码非 0（fail/blocked）时，任务继续留在 active，记录稳定 code/target 后停止。
 
 若需要在摘要中镜像 `post-review-commit` 的 human-decided exemption，在步骤 4 尽力同步原始 failure code/message、PRC id/evidence 和裁决信息；同步失败只记录 `SUMMARY_SYNC_FAILED` warning，仍继续生命周期。最终是否完成由生命周期后的 terminal verification 决定。

package/templates/.agents/skills/create-pr/SKILL.en.md

@@ -102,6 +102,8 @@ If this operation is associated with `{task-id}`, run the verification gate to c
 agent-infra-internal task-verify {task-id} create-pr.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