@fitlab-ai/agent-infra 0.9.13 → 0.9.14

package/lib/task/verification-engine.ts

@@ -35,6 +35,9 @@ import { OrchestrationStateError, readRun } from "./orchestration.ts";
 import { resolveDeliveryTarget } from "./delivery-target.ts";
 import { readPrDeliveryFact } from "./pr-delivery-fact.ts";
 import { validateLocalArtifact } from "./local-artifact-finalization.ts";
+import { validateQualificationAudit } from "./qualification-audit.ts";
+import { getArtifactSchema } from "./artifact-schema.ts";
+import { inspectArtifactContract } from "./artifact-operations.ts";
 
 const TASK_ENUMS = {
   type: ["feature", "bugfix", "refactor", "docs", "chore"],
@@ -600,15 +603,45 @@ function checkArtifact({ taskDir, config, artifactFile, skillName }: any): any {
   }
 
   const content = fs.readFileSync(artifactPath, "utf8");
-  const requiredSections = config.required_sections || [];
+  let taskContent = "";
+  const taskPath = path.join(taskDir, "task.md");
+  if (fs.existsSync(taskPath)) {
+    try {
+      taskContent = fs.readFileSync(taskPath, "utf8");
+    } catch (error) {
+      return failResult("artifact", `Cannot read task qualification contract: ${error instanceof Error ? error.message : String(error)}`);
+    }
+  }
+  if (taskContent && /^review-(?:analysis|plan|code)$/.test(skillName)) {
+    const qualification = validateQualificationAudit(taskContent, content, { artifact: path.basename(artifactPath) });
+    if (!qualification.ok) return failResult("artifact", `${path.basename(artifactPath)} has qualification audit errors: ${qualification.code}: ${qualification.message}`);
+  }
+  const schemaFamily = skillName === "analyze-task"
+    ? "analysis"
+    : skillName === "review-analysis"
+      ? "review-analysis"
+      : skillName === "plan-task"
+        ? "plan"
+        : skillName === "review-plan"
+          ? "review-plan"
+          : skillName === "code-task"
+            ? "code"
+            : skillName === "review-code" ? "review-code" : null;
+  const schema = schemaFamily ? getArtifactSchema(schemaFamily) : null;
   const localFamily = skillName === "analyze-task"
     ? "analysis"
     : skillName === "plan-task" ? "plan" : skillName === "code-task" ? "code" : null;
+  if (schema) {
+    const structure = inspectArtifactContract(content, schema);
+    if (!structure.ok && !localFamily) {
+      return failResult("artifact", `${path.basename(artifactPath)} has shared structural errors: ${structure.diagnostics.map((item) => `${item.code}: ${item.message}`).join('; ')}`);
+    }
+  }
   if (localFamily) {
     const local = validateLocalArtifact(content, {
       family: localFamily,
-      requiredSections: requiredSections.filter((section: unknown): section is string => typeof section === "string"),
-      requiredPatterns: (config.required_patterns || []).filter((pattern: unknown): pattern is string => typeof pattern === "string")
+      ...(taskContent ? { taskContent } : {}),
+      artifact: path.basename(artifactPath)
     });
     if (!local.ok) {
       return failResult(
@@ -618,9 +651,16 @@ function checkArtifact({ taskDir, config, artifactFile, skillName }: any): any {
     }
     return passResult(
       "artifact",
-      `${path.basename(artifactPath)} passed (${requiredSections.length} sections)`
+      `${path.basename(artifactPath)} passed (${schema?.sections.length ?? 0} sections)`
     );
   }
+  if (schema) {
+    return passResult(
+      "artifact",
+      `${path.basename(artifactPath)} passed (${schema.sections.length} sections)`
+    );
+  }
+  const requiredSections = config.required_sections || [];
   const missingSections = requiredSections.filter(
     (section: any) => !new RegExp(`^##\\s+${escapeRegExp(section)}\\s*$`, "m").test(content)
   );
@@ -786,6 +826,7 @@ function checkActivityLog({ taskDir, config }: any): any {
   let previousTimestamp = "";
   let latestAction = "";
   let latestTimestamp = "";
+  const doneActions: string[] = [];
 
   for (const entry of entries) {
     const match = entry.match(ACTIVITY_LOG_PATTERN);
@@ -805,6 +846,16 @@ function checkActivityLog({ taskDir, config }: any): any {
     if (!ACTIVITY_LOG_STARTED_RE.test(action)) {
       latestTimestamp = timestamp;
       latestAction = action;
+      doneActions.push(action);
+    }
+  }
+
+  if (config.expected_action_pattern && !new RegExp(config.expected_action_pattern).test(latestAction)) {
+    const expected = new RegExp(config.expected_action_pattern);
+    let index = doneActions.length - 1;
+    while (index >= 0 && doneActions[index] === 'Commit' && !expected.test(doneActions[index]!)) index -= 1;
+    if (index >= 0 && expected.test(doneActions[index]!)) {
+      latestAction = doneActions[index]!;
     }
   }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fitlab-ai/agent-infra",
-  "version": "0.9.13",
+  "version": "0.9.14",
   "description": "Bootstrap tool for AI multi-tool collaboration infrastructure — works with Claude Code, Codex, Antigravity CLI, and OpenCode",
   "license": "MIT",
   "type": "module",
@@ -54,6 +54,7 @@
     "@clack/prompts": "1.7.0",
     "@larksuiteoapi/node-sdk": "^1.68.0",
     "cross-spawn": "^7.0.6",
+    "fs-ext-extra-prebuilt": "2.2.13",
     "picocolors": "1.1.1",
     "semver": "^7.8.1",
     "smol-toml": "^1.6.1",
@@ -65,6 +66,7 @@
     "prepare": "git config core.hooksPath .git-hooks || true",
     "typecheck": "tsc -p tsconfig.test.json --noEmit && tsc -p tsconfig.jschecks.json --noEmit",
     "test:smoke": "node scripts/run-tests.js \"tests/unit/**/*.test.ts\"",
+    "test:smoke:fast": "node scripts/run-tests.js --skip-build \"tests/unit/**/*.test.ts\"",
     "test:core": "node scripts/run-tests.js \"tests/unit/**/*.test.ts\" \"tests/integration/**/*.test.ts\"",
     "test:integration": "node scripts/run-tests.js \"tests/integration/**/*.test.ts\" \"tests/e2e/**/*.test.ts\"",
     "check": "npm run typecheck && npm test",
@@ -83,5 +85,8 @@
   },
   "overrides": {
     "axios": "1.18.1"
+  },
+  "allowScripts": {
+    "fs-ext-extra-prebuilt@2.2.13": true
   }
 }

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

@@ -13,7 +13,9 @@ so you can quickly find "which ones to read" without opening each file.
 - [`version-stamp.md`](version-stamp.md) — How and when to stamp `agent_infra_version`.
 - [`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.
 - [`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.
 
 ## Issue / PR
 

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

@@ -12,7 +12,9 @@
 - [`version-stamp.md`](version-stamp.md) — `agent_infra_version` 版本戳的取值命令与写入时机。
 - [`debugging-guide.md`](debugging-guide.md) — 结构化调试流程：收集证据→形成假设→验证假设→修复根因，禁止盲目改代码重试。
 - [`compatibility-policy.md`](compatibility-policy.md) — 兼容性默认关闭：准入证据、实现边界、退出条件与生命周期审查要求。
+- [`evidence-reporting.md`](evidence-reporting.md) — 生命周期报告的状态核对、成功摘要、异常证据、身份字段和敏感信息边界。
 - [`sync-content-generation.md`](sync-content-generation.md) — 同步到 Issue 的任务和生命周期 Markdown 生成约束。
+- [`decision-qualification.md`](decision-qualification.md) — 约束、候选、人工确认和六类 artifact 资格审计契约。
 
 ## Issue / PR
 

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

@@ -0,0 +1,22 @@
+# Decision Qualification and Constraint Audit
+
+Any analysis, plan, implementation, or review that decides whether a human decision is needed must audit qualification from the normalized constraints and candidates in `task.md` before creating `HD-N`.
+
+## Single source of truth
+
+- 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.
+
+## Status and confirmation
+
+- A `confirmed` constraint requires source evidence, the current semantic digest, and a qualification confirmation record; a confirmation for an old digest cannot be reused.
+- `derived`, `assumption`, `open`, `conflicted`, and `superseded` are pending facts and cannot automatically exclude a candidate.
+- The internal proposal entry point may write only non-confirmed constraints and `pending` candidates. It cannot write actor, QCR, confirmed, or approval fields.
+- `agent-infra-internal task-qualification` is the internal confirmation, supersession, and revocation entry point for agents and skills; ordinary users are not exposed to the constraint-digest protocol. `human-declared` is an audit label, not identity authentication. On confirmation, the core generates the QCR and binds it to the current post-write per-constraint digest, request id, time, and a single-line rationale. Supersession and revocation move the constraint to `superseded` and `open`, respectively, clear current approval evidence, and retain historical QCRs.
+
+## 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.
+
+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.

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

@@ -0,0 +1,22 @@
+# 决策资格与约束审计
+
+涉及“是否需要人工裁决”的分析、方案、实现或审查，必须先基于 `task.md` 的规范化约束和候选表完成资格审计，再决定是否创建 `HD-N`。
+
+## 唯一事实源
+
+- `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。
+
+## 状态与确认
+
+- `confirmed` 约束必须有来源证据、当前语义 digest 和 `资格确认记录`；旧 digest 的确认不能复用。
+- `derived`、`assumption`、`open`、`conflicted`、`superseded` 只能作为待审事实，不能自动排除候选。
+- 内部 proposal 入口只能写入非 confirmed 约束和 `pending` 候选，不能写 actor、QCR、confirmed 或 approval 字段。
+- `agent-infra-internal task-qualification` 是供 Agent/skill 使用的内部确认、替代和撤销入口，不向普通用户暴露 constraint digest 协议；`human-declared` 是审计标签，不是身份认证。确认时 QCR 由核心生成并绑定确认写入后的当前单约束 digest、request id、时间和单行理由；替代与撤销分别把约束转为 `superseded` 与 `open`，清空当前 approval evidence，并保留历史 QCR。
+
+## 失效与审查
+
+约束变化时，只有声明受影响 `C-N` 的 artifact 才能成为直接失效种子，并沿真实上游关系的下游闭包传播；六类 artifact（含 review）对等处理。快照、关系图或变化分类无法证明为纯约束变化时，回退既有全量失效路径。新完成的 source artifact、自身 receipt 和派生快照不作为旧图目标。
+
+缺失、未知引用、digest 不匹配、悬空关系或环都必须 fail closed。排版变化不应改变语义 digest；语义、来源、状态、候选或上游 identity 变化必须触发重新审计。

package/templates/.agents/rules/evidence-reporting.en.md

@@ -0,0 +1,28 @@
+# Lifecycle Evidence Reporting
+
+This rule governs lifecycle reports persisted in the task workspace or synchronized to an Issue. It defines the minimum evidence semantics without changing artifact identity, receipts, synchronization, or restore protocols.
+
+## State Check
+
+- Record the `task-snapshot` command and its task, artifact, and scope.
+- For normal results, record the key conclusion and exceptions; do not repeat the full directory listing or `task.md` tail.
+- For identity mismatches, failures, blocking conditions, or disputes, retain the decisive raw lines that support the judgment.
+
+## Successful Checks
+
+Every successful check records the command or an allowed public command name, target and scope, exit status or structured result, actual result, and uncovered parts. Do not write only “passed” or “tests passed”, and do not paste complete successful stdout by default.
+
+## Failures, Blocking Conditions, and Disputes
+
+Record a reproducible command or entry point, the exact file/line/object/version location, exit status, and the smallest decisive excerpt supporting the conclusion. If reproduction is unavailable, state the limitation explicitly rather than presenting incomplete evidence as success.
+
+## Preserved Identity and Security Boundaries
+
+- Preserve artifact SHA-256, semantic digest, review head, receipt, request-id, snapshot tree, and platform marker exactly.
+- The Issue continues to mirror the complete report; the report must not depend on logs accessible only on the local machine.
+- Manual validation keeps its stricter basename-only and sanitized-result rules; this shared rule does not expand public fields.
+- A `$ ` command line satisfies the structural gate but does not require complete successful output.
+
+## Evidence Pairing
+
+Pair every verification claim with a `$ ` command and a proportionate result summary. Include a decisive raw excerpt only for failure, blocking, or dispute conclusions. When a command contains sensitive arguments, use its allowed public name or a redacted command.

package/templates/.agents/rules/evidence-reporting.zh-CN.md

@@ -0,0 +1,28 @@
+# 生命周期报告证据记录规则
+
+本规则约束会持久化到任务目录或同步到 Issue 的生命周期报告。它统一报告的最低证据语义，不改变 artifact 身份、receipt、同步或恢复协议。
+
+## 状态核对
+
+- 记录 `task-snapshot` 命令及任务、产物和检查范围。
+- 正常结果记录关键结论和异常；不要重复粘贴完整目录清单或 `task.md` 尾部。
+- 身份不一致、失败、阻塞或争议时，保留能支持判断的决定性原文行。
+
+## 成功检查
+
+成功路径至少记录：命令或允许公开的命令名称、目标与检查范围、退出状态或结构化结果、实际结果、未覆盖部分。不能只写“通过”或“测试通过”，也不默认粘贴完整成功 stdout。
+
+## 失败、阻塞和争议
+
+记录可复现的命令或调用入口、准确的文件/行号/对象/版本位置、退出状态，以及决定结论的最小决定性摘录。无法复现时明确写出限制，不把不完整证据写成成功。
+
+## 不变的身份与安全边界
+
+- artifact SHA-256、semantic digest、review head、receipt、request-id、快照树和平台 marker 必须精确保留。
+- Issue 继续镜像报告全文；报告不得依赖只有本机可访问的日志。
+- 人工验证继续使用 basename-only、sanitized result 等更严格规则；共享规则不扩大可公开字段。
+- `$ ` 命令行标记满足结构门禁，但不要求附带完整成功输出。
+
+## 证据配对
+
+报告中的每个验证断言都应配一个 `$ ` 命令和相称结果摘要；只有失败、阻塞或争议结论才附决定性原文摘录。命令含敏感参数时使用允许公开的命令名或脱敏命令。

package/templates/.agents/rules/label-milestone-setup.en.md

@@ -2,17 +2,17 @@
 
 Read this rule before initializing labels or milestones, or before changing milestone metadata during release work.
 
-## Entry points
+## Runtime intent entry points
 
-Use the shared scripts rather than composing provider commands in a skill:
+Use the internal runtime intents rather than composing platform commands in a skill:
 
 ```text
-bash .agents/skills/init-labels/scripts/init-labels.sh [--cleanup-stale-in]
-bash .agents/skills/init-milestones/scripts/init-milestones.sh "$ARGUMENTS"
+agent-infra-internal platform-metadata init-labels [--cleanup-stale-in]
+agent-infra-internal platform-metadata init-milestones [--history]
 ```
 
-`init-labels.sh` reads the repository's `labels.in` configuration, creates or updates the declared `in:` labels, and preserves unrelated labels. `--cleanup-stale-in` is destructive and may only be passed after explicit confirmation; it removes stale `in:` labels that are no longer declared.
+The `init-labels` runtime intent reads the repository's `labels.in` configuration, creates or updates the declared `in:` labels, and preserves unrelated labels. `--cleanup-stale-in` is destructive and may only be passed after explicit confirmation; it removes stale `in:` labels that are no longer declared.
 
-`init-milestones.sh` owns milestone inference and the provider-specific write path. Callers must pass the requested arguments through unchanged and must not rebuild milestone discovery, ordering, branch ancestry, or write logic.
+The `init-milestones` runtime intent owns milestone planning and result reporting. Callers must pass the requested arguments through unchanged and must not rebuild milestone discovery, ordering, or write logic.
 
-Both scripts return a stable status. A successful no-op is still success; a degraded result must be reported without claiming that remote metadata was changed. Failed or cancelled operations must not be reported as completed.
+Both intents return a stable status. A successful no-op is still success; a degraded result must be reported without claiming that remote metadata was changed. Failed or cancelled operations must not be reported as completed.

package/templates/.agents/rules/label-milestone-setup.zh-CN.md

@@ -2,17 +2,17 @@
 
 在初始化 label、milestone，或在发布工作中修改 milestone 元数据前，先阅读本规则。
 
-## 入口
+## Runtime intent 入口
 
-SKILL 应调用共享脚本，不得自行拼装 provider 命令：
+SKILL 应调用内部 runtime intent，不得自行拼装平台命令：
 
 ```text
-bash .agents/skills/init-labels/scripts/init-labels.sh [--cleanup-stale-in]
-bash .agents/skills/init-milestones/scripts/init-milestones.sh "$ARGUMENTS"
+agent-infra-internal platform-metadata init-labels [--cleanup-stale-in]
+agent-infra-internal platform-metadata init-milestones [--history]
 ```
 
-`init-labels.sh` 读取仓库的 `labels.in` 配置，创建或更新声明的 `in:` label，并保留无关 label。`--cleanup-stale-in` 具有破坏性，只有在得到明确确认后才能传入；它会删除不再声明的过期 `in:` label。
+`init-labels` runtime intent 读取仓库的 `labels.in` 配置，创建或更新声明的 `in:` label，并保留无关 label。`--cleanup-stale-in` 具有破坏性，只有在得到明确确认后才能传入；它会删除不再声明的过期 `in:` label。
 
-`init-milestones.sh` 负责 milestone 推断和 provider 写入路径。调用方应原样传递请求参数，不得重新实现 milestone 发现、排序、分支祖先判断或写入逻辑。
+`init-milestones` runtime intent 负责 milestone 规划和结果报告。调用方应原样传递请求参数，不得重新实现 milestone 发现、排序或写入逻辑。
 
-两个脚本都返回稳定状态。成功的 no-op 仍算成功；degraded 结果必须如实报告，不能声称远端元数据已变更。失败或取消的操作不得报告为已完成。
+两个 intent 都返回稳定状态。成功的 no-op 仍算成功；degraded 结果必须如实报告，不能声称远端元数据已变更。失败或取消的操作不得报告为已完成。

package/templates/.agents/rules/local-artifact-repair.en.md

@@ -5,7 +5,7 @@ This rule applies when `analyze-task`, `plan-task`, or `code-task` handles **the
 ## Pre-completion gate for analysis, plan, and code artifacts
 
 - `analyze-task`, `plan-task`, and `code-task` must call `task-artifact ... finalize-local` before publishing a completed event; pass only that call's `artifactSha256` and `semanticDigest` to the completed event.
-- `finalize-local` does not modify the artifact or task state, but it writes a one-shot local provenance intent in the repository workspace. After `failed`, the model may make one minimal edit in the same artifact only when `repairable=true` and the diagnostic explicitly describes a one-line replacement, then rerun the same call completely; count each byte-changing edit, up to 8.
+- `finalize-local` does not modify the artifact or task state, but it writes a one-shot local provenance intent in the repository workspace. After `failed`, the model may make one minimal edit in the same artifact only when `repairable=true` and the diagnostic explicitly describes one provably safe structural operation (the current shared engine operations are `replace-line` and `insert-section`), then rerun the same call completely; count each byte-changing edit, up to 8.
 - The first repairable failure's semantic digest is retained in that intent; a later `passed` result must match the baseline, and the completed event must verify and atomically transition the same intent to `consumed` before writing `task.md` under the task lock. A consumption failure must not write the task; the consumed intent is durable and retryable, so no failure-prone post-write deletion is attempted. Do not replace a failed baseline with a newly computed digest or publish a completed event without the finalizer.
 - After `failed`, no progress, or a repeated diagnostic or fingerprint, do not publish a completed event. After `passed`, do not rescan or manually write summary data.
 
@@ -40,6 +40,10 @@ If any condition fails, stop immediately without invoking a model edit. The mode
 
 The repair count exists only in the in-memory context of the current skill invocation. Do not write it to `task.md`, the ledger, or a public receipt. Do not create different normal budgets by error code, skill, or problem type.
 
+## Shared Structural Engine
+
+The report skeleton is created by `agent-infra-internal task-artifact {task-id} init --family {family} --artifact {artifact}`. The skeleton writes only identity, headings, and `artifact-section:{family}:{section-id}` markers; it does not represent semantic completion. The current skill must fill each slot with real content. When the finalizer returns one provably safe structural operation, use that result's SHA and semantic digest with `task-artifact {task-id} repair --family {family} --artifact {artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`. Repair executes only the one operation from the shared engine, does not write `task.md`, the ledger, receipts, Git, or platform resources, and must be followed by a complete rerun of the original finalizer.
+
 ## Completion Events and User Output
 
 - After the final complete finalizer result succeeds, publish the review completed event using that same result's provenance, ledger state, verdict, and counts. Generate cross-stage next-step commands only when `stageStatus.canAdvance=true` and the verdict is Approved; when `canAdvance=false`, still record the result and route to same-stage revision/review.

package/templates/.agents/rules/local-artifact-repair.zh-CN.md

@@ -5,7 +5,7 @@
 ## 分析、方案和代码产物完成前门禁
 
 - `analyze-task`、`plan-task` 和 `code-task` 必须在发布 completed 事件前调用 `task-artifact ... finalize-local`；只有同一次返回的 `artifactSha256` 和 `semanticDigest` 才能传给 completed 事件。
-- `finalize-local` 不修改产物或任务状态，但会在仓库工作区写入一次性的本地 provenance intent。返回 `failed` 时，只有 `repairable=true` 且诊断明确为单行替换，模型才可在同一产物中执行一次最小编辑，然后完整重跑同一调用；每次实际字节修改计一次，最多 8 次。
+- `finalize-local` 不修改产物或任务状态，但会在仓库工作区写入一次性的本地 provenance intent。返回 `failed` 时，只有 `repairable=true` 且诊断明确为一个可证明安全的结构操作（当前共享引擎操作为 `replace-line` 或 `insert-section`），模型才可在同一产物中执行一次最小编辑，然后完整重跑同一调用；每次实际字节修改计一次，最多 8 次。
 - 首次可修复失败的 semantic digest 会保存在该 intent 中；后续 `passed` 必须匹配该基线，completed event 还必须在任务锁内验证并在写 task.md 前原子转换为 `consumed` 状态。消费失败时不得写任务；转换后的 intent 是可重试的 durable 记录，成功写入后不再执行可能失败的后置删除。不得用重新计算的新摘要替换失败基线，也不得绕过 finalizer 直接发布 completed event。
 - 返回 `failed`、无进展、诊断或指纹重复时不得发布 completed 事件；返回 `passed` 后也不得重新扫描或手工补写摘要。
 
@@ -40,6 +40,10 @@
 
 修复次数只存在于当前 skill invocation 的内存上下文，不写入 task.md、ledger 或公共 receipt。不得按错误码、技能或问题类型设置不同的正常预算。
 
+## 共享结构引擎
+
+报告骨架由 `agent-infra-internal task-artifact {task-id} init --family {family} --artifact {artifact}` 创建。骨架只写身份、标题和 `artifact-section:{family}:{section-id}` marker，不代表语义完成；槽位必须由当前 skill 填入真实内容。finalizer 返回单一可证明结构操作时，使用同一返回值的 SHA 和 semantic digest 调用 `task-artifact {task-id} repair --family {family} --artifact {artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`。repair 只执行共享引擎给出的一个结构操作，不写 task.md、ledger、receipt、Git 或平台资源，之后必须完整重跑原 finalizer。
+
 ## 完成事件与用户输出
 
 - 最终一次完整 finalizer 成功后，必须使用同一次返回的 provenance、账本状态、verdict 和计数发布 review completed 事件；`stageStatus.canAdvance=true` 且结论为 Approved 时才可生成跨阶段 next-step 命令，`canAdvance=false` 时仍须登记结果并路由到同阶段修订/复审。

package/templates/.agents/rules/security-alerts.en.md

@@ -2,19 +2,19 @@
 
 Read this rule before importing or dismissing dependency or code-scanning alerts.
 
-## Shared entry point
+## Shared runtime intent
 
-All callers use the shared security script and parse its single JSON result:
+All callers use the runtime security intent and parse its single JSON result:
 
 ```text
-bash .agents/scripts/security-alerts.sh read-dependabot --number {number}
-bash .agents/scripts/security-alerts.sh dismiss-dependabot --number {number} --reason {api-reason} --comment-file {file}
-bash .agents/scripts/security-alerts.sh read-codescan --number {number}
-bash .agents/scripts/security-alerts.sh dismiss-codescan --number {number} --reason {api-reason} --comment-file {file}
+agent-infra-internal platform-security read --kind dependabot --number {number}
+agent-infra-internal platform-security dismiss --kind dependabot --number {number} --reason {reason} --comment-file {file}
+agent-infra-internal platform-security read --kind code-scanning --number {number}
+agent-infra-internal platform-security dismiss --kind code-scanning --number {number} --reason {reason} --comment-file {file}
 ```
 
 The result contains `status`, `operation`, and either `data` or `error.code` plus `error.message`. The status is one of `applied`, `no-op`, `degraded`, or `failed`. Diagnostics belong on stderr; stdout must contain exactly one JSON object.
 
-Read the current alert before any dismiss operation. A dismiss reason must use the provider API reason value, and the generated task or Issue comment must be passed through `--comment-file`.
+Read the current alert before any dismiss operation. The runtime intent validates the structured reason, and the generated task or Issue comment must be passed through `--comment-file`.
 
-Do not invoke a provider CLI directly from a SKILL. A degraded or failed result must be reported accurately, and cancelled or failed operations must not be recorded as successful.
+Do not execute platform commands or implement the platform state machine directly from a SKILL. A degraded or failed result must be reported accurately, and cancelled or failed operations must not be recorded as successful.

package/templates/.agents/rules/security-alerts.zh-CN.md

@@ -2,19 +2,19 @@
 
 在导入或关闭依赖告警、代码扫描告警前，先阅读本规则。
 
-## 共享入口
+## 共享 runtime intent 入口
 
-所有调用方都使用共享安全脚本，并解析其单个 JSON 结果：
+所有调用方都使用 runtime security intent，并解析其单个 JSON 结果：
 
 ```text
-bash .agents/scripts/security-alerts.sh read-dependabot --number {number}
-bash .agents/scripts/security-alerts.sh dismiss-dependabot --number {number} --reason {api-reason} --comment-file {file}
-bash .agents/scripts/security-alerts.sh read-codescan --number {number}
-bash .agents/scripts/security-alerts.sh dismiss-codescan --number {number} --reason {api-reason} --comment-file {file}
+agent-infra-internal platform-security read --kind dependabot --number {number}
+agent-infra-internal platform-security dismiss --kind dependabot --number {number} --reason {reason} --comment-file {file}
+agent-infra-internal platform-security read --kind code-scanning --number {number}
+agent-infra-internal platform-security dismiss --kind code-scanning --number {number} --reason {reason} --comment-file {file}
 ```
 
 结果包含 `status`、`operation`，以及 `data` 或 `error.code` 与 `error.message`。`status` 只能是 `applied`、`no-op`、`degraded` 或 `failed`。诊断信息写入 stderr；stdout 必须只包含一个 JSON 对象。
 
-任何关闭操作前都必须先读取当前告警。关闭原因必须使用 provider API 的 reason 值，生成的任务或 Issue 评论必须通过 `--comment-file` 传入。
+任何关闭操作前都必须先读取当前告警。关闭原因由 runtime intent 作为结构化输入校验，生成的任务或 Issue 评论必须通过 `--comment-file` 传入。
 
-SKILL 不得直接调用 provider CLI。degraded 或 failed 结果必须如实报告，取消或失败的操作不得记录为成功。
+SKILL 不得直接执行平台命令或实现平台状态机。degraded 或 failed 结果必须如实报告，取消或失败的操作不得记录为成功。

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

@@ -13,6 +13,11 @@ If the entry operands contain `--orchestrated`, bind `{execution-flag}` to `--or
 
 ## Boundary / Critical Rules
 
+### Persisted Report Evidence
+
+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
 - 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
@@ -25,7 +30,7 @@ Version stamp rule: when creating or updating `task.md` frontmatter, read `.agen
 
 After loading workflow / skill / rules instructions, and before any task-state judgment or user-visible conclusion, run the state check first. Reading instruction files does not count as an external-state action or conclusion.
 
-Run these commands and paste the raw output into this round's `## State Check` section:
+Run these commands and record the task/artifact scope, key result, and uncovered parts in this round's `## State Check` section; do not paste complete directory listings or task tails on normal success. Retain decisive raw lines only for failures, blocking conditions, identity mismatches, or disputes:
 
 ```bash
 agent-infra-internal task-snapshot {task-id} --format text
@@ -129,6 +134,14 @@ Follow the `analysis` step in `.agents/workflows/feature-development.yaml`:
 
 ### 6. Output Analysis Document
 
+Before writing this round's `{analysis-artifact}`, create the controlled report skeleton:
+
+```bash
+agent-infra-internal task-artifact {task-id} init --family analysis --artifact {analysis-artifact} --locale en
+```
+
+The skeleton contains identity metadata, stable section markers, and required headings only; real analysis content is required before the completion gate can pass. If the finalizer returns one provably safe structural error, call `task-artifact {task-id} repair --family analysis --artifact {analysis-artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`, then rerun the same finalizer.
+
 > Steps 6–9 are the **Scenario A (normal output)** path. **Scenario B (ask and early-exit)** already finished its state update, task-comment sync, and verification inside step 4 and STOPped, so it does not enter these steps.
 
 Create `.agents/workspace/active/{task-id}/{analysis-artifact}`.
@@ -143,7 +156,7 @@ Create `.agents/workspace/active/{task-id}/{analysis-artifact}`.
 
 ## State Check
 
-> Paste the raw Step 0 state-check command output; each command starts with `$ `.
+> Record the Step 0 state-check command, task/artifact scope, key result, and uncovered parts; each command starts with `$ `. Do not paste complete directory listings or task tails on normal success; retain decisive raw lines only for failures, blocking conditions, identity mismatches, or disputes.
 
 ## Requirement Source
 

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

@@ -13,6 +13,11 @@ description: >
 
 ## 行为边界 / 关键规则
 
+### 持久化报告证据
+
+生成分析报告时，先读取 `.agents/rules/evidence-reporting.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` 并遵循其中的生成端约束；同步端不解析或改写正文
@@ -25,7 +30,7 @@ description: >
 
 在加载 workflow / skill / rules 指令之后、做任何任务状态判断或用户可见结论之前，必须先执行状态核对。指令类文件读取不算对外动作或结论。
 
-运行以下命令，并把原文粘贴到本轮产物的 `## 状态核对` 段：
+运行以下命令，并在本轮产物的 `## 状态核对` 段记录任务/产物范围、关键结果和未覆盖部分；正常成功不粘贴完整目录清单或 `task.md` 尾部。失败、阻塞、身份不一致或争议时，附决定性原文行：
 
 ```bash
 agent-infra-internal task-snapshot {task-id} --format text
@@ -132,6 +137,14 @@ agent-infra-internal task-event {task-id} analyze.started --agent {standard-agen
 
 ### 6. 输出分析文档
 
+在首次写入本轮 `{analysis-artifact}` 前，先创建受控报告骨架：
+
+```bash
+agent-infra-internal task-artifact {task-id} init --family analysis --artifact {analysis-artifact}
+```
+
+骨架只包含身份元数据、稳定 section marker 和必需标题；必须填入真实分析内容后才能通过完成门禁。finalizer 返回可证明的单个结构错误时，使用其 SHA 和 semantic digest 调用 `task-artifact {task-id} repair --family analysis --artifact {analysis-artifact} --expected-sha256 {artifact-sha256} --expected-semantic-digest {semantic-digest}`，然后完整重跑 finalizer。
+
 > 步骤 6–9 属**场景 A（正常产出）**路径。**场景 B（提问早退）**已在步骤 4 内完成状态更新、task 评论同步与校验并 STOP，不进入这些步骤。
 
 创建 `.agents/workspace/active/{task-id}/{analysis-artifact}`。
@@ -146,7 +159,7 @@ agent-infra-internal task-event {task-id} analyze.started --agent {standard-agen
 
 ## 状态核对
 
-> 粘贴第 0 步状态核对命令原文；每条命令以 `$ ` 开头。
+> 记录第 0 步状态核对命令、任务/产物范围、关键结果和未覆盖部分；每条命令以 `$ ` 开头。正常成功不粘贴完整目录清单或 `task.md` 尾部，失败、阻塞、身份不一致或争议时附决定性原文行。
 
 ## 需求来源
 
@@ -173,6 +186,10 @@ agent-infra-internal task-event {task-id} analyze.started --agent {standard-agen
 ## 依赖关系
 - {需要的依赖和与其他模块的协调}
 
+## 资格审计
+
+> 按 `.agents/rules/decision-qualification.md` 填写约束依赖、候选资格、分类结果、上游关系、依赖快照五张表；没有 artifact 上游时保留空表头，不虚构关系。
+
 ## 假设
 
 > 如本次分析依赖某些假设，列在此处；没有则可省略本段。

package/templates/.agents/skills/analyze-task/config/verify.en.json

@@ -18,18 +18,7 @@
     },
     "artifact": {
       "file_pattern": "analysis.md|analysis-r{N}.md",
-      "required_sections": [
-        "Requirement Source",
-        "Requirement Understanding",
-        "Related Files",
-        "Impact Assessment",
-        "Technical Risks",
-        "Effort and Complexity Assessment",
-        "State Check"
-      ],
-      "required_patterns": [
-        "^\\$ "
-      ]
+      "schema": "analysis"
     },
     "activity-log": {
       "expected_action_pattern": "(Analyze Task|Requirement Analysis) \\(Round \\d+\\)"

package/templates/.agents/skills/analyze-task/config/verify.zh-CN.json

@@ -18,18 +18,7 @@
     },
     "artifact": {
       "file_pattern": "analysis.md|analysis-r{N}.md",
-      "required_sections": [
-        "需求来源",
-        "需求理解",
-        "相关文件",
-        "影响评估",
-        "技术风险",
-        "工作量和复杂度评估",
-        "状态核对"
-      ],
-      "required_patterns": [
-        "^\\$ "
-      ]
+      "schema": "analysis"
     },
     "activity-log": {
       "expected_action_pattern": "(Analyze Task|Requirement Analysis) \\(Round \\d+\\)"

package/templates/.agents/skills/close-codescan/SKILL.en.md

@@ -23,7 +23,7 @@ The skill still owns the security-alert API. When a related task exists, Step 7
 
 ### 1. Retrieve Alert Information
 
-Read `.agents/rules/security-alerts.md` before this step, then run `bash .agents/scripts/security-alerts.sh read-codescan --number {alert-number}` and parse its JSON result to fetch the alert details.
+Read `.agents/rules/security-alerts.md` before this step, then run `agent-infra-internal platform-security read --kind code-scanning --number {alert-number}` and parse its JSON result to fetch the alert details.
 
 Verify that the alert is in the `open` state. If it is already dismissed or fixed, inform the user and exit.
 
@@ -71,7 +71,7 @@ Confirm? (y/N)
 
 ### 6. Execute the Dismissal
 
-Write the user's explanation to `{comment-file}`, then run `bash .agents/scripts/security-alerts.sh dismiss-codescan --number {alert-number} --reason {api-reason} --comment-file {comment-file}`. Parse the JSON result and continue only when the dismissal is `applied` or `no-op`.
+Write the user's explanation to `{comment-file}`, then run `agent-infra-internal platform-security dismiss --kind code-scanning --number {alert-number} --reason {api-reason} --comment-file {comment-file}`. Parse the JSON result and continue only when the dismissal is `applied` or `no-op`.
 
 **API reason mapping** (per the Code Scanning API):
 - False Positive -> `false positive`

package/templates/.agents/skills/close-codescan/SKILL.zh-CN.md

@@ -23,7 +23,7 @@ description: >
 
 ### 1. 获取告警信息
 
-执行前先读取 `.agents/rules/security-alerts.md`，然后运行 `bash .agents/scripts/security-alerts.sh read-codescan --number {alert-number}`，解析其 JSON 结果获取告警详情。
+执行前先读取 `.agents/rules/security-alerts.md`，然后运行 `agent-infra-internal platform-security read --kind code-scanning --number {alert-number}`，解析其 JSON 结果获取告警详情。
 
 验证告警处于 `open` 状态。如果已被关闭/修复，告知用户并退出。
 
@@ -71,7 +71,7 @@ Code Scanning 告警 #{alert-number}
 
 ### 6. 执行关闭
 
-将用户说明写入 `{comment-file}`，然后运行 `bash .agents/scripts/security-alerts.sh dismiss-codescan --number {alert-number} --reason {api-reason} --comment-file {comment-file}`。解析 JSON 结果，仅当关闭状态为 `applied` 或 `no-op` 时继续。
+将用户说明写入 `{comment-file}`，然后运行 `agent-infra-internal platform-security dismiss --kind code-scanning --number {alert-number} --reason {api-reason} --comment-file {comment-file}`。解析 JSON 结果，仅当关闭状态为 `applied` 或 `no-op` 时继续。
 
 **API reason 映射**（按 Code Scanning API）：
 - 误报 -> `false positive`