@fitlab-ai/agent-infra 0.11.5 → 0.11.7

package/templates/.agents/skills/archive-tasks/scripts/archive-tasks.sh

@@ -8,9 +8,14 @@ WORKSPACE_ROOT="$REPO_ROOT/.agents/workspace"
 COMPLETED_DIR="$WORKSPACE_ROOT/completed"
 ARCHIVE_DIR="$WORKSPACE_ROOT/archive"
 MANIFEST_PATH="$ARCHIVE_DIR/manifest.md"
+tmpdir=""
+cleanup() {
+  [ -z "$tmpdir" ] || rm -rf "$tmpdir"
+}
+trap 'cleanup' 0
+trap 'cleanup; exit 1' HUP INT TERM
 
-tmpdir="$(mktemp -d)"
-trap 'rm -rf "$tmpdir"' EXIT HUP INT TERM
+tmpdir="$(mktemp -d "$WORKSPACE_ROOT/.archive-tmp.XXXXXX")"
 
 IDS_FILE="$tmpdir/task-ids.txt"
 : > "$IDS_FILE"
@@ -160,6 +165,17 @@ archive_task_dir() {
     return 0
   fi
 
+  find "$task_dir" -name manifest.md -print > "$tmpdir/task-manifests.txt"
+  if [ -s "$tmpdir/task-manifests.txt" ]; then
+    echo "TASK content cannot contain manifest.md: $task_id" >&2
+    return 1
+  fi
+  find "$task_dir" ! -type f ! -type d -print > "$tmpdir/task-special-files.txt"
+  if [ -s "$tmpdir/task-special-files.txt" ]; then
+    echo "TASK content cannot contain symbolic links or special files: $task_id" >&2
+    return 1
+  fi
+
   completed_at=$(extract_completed_at "$task_file")
   task_date=$(printf '%s' "$completed_at" | cut -c1-10)
 
@@ -179,12 +195,89 @@ archive_task_dir() {
     return 0
   fi
 
-  mkdir -p "$ARCHIVE_DIR/$year/$month/$day"
-  mv "$task_dir" "$destination_dir"
+  mkdir -p "$(dirname "$destination_dir")"
+  staged_dir="$tmpdir/$task_id"
+  mkdir -p "$staged_dir/local"
+  cp -R "$task_dir"/. "$staged_dir/local/"
+  write_contents_hash "$staged_dir/local"
+  mv "$staged_dir" "$destination_dir"
+  if ! rm -rf "$task_dir"; then
+    if ! rm -rf "$destination_dir"; then
+      echo "Failed to remove completed task and roll back archive copy: $task_id" >&2
+    else
+      echo "Failed to remove completed task; rolled back archive copy: $task_id" >&2
+    fi
+    return 1
+  fi
   archived_count=$((archived_count + 1))
   printf 'Archived %s -> %s\n' "$task_id" "$relative_path"
 }
 
+write_contents_hash() {
+  local_dir="$1"
+  hash_path=${2:-$local_dir/contents.sha256}
+  hash_tmp="$tmpdir/contents.sha256"
+  newline='
+'
+  : > "$hash_tmp"
+  find "$local_dir" -type f ! -name contents.sha256 | LC_ALL=C sort | while IFS= read -r source_file; do
+    relative_file=${source_file#"$local_dir"/}
+    case "$relative_file" in *"$newline"*|*"$(printf '\r')"*) echo "Newline path is not supported" >&2; return 1 ;; esac
+    if command -v sha256sum >/dev/null 2>&1; then
+      digest=$(sha256sum "$source_file" | awk '{print $1}')
+    else
+      digest=$(shasum -a 256 "$source_file" | awk '{print $1}')
+    fi
+    printf '%s  %s\n' "$digest" "$relative_file" >> "$hash_tmp"
+  done
+  mv "$hash_tmp" "$hash_path"
+  if [ "$hash_path" = "$local_dir/contents.sha256" ] && command -v sha256sum >/dev/null 2>&1; then
+    (cd "$local_dir" && sha256sum -c contents.sha256 >/dev/null)
+  elif [ "$hash_path" = "$local_dir/contents.sha256" ]; then
+    (cd "$local_dir" && shasum -a 256 -c contents.sha256 >/dev/null)
+  fi
+}
+
+validate_source_hash() {
+  source_dir="$1"
+  [ -f "$source_dir/task.md" ] || { echo "Archive source lacks task.md: $source_dir" >&2; return 1; }
+  [ -f "$source_dir/contents.sha256" ] || { echo "Archive source lacks contents.sha256: $source_dir" >&2; return 1; }
+  write_contents_hash "$source_dir" "$tmpdir/contents.expected"
+  if ! cmp -s "$tmpdir/contents.expected" "$source_dir/contents.sha256"; then
+    echo "Archive source checksum mismatch: $source_dir" >&2
+    return 1
+  fi
+}
+
+validate_existing_archive() {
+  [ -d "$ARCHIVE_DIR" ] || return 0
+  for year_dir in "$ARCHIVE_DIR"/[0-9][0-9][0-9][0-9]; do
+    [ -d "$year_dir" ] || continue
+    for month_dir in "$year_dir"/[0-9][0-9]; do
+      [ -d "$month_dir" ] || continue
+      for day_dir in "$month_dir"/[0-9][0-9]; do
+        [ -d "$day_dir" ] || continue
+        for task_dir in "$day_dir"/TASK-*; do
+          [ -d "$task_dir" ] || continue
+          [ -d "$task_dir/local" ] || { echo "Unsupported legacy archive task layout: $task_dir" >&2; return 1; }
+          for task_entry in "$task_dir"/*; do
+            [ -e "$task_entry" ] || continue
+            case "$(basename "$task_entry")" in
+              local|github|derived) [ -d "$task_entry" ] || { echo "Invalid archive source directory: $task_entry" >&2; return 1; } ;;
+              *) echo "Unexpected TASK root entry: $task_entry" >&2; return 1 ;;
+            esac
+          done
+          find "$task_dir/local" -name manifest.md -print > "$tmpdir/task-manifests.txt"
+          [ ! -s "$tmpdir/task-manifests.txt" ] || { echo "TASK content cannot contain manifest.md: $task_dir" >&2; return 1; }
+          find "$task_dir/local" ! -type f ! -type d -print > "$tmpdir/task-special-files.txt"
+          [ ! -s "$tmpdir/task-special-files.txt" ] || { echo "TASK content cannot contain symbolic links or special files: $task_dir" >&2; return 1; }
+          validate_source_hash "$task_dir/local"
+        done
+      done
+    done
+  done
+}
+
 should_archive_filtered_task() {
   task_dir="$1"
   task_file="$task_dir/task.md"
@@ -231,7 +324,7 @@ rebuild_manifest() {
           [ -d "$task_dir" ] || continue
 
           task_id=$(basename "$task_dir")
-          task_file="$task_dir/task.md"
+          task_file="$task_dir/local/task.md"
           relative_path="$year/$month/$day/$task_id/"
           title="$task_id"
           task_type="unknown"
@@ -261,7 +354,15 @@ rebuild_manifest() {
     done
   done
 
-  find "$ARCHIVE_DIR" -type f -name 'manifest.md' -exec rm -f {} \;
+  rm -f "$ARCHIVE_DIR/manifest.md"
+  for year_dir in "$ARCHIVE_DIR"/[0-9][0-9][0-9][0-9]; do
+    [ -d "$year_dir" ] || continue
+    rm -f "$year_dir/manifest.md"
+    for month_dir in "$year_dir"/[0-9][0-9]; do
+      [ -d "$month_dir" ] || continue
+      rm -f "$month_dir/manifest.md"
+    done
+  done
 
   awk -F'\t' '{print $1 "\t" $2}' "$entries_file" | LC_ALL=C sort -u > "$month_keys_file"
   awk -F'\t' '{print $1}' "$entries_file" | LC_ALL=C sort -u > "$year_keys_file"
@@ -436,6 +537,8 @@ if [ -s "$IDS_FILE" ]; then
   MODE="ids"
 fi
 
+validate_existing_archive
+
 archived_count=0
 skipped_count=0
 

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

package/templates/.agents/skills/create-pr/SKILL.zh-CN.md

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

package/templates/.agents/skills/create-release-note/SKILL.en.md

@@ -53,6 +53,7 @@ agent-infra-internal platform-release-notes context \
 
 **Purpose**:
 - Part A: Analyze the section structure, heading style, emoji usage, and item format from the latest 3 historical release notes
+- Each `history` item contains a tag, body, and Release URL; use the body as a format sample, not as current change facts
 - Part B: Provide a static complete category list so no existing category is omitted
 - This static list ensures existing category names are not missed during classification; if the current release has no entries for a category, Step 7 still omits the empty section
 - When generating release notes in Step 7, **must** follow both the historical format style and the full category list gathered in Step 3
@@ -60,7 +61,7 @@ agent-infra-internal platform-release-notes context \
 
 ### 4. Collect Merged PRs and Contributors
 
-Use `pullRequests` and `commits` from Step 3. Each commit's `authors` are normalized platform facts containing the git author and co-authors; the skill does not interpret raw platform fields or email rules.
+Use `pullRequests` and `commits` from Step 3. Each commit's `authors` contains only that commit's platform authors; `pullRequestNumbers` records the platform's PR associations. The skill does not interpret raw platform fields or email rules. A PR's `closingIssues` contains its actual closing Issues; never infer a relationship from matching PR and Issue numbers.
 
 ### 5. Collect Related Issues
 
@@ -79,31 +80,36 @@ Use each PR's `closingIssues` from Step 3. Do not parse platform-specific refere
 
 ### 7. Generate Release Notes
 
-**Prioritize the historical format style obtained in Step 3 and ensure all categories listed in Step 3 are covered.** If historical release notes exist, strictly follow their section structure, heading style (including emojis), item format, and bilingual layout.
+**Prioritize the historical format style obtained in Step 3 and ensure all categories listed in Step 3 are covered.** Dynamically use the latest 3 published notes each time. Treat sections, bilingual layout, and installation instructions shared by those notes as stable format; allow item content to vary by release. Never copy an example's authors or links into the current release.
 
 If no historical release notes exist, use the following default Markdown format:
 
 ```markdown
-## {Module/Platform Name}
+## {Module / 模块}
 
-### Enhancement
+### Enhancement / 增强
 
 - [{scope}] Description by @author in [#N](url)
 
-### Bugfix
+### Bugfix / 修复
 
 - [{scope}] Description by @author in [#N](url)
 
-## Contributors
+## Contributors / 贡献者
 
 @contributor1, @contributor2, @contributor3, @reporter1 (reported #N)
+
+## Installation / 安装
+
+{English and Chinese installation instructions for this release, following stable steps in historical notes}
 ```
 
 **Format rules**:
-1. Item format: `- [scope] Description by @author in [#N](url)`
-2. Issue + PR: `in [#Issue](url) and [#PR](url)`
-3. Description: Use PR title, remove `type(scope):` prefix, capitalize first letter
-4. **Contributor collection**:
+1. PR item format: `- [scope] Description by @author in [#N](url)`
+2. Issue + PR: `in [#Issue](url) and [#PR](url)`; Issue reporters come from that PR's `closingIssues`
+3. Render each commit with an empty `pullRequestNumbers` as a standalone item using its subject and resolvable author; link to the commit itself when its URL is available, without adding an Issue or PR link
+4. Description: Use the PR title or commit subject; remove `type(scope):` from PR titles and capitalize the first letter
+5. **Contributor collection**:
    - **Data sources**:
      - PR authors from the typed context
      - Commit co-authors from the typed context's commit `authors`
@@ -123,7 +129,7 @@ If no historical release notes exist, use the following default Markdown format:
      - Reporter-only contributors use the format `@login (reported #N)`; if the same reporter reported multiple Issues, use `@login (reported #N1, #N2)`
      - Reporters are appended after code contributors in the Contributors section, separated by commas
      - Sort reporters by reported Issue count descending, then lexicographically by login for ties
-5. Empty sections: Omit sections with no entries
+6. Empty sections: Omit categories with no entries; retain bilingual headings and the installation section from the historical format
 
 ### 8. Stage, Present, and Confirm
 

package/templates/.agents/skills/create-release-note/SKILL.zh-CN.md

@@ -53,6 +53,7 @@ agent-infra-internal platform-release-notes context \
 
 **用途**：
 - Part A：分析最近 3 条历史发布说明的章节结构、标题风格、emoji 使用、条目格式
+- 每项 `history` 含 tag、正文和 Release URL；正文只作为格式样例，不作为当前版本的变更事实
 - Part B：提供静态完整分类清单，确保后续生成时不遗漏已有分类
 - 该静态清单用于确保变更分类时不遗漏已有类别名称；若当前版本无该类变更，仍按步骤 7 的格式规则省略空分类
 - 后续步骤 7 生成发布说明时，**必须**同时参考步骤 3 的历史格式风格和完整分类清单，保持版本间的一致性
@@ -60,7 +61,7 @@ agent-infra-internal platform-release-notes context \
 
 ### 4. 收集已合并的 PR 与贡献者
 
-使用步骤 3 返回的 `pullRequests` 与 `commits`。每个 commit 的 `authors` 已按平台事实规范化并包含 git author 与 co-author；技能不读取平台原始字段或邮箱规则。
+使用步骤 3 返回的 `pullRequests` 与 `commits`。每个 commit 的 `authors` 只包含该 commit 的平台作者；`pullRequestNumbers` 表示平台记录的 PR 关联。技能不读取平台原始字段或邮箱规则。PR 的 `closingIssues` 是该 PR 实际关闭的 Issue，不按 PR/Issue 编号推断关联。
 
 ### 5. 收集关联 Issue
 
@@ -79,31 +80,36 @@ agent-infra-internal platform-release-notes context \
 
 ### 7. 生成发布说明
 
-**优先使用步骤 3 中获取的历史格式风格，并确保覆盖步骤 3 列出的所有分类。** 如果存在历史发布说明，严格沿用其章节结构、标题风格（含 emoji）、条目格式和双语布局。
+**优先使用步骤 3 中获取的历史格式风格，并确保覆盖步骤 3 列出的所有分类。** 每次动态参考最近 3 条已发布说明；把这些正文共同使用的章节、双语布局和安装段作为稳定格式，条目内容按当前版本变化。不要把样例中的作者或链接复制到当前版本。
 
 如果没有历史发布说明，使用以下默认格式化为 Markdown：
 
 ```markdown
-## {模块/平台名称}
+## {Module / 模块}
 
-### Enhancement
+### Enhancement / 增强
 
 - [{scope}] Description by @author in [#N](url)
 
-### Bugfix
+### Bugfix / 修复
 
 - [{scope}] Description by @author in [#N](url)
 
-## Contributors
+## Contributors / 贡献者
 
 @contributor1, @contributor2, @contributor3, @reporter1 (reported #N)
+
+## Installation / 安装
+
+{本版本的中英文安装说明，沿用历史正文中的稳定安装步骤}
 ```
 
 **格式规则**：
-1. 条目格式：`- [scope] Description by @author in [#N](url)`
-2. Issue + PR：`in [#Issue](url) and [#PR](url)`
-3. 描述：使用 PR 标题，移除 `type(scope):` 前缀，首字母大写
-4. **贡献者搜集**：
+1. PR 条目格式：`- [scope] Description by @author in [#N](url)`
+2. Issue + PR：`in [#Issue](url) and [#PR](url)`；Issue reporter 来自该 PR 的 `closingIssues`
+3. `pullRequestNumbers` 为空的 commit 单独作为条目，使用 commit subject 和可解析作者；有 commit URL 时链接 commit 本身，不添加 Issue/PR 链接
+4. 描述：使用 PR 标题或 commit subject；移除 PR 标题中的 `type(scope):` 前缀，首字母大写
+5. **贡献者搜集**：
    - **数据源**：
      - PR author：来自 `.agents/rules/release-commands.md` 中已合并 PR 查询规则
      - Commit co-authors：来自步骤 3 typed context 的 commit `authors`
@@ -123,7 +129,7 @@ agent-infra-internal platform-release-notes context \
      - 仅报告贡献的用户以 `@login (reported #N)` 格式展示；同一 reporter 报告多个 Issue 时使用 `@login (reported #N1, #N2)`
      - Reporter 在 Contributors 段落中排在代码贡献者之后，以逗号分隔追加
      - Reporter 之间按报告的 Issue 数量降序排列，数量相同时按 login 字典序
-5. 空部分：省略没有条目的部分
+6. 空部分：省略没有条目的分类；保留历史格式中的双语章节与安装段
 
 ### 8. Stage、展示并确认
 

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

@@ -153,6 +153,8 @@ The host `task-create` service runs the same typed gate before returning. Consum
 agent-infra-internal task-verify {task-id} create-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/create-task/SKILL.zh-CN.md

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

package/templates/.agents/skills/import-codescan/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} import-codescan.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/import-codescan/SKILL.zh-CN.md

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

package/templates/.agents/skills/import-dependabot/SKILL.en.md

@@ -89,6 +89,8 @@ Run the verification gate to confirm the task artifact and sync state are valid:
 agent-infra-internal task-verify {task-id} import-dependabot.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/import-dependabot/SKILL.zh-CN.md

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

package/templates/.agents/skills/import-issue/SKILL.en.md

@@ -167,6 +167,8 @@ Run the verification gate to confirm the task artifact and sync state are valid:
 agent-infra-internal task-verify {task-id} import-issue.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/import-issue/SKILL.zh-CN.md

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

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

@@ -21,7 +21,7 @@ This stage consumes only the canonical path fact parsed by core from the latest
 
 Before generating the plan 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 verification; 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 plan 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 plan artifact; unknown or unconfirmed constraints must not automatically exclude a candidate
 - This skill only outputs a technical plan document (`plan.md` or `plan-r{N}.md`) and does not modify any business code
 - The full path proceeds to plan review; the standard path may proceed directly to implementation
 - 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
@@ -159,6 +159,8 @@ Run the verification gate to confirm the task artifact and sync state are valid:
 agent-infra-internal task-verify {task-id} plan.completed --artifact {plan-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