@fitlab-ai/agent-infra 0.8.2 → 0.8.3

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

@@ -0,0 +1,118 @@
+---
+name: complete-manual-validation
+description: >
+  Mark PR manual validation as completed and update the manual-validation section
+  in the existing PR summary comment in place.
+---
+
+# Complete Manual Validation
+
+## Boundary / Critical Rules
+
+- This skill closes the manual-validation status in an existing PR summary comment; it does not create a parallel ordinary validation comment.
+- It must write `manual-validation.md` or `manual-validation-r{N}.md` so later PR summary refreshes can reuse the validation result.
+- If the `sync-pr` summary comment is missing, fail instead of creating a partial fallback summary.
+- After this skill runs, update `task.md` immediately.
+
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
+## Step 0: State Check (pre-execution hard gate)
+
+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 both the user-facing reply and this round's `## State Check` section:
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+tail .agents/workspace/active/{task-id}/task.md
+```
+
+## Task id short ref
+
+> If `{task-id}` matches `^[#]?[0-9]+$` (bare numeric or `#`-prefixed), follow the "SKILL parameter resolver" section of `.agents/rules/task-short-id.md`; treat `{task-id}` as the resolved full `TASK-YYYYMMDD-HHMMSS` form for every downstream command.
+
+## Step Start: Write the started Marker
+
+After confirming prerequisites and the artifact round, and before this round's first artifact action, append a started marker to task.md `## Activity Log`:
+
+```
+- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Complete Manual Validation [started]** by {agent} — started
+```
+
+See the "Activity Log started / done dual-marker convention" in `.agents/rules/task-management.md`.
+
+## Steps
+
+### 1. Parse Arguments
+
+Input:
+
+```text
+complete-manual-validation {task-ref} [{pr-ref}] {verification-summary}
+```
+
+- `{task-ref}` is required.
+- `{pr-ref}` is optional and accepts `#NN`, `NN`, or a full PR URL.
+- `{verification-summary}` is required. If it is missing, stop and ask for a validation summary; do not write an artifact or update the PR.
+
+### 2. Verify Prerequisites
+
+Check:
+- `.agents/workspace/active/{task-id}/task.md`
+- a valid PR: prefer explicit `{pr-ref}`, otherwise read `pr_number` from task.md frontmatter
+
+Stop if the task is missing, the validation summary is missing, or no valid PR can be resolved.
+
+### 3. Determine Artifact Round
+
+Scan the task directory:
+- no `manual-validation.md` and no `manual-validation-r*.md` -> write `manual-validation.md`
+- `manual-validation.md` exists and no `manual-validation-r*.md` -> write `manual-validation-r2.md`
+- `manual-validation-r{N}.md` exists -> write `manual-validation-r{N+1}.md`
+
+### 4. Update the PR Summary
+
+Before this step, read:
+- `.agents/rules/issue-sync.md`
+- `.agents/rules/pr-sync.md`
+- `reference/summary-update.md`
+
+Follow `reference/summary-update.md` to resolve the PR number, find the `sync-pr` summary comment, extract the manual-validation scope, and update the section to `### ✅ Manual Validation Passed`.
+
+### 5. Create the Manual Validation Artifact
+
+Before this step, read `reference/report-template.md`. Create `{manual-validation-artifact}` with state check, validation verdict, validation scope, validation details, and PR summary sync result.
+
+### 6. Update task.md
+
+Get the current time:
+
+```bash
+date "+%Y-%m-%d %H:%M:%S%:z"
+```
+
+Update `.agents/workspace/active/{task-id}/task.md`:
+- `updated_at`: current time
+- `assigned_to`: current agent
+- `agent_infra_version`: value from `.agents/rules/version-stamp.md`
+- keep `current_step` unchanged
+- append the `{manual-validation-artifact}` link and PR summary sync result to `## Implementation Notes`
+- append Activity Log:
+  ```
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Complete Manual Validation** by {agent} — Manual validation passed → {manual-validation-artifact}; {summary-result}
+  ```
+
+If the task has a valid `issue_number`, follow `.agents/rules/issue-sync.md` to update the task comment and publish the `{manual-validation-artifact}` comment.
+
+### 7. Verification Gate
+
+Run:
+
+```bash
+node .agents/scripts/validate-artifact.js gate complete-manual-validation .agents/workspace/active/{task-id} {manual-validation-artifact} --format text
+```
+
+### 8. Tell the User
+
+Report the artifact path, PR summary sync result, and verification output. 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

@@ -0,0 +1,118 @@
+---
+name: complete-manual-validation
+description: >
+  标记 PR 人工验证已完成，并原地更新 PR 摘要评论中的人工校验段落。
+  当维护者已完成真实环境或权限相关人工验证、需要统一收尾 PR 摘要时使用。
+---
+
+# 完成人工验证
+
+## 行为边界 / 关键规则
+
+- 本技能用于收尾已有 PR 摘要评论中的人工校验状态，不创建并行的普通验证留言。
+- 必须写入 `manual-validation.md` 或 `manual-validation-r{N}.md`，让后续 PR 摘要刷新可复用人工验证结果。
+- 找不到 `sync-pr` 摘要评论时失败，不创建部分摘要兜底。
+- 执行本技能后必须立即更新 `task.md`。
+
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
+## 第 0 步：状态核对（执行前硬约束）
+
+在加载 workflow / skill / rules 指令之后、做任何任务状态判断或用户可见结论之前，必须先执行状态核对。指令类文件读取不算对外动作或结论。
+
+运行以下命令，并把原文粘贴到回复正文和本轮产物的 `## 状态核对` 段：
+
+```bash
+git status -s
+ls -la .agents/workspace/active/{task-id}/
+tail .agents/workspace/active/{task-id}/task.md
+```
+
+## 任务入参短号别名
+
+> 如果 `{task-id}` 入参匹配 `^[#]?[0-9]+$`（裸数字或带 `#` 前缀），先读取 `.agents/rules/task-short-id.md` 的「SKILL 入参解析」段执行解析；后续命令视 `{task-id}` 为解析后的全长 `TASK-YYYYMMDD-HHMMSS` 形式。
+
+## 步骤开始：写入 started 标记
+
+确认前置条件和产物轮次后、本轮第一个产出动作之前，向 task.md `## 活动日志` 追加一条 started 标记：
+
+```
+- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Complete Manual Validation [started]** by {agent} — started
+```
+
+格式与配对规则见 `.agents/rules/task-management.md` 的「Activity Log started / done 双标记约定」。
+
+## 执行步骤
+
+### 1. 解析入参
+
+输入格式：
+
+```text
+complete-manual-validation {task-ref} [{pr-ref}] {verification-summary}
+```
+
+- `{task-ref}` 必填。
+- `{pr-ref}` 可选，支持 `#NN`、`NN` 或完整 PR URL。
+- `{verification-summary}` 必填。若缺失，立即停止并提示补充验证说明；不写产物、不更新 PR。
+
+### 2. 验证前置条件
+
+检查：
+- `.agents/workspace/active/{task-id}/task.md`
+- 有效 PR：优先使用显式 `{pr-ref}`，否则读取 task.md frontmatter 的 `pr_number`
+
+如果任务不存在、验证说明缺失，或无法解析有效 PR，立即停止。
+
+### 3. 确定产物轮次
+
+扫描任务目录：
+- 不存在 `manual-validation.md` 且不存在 `manual-validation-r*.md` -> 本轮产物为 `manual-validation.md`
+- 已存在 `manual-validation.md` 且不存在 `manual-validation-r*.md` -> 本轮产物为 `manual-validation-r2.md`
+- 已存在 `manual-validation-r{N}.md` -> 本轮产物为 `manual-validation-r{N+1}.md`
+
+### 4. 更新 PR 摘要
+
+执行此步骤前，先读取：
+- `.agents/rules/issue-sync.md`
+- `.agents/rules/pr-sync.md`
+- `reference/summary-update.md`
+
+按 `reference/summary-update.md` 解析 PR 号、查找 `sync-pr` 摘要评论、提取待人工校验范围，并把人工校验段落更新为 `### ✅ 人工验证已通过`。
+
+### 5. 创建人工验证产物
+
+执行此步骤前，先读取 `reference/report-template.md`。创建 `{manual-validation-artifact}`，记录状态核对、验证结论、验证范围、验证详情和 PR 摘要同步结果。
+
+### 6. 更新 task.md
+
+获取当前时间：
+
+```bash
+date "+%Y-%m-%d %H:%M:%S%:z"
+```
+
+更新 `.agents/workspace/active/{task-id}/task.md`：
+- `updated_at`：{当前时间}
+- `assigned_to`：{当前代理}
+- `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
+- 保持 `current_step` 不变
+- 在 `## 实现备注` 中追加 `{manual-validation-artifact}` 链接和 PR 摘要同步结果
+- 追加 Activity Log：
+  ```
+  - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Complete Manual Validation** by {agent} — Manual validation passed → {manual-validation-artifact}; {summary-result}
+  ```
+
+如任务存在有效 `issue_number`，按 `.agents/rules/issue-sync.md` 更新 task 评论并发布 `{manual-validation-artifact}` 评论。
+
+### 7. 完成校验
+
+运行完成校验：
+
+```bash
+node .agents/scripts/validate-artifact.js gate complete-manual-validation .agents/workspace/active/{task-id} {manual-validation-artifact} --format text
+```
+
+### 8. 告知用户
+
+输出产物路径、PR 摘要同步结果和当次完成校验输出。渲染最终输出前，先读取 `.agents/rules/next-step-output.md`，并在绝对最后一行追加 `Completed at: YYYY-MM-DD HH:mm:ss`。

package/templates/.agents/skills/complete-manual-validation/config/verify.en.json

@@ -0,0 +1,49 @@
+{
+  "skill": "complete-manual-validation",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "agent_infra_version",
+        "current_step",
+        "assigned_to"
+      ]
+    },
+    "artifact": {
+      "file_pattern": "manual-validation.md|manual-validation-r{N}.md",
+      "required_sections": [
+        "State Check",
+        "Validation Verdict",
+        "Validation Scope",
+        "Validation Details",
+        "PR Summary Sync"
+      ],
+      "freshness_minutes": 30,
+      "required_patterns": [
+        "^\\$ "
+      ]
+    },
+    "activity-log": {
+      "expected_action_pattern": "Complete Manual Validation",
+      "freshness_minutes": 30
+    },
+    "review-ledger": {
+      "stage_scope": ["analysis", "plan", "code"]
+    },
+    "platform-sync": {
+      "when": "pr_number_exists",
+      "expected_pr_comment_marker_key": "prSummary",
+      "expected_pr_comment_required_patterns": [
+        "^### ✅ Manual Validation Passed$"
+      ],
+      "verify_task_comment_content": true,
+      "verify_issue_type": true,
+      "verify_issue_fields": false
+    }
+  }
+}

package/templates/.agents/skills/complete-manual-validation/config/verify.zh-CN.json

@@ -0,0 +1,49 @@
+{
+  "skill": "complete-manual-validation",
+  "checks": {
+    "task-meta": {
+      "required_fields": [
+        "id",
+        "type",
+        "workflow",
+        "status",
+        "created_at",
+        "updated_at",
+        "agent_infra_version",
+        "current_step",
+        "assigned_to"
+      ]
+    },
+    "artifact": {
+      "file_pattern": "manual-validation.md|manual-validation-r{N}.md",
+      "required_sections": [
+        "状态核对",
+        "验证结论",
+        "验证范围",
+        "验证详情",
+        "PR 摘要同步"
+      ],
+      "freshness_minutes": 30,
+      "required_patterns": [
+        "^\\$ "
+      ]
+    },
+    "activity-log": {
+      "expected_action_pattern": "Complete Manual Validation",
+      "freshness_minutes": 30
+    },
+    "review-ledger": {
+      "stage_scope": ["analysis", "plan", "code"]
+    },
+    "platform-sync": {
+      "when": "pr_number_exists",
+      "expected_pr_comment_marker_key": "prSummary",
+      "expected_pr_comment_required_patterns": [
+        "^### ✅ 人工验证已通过$"
+      ],
+      "verify_task_comment_content": true,
+      "verify_issue_type": true,
+      "verify_issue_fields": false
+    }
+  }
+}

package/templates/.agents/skills/complete-manual-validation/reference/report-template.en.md

@@ -0,0 +1,48 @@
+# Manual Validation Completion Report Template
+
+Read this file before creating `manual-validation.md` / `manual-validation-r{N}.md`.
+
+````markdown
+# Manual Validation Completion Report
+
+- **Validation Round**: Round {N}
+- **Artifact File**: `manual-validation.md`
+
+## State Check
+
+```text
+$ git status -s
+$ ls -la .agents/workspace/active/{task-id}/
+$ tail .agents/workspace/active/{task-id}/task.md
+```
+
+## Validation Verdict
+
+- Verdict: passed
+- Validation time: {YYYY-MM-DD HH:mm:ss±HH:MM}
+- Operator: {agent}
+
+## Validation Scope
+
+- PR: #{pr-number}
+- Summary comment: {comment-id or URL}
+- Manual-validation items:
+  - {item-1}
+
+## Validation Details
+
+{verification-summary}
+
+## PR Summary Sync
+
+- Result: {summary-result}
+- Summary comment: {comment-id or URL}
+- Updated status: `### ✅ Manual Validation Passed`
+````
+
+## Filling Rules
+
+- Keep `Validation Details` grounded in the user-provided validation notes.
+- Derive `Validation Scope` from the PR summary's manual-verification section.
+- `PR Summary Sync` must record success, skip, or failure.
+- Only write a passing artifact after the summary comment is updated or skipped because there is no diff.

package/templates/.agents/skills/complete-manual-validation/reference/report-template.zh-CN.md

@@ -0,0 +1,48 @@
+# 人工验证完成报告模板
+
+创建 `manual-validation.md` / `manual-validation-r{N}.md` 前先读取本文件。
+
+````markdown
+# 人工验证完成报告
+
+- **验证轮次**：Round {N}
+- **产物文件**：`manual-validation.md`
+
+## 状态核对
+
+```text
+$ git status -s
+$ ls -la .agents/workspace/active/{task-id}/
+$ tail .agents/workspace/active/{task-id}/task.md
+```
+
+## 验证结论
+
+- 结论：通过
+- 验证时间：{YYYY-MM-DD HH:mm:ss±HH:MM}
+- 执行者：{agent}
+
+## 验证范围
+
+- PR：#{pr-number}
+- 摘要评论：{comment-id 或 URL}
+- 待人工校验项：
+  - {item-1}
+
+## 验证详情
+
+{verification-summary}
+
+## PR 摘要同步
+
+- 结果：{summary-result}
+- 摘要评论：{comment-id 或 URL}
+- 更新状态：`### ✅ 人工验证已通过`
+````
+
+## 填写规则
+
+- `验证详情` 保留用户提供的人工验证说明，不改写成未经确认的结论。
+- `验证范围` 来自 PR 摘要评论中的 `### ⚠️ 需人工校验` 段。
+- `PR 摘要同步` 必须记录成功、跳过或失败结果。
+- 只有在摘要评论已成功更新或无 diff 跳过时，才写入通过产物。

package/templates/.agents/skills/complete-manual-validation/reference/summary-update.en.md

@@ -0,0 +1,60 @@
+# PR Summary Manual Validation Update
+
+Read this file before `complete-manual-validation` updates the PR summary comment.
+
+## Responsibility Boundary
+
+This file only describes PR summary comment updates. The manual-validation artifact schema lives in `reference/report-template.md`.
+
+## PR Number Resolution
+
+1. Resolve `{task-ref}` to the task directory and read `task.md`.
+2. Prefer `task.md` frontmatter `pr_number`.
+3. If `pr_number` is empty, parse `{pr-ref}` from user input: `#123`, `123`, or a full PR URL.
+4. If `task.md` already has `pr_number` and the user also passed `{pr-ref}`, they must match.
+5. If they differ, fail with `summary failed: pr_number mismatch`. Do not write an artifact or PATCH a comment.
+6. If both are missing, fail with `summary failed: missing pr_number`. Do not write an artifact or PATCH a comment.
+
+## Required Reads
+
+Before remote operations, read:
+- `.agents/rules/issue-sync.md` to resolve upstream repository and permissions.
+- `.agents/rules/pr-sync.md` to reuse the PR summary hidden marker, Issues comments API, and shell safety rules.
+
+## Comment Lookup
+
+Fetch ordinary PR comments with the current platform's Issues comments API. Follow the concrete command pattern in `.agents/rules/pr-sync.md`.
+
+Find the `<!-- sync-pr:{task-id}:summary -->` summary comment. If it is missing, fail with `summary failed: missing sync-pr summary`.
+
+On failure, do not create an ordinary validation comment, do not create a partial summary comment, and do not write a `manual-validation*` artifact.
+
+## Manual Validation Scope Extraction
+
+- If a `### ⚠️ Manual Verification Required` section exists, take that section until the next `### ` heading.
+- If the current summary already says `### ✅ Manual Validation Passed`, allow a new validation artifact round and update the details.
+- If the current summary says `### ✅ No Manual Verification Needed`, stop and report that this PR does not need manual validation; do not mark it as passed.
+
+## Three-Branch Rendering
+
+The updated `{manual-validation-section}` is:
+
+```markdown
+### ✅ Manual Validation Passed
+
+- Validation time: {time}
+- Validation notes: {verification-summary}
+```
+
+Later `pr-sync` aggregation renders in this priority order:
+1. latest `manual-validation.md` / `manual-validation-r{N}.md` has a passed verdict -> `### ✅ Manual Validation Passed`
+2. no passed artifact and retained manual-validation items exist -> `### ⚠️ Manual Verification Required`
+3. no passed artifact and no retained manual-validation items -> `### ✅ No Manual Verification Needed`
+
+## PATCH Rules
+
+Update existing comments with Issues comments PATCH and follow the heredoc safety rules in `.agents/rules/pr-sync.md`.
+
+## Result Reporting
+
+Return `summary updated`, `summary skipped (no diff)`, or `summary failed: <reason>`.

package/templates/.agents/skills/complete-manual-validation/reference/summary-update.zh-CN.md

@@ -0,0 +1,87 @@
+# PR 摘要人工验证更新
+
+在 `complete-manual-validation` 更新 PR 摘要评论前先读取本文件。
+
+## 职责边界
+
+本文件只描述 PR 摘要评论更新流程。人工验证产物结构见 `reference/report-template.md`。
+
+## PR 号解析
+
+1. 从 `{task-ref}` 定位任务目录并读取 `task.md`。
+2. 优先读取 `task.md` frontmatter 的 `pr_number`。
+3. 如果 `pr_number` 为空，再从用户输入的 `{pr-ref}` 解析：
+   - `#123`
+   - `123`
+   - `{platform-host}/{owner}/{repo}/pull/123`
+4. 如果 `task.md` 已有 `pr_number`，且用户也传入 `{pr-ref}`，两者必须一致。
+5. 两者不一致时失败：`summary failed: pr_number mismatch`。不写 artifact，不 PATCH 评论。
+6. 两者都缺失时失败：`summary failed: missing pr_number`。不写 artifact，不 PATCH 评论。
+
+## 前置读取
+
+执行远端操作前先读取：
+- `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测。
+- `.agents/rules/pr-sync.md`，复用 PR 摘要隐藏标记、Issues comments API 和 Shell 安全规则。
+
+## 评论查找
+
+使用当前平台的 Issues comments API 查询 PR 上的普通评论，具体命令遵循 `.agents/rules/pr-sync.md`。
+
+查找以以下标记开头或包含该标记的评论：
+
+```html
+<!-- sync-pr:{task-id}:summary -->
+```
+
+找不到时失败：
+
+```text
+summary failed: missing sync-pr summary
+```
+
+失败时不创建普通验证留言，不创建部分摘要评论，不写 `manual-validation*` artifact。
+
+## 待人工校验范围提取
+
+从当前摘要评论中提取人工校验范围：
+- 如果存在 `### ⚠️ 需人工校验` 段，取该段到下一个 `### ` heading 之前的内容。
+- 如果当前摘要已是 `### ✅ 人工验证已通过`，允许再次写入新一轮验证产物并更新详情。
+- 如果当前摘要是 `### ✅ 无需人工校验`，停止并提示当前 PR 无需人工校验；不误标为人工验证已通过。
+
+## 三分支渲染
+
+更新后的 `{manual-validation-section}` 为：
+
+```markdown
+### ✅ 人工验证已通过
+
+- 验证时间：{time}
+- 验证说明：{verification-summary}
+```
+
+后续 `pr-sync` 聚合时按以下优先级渲染：
+1. 最新 `manual-validation.md` / `manual-validation-r{N}.md` 结论为通过 -> `### ✅ 人工验证已通过`
+2. 没有通过产物且仍有保留人工校验项 -> `### ⚠️ 需人工校验`
+3. 没有通过产物且无保留人工校验项 -> `### ✅ 无需人工校验`
+
+## PATCH 规则
+
+更新已有评论时必须使用 Issues comments PATCH，具体命令遵循 `.agents/rules/pr-sync.md`。
+
+Shell 安全规则：
+- 先读取本地和远端正文，再构造完整正文。
+- heredoc 使用单引号 `<<'EOF'`。
+- 不在 heredoc 内执行变量展开或命令替换。
+- 构造含 `<!-- -->` 的正文时不用 `echo`。
+
+## 结果回传
+
+返回以下结果之一：
+- `summary updated`
+- `summary skipped (no diff)`
+- `summary failed: missing pr_number`
+- `summary failed: pr_number mismatch`
+- `summary failed: missing sync-pr summary`
+- `summary failed: no manual validation required`
+- `summary failed: <reason>`

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

@@ -165,3 +165,5 @@ Next step (alternative) - Skip monitoring and archive the task directly:
 - Push rejected: suggest `git pull --rebase`
 - Existing PR found: show the current PR URL and stop
 - Inaccessible Issue metadata: skip inheritance and continue
+- PR creation failed with an associated `{task-id}`: run `node .agents/scripts/workflow-warnings.js add .agents/workspace/active/{task-id} --step create-pr --severity ACTION_REQUIRED --code PR_CREATE_FAILED --target pr --message "{reason}" --action "Fix push, permission, or platform issues and rerun create-pr"` and do not write `pr_number`
+- PR summary comment failed with an associated `{task-id}`: record a `COMMENT_SYNC_FAILED` warning per `.agents/rules/pr-sync.md`, without rolling back an already-created PR

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

@@ -165,3 +165,5 @@ node .agents/scripts/validate-artifact.js gate create-pr .agents/workspace/activ
 - 推送被拒绝：建议执行 `git pull --rebase`
 - 已存在 PR：直接输出当前 PR URL 并结束
 - 无法访问 Issue 元数据：跳过继承并继续
+- PR 创建失败且已关联 `{task-id}`：调用 `node .agents/scripts/workflow-warnings.js add .agents/workspace/active/{task-id} --step create-pr --severity ACTION_REQUIRED --code PR_CREATE_FAILED --target pr --message "{reason}" --action "修复推送、权限或平台问题后重跑 create-pr"`，不写 `pr_number`
+- PR 摘要评论失败且已关联 `{task-id}`：按 `.agents/rules/pr-sync.md` 记录 `COMMENT_SYNC_FAILED` 告警，不回滚已创建 PR

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

@@ -135,7 +135,7 @@ The rule's content is determined by the configured code platform:
 
 Handle the result:
 - Rule successfully created the Issue: `issue_number` has been written back to task.md per the rule; continue by reading `.agents/rules/issue-sync.md`, completing upstream repository and permission detection, then sync the task comment and set `status: waiting-for-triage` by rule
-- Rule failed (auth / network / template parse / etc.): do not roll back task.md; do NOT append an extra Activity Log entry; follow "Scenario C: Issue creation failed" output to surface `error_code` and `error_message` to the user so they can decide whether to retry manually or write `issue_number` later
+- Rule failed (auth / network / template parse / etc.): do not roll back task.md; do NOT append an extra Activity Log entry; first run `node .agents/scripts/workflow-warnings.js add .agents/workspace/active/{task-id} --step create-task --severity ACTION_REQUIRED --code ISSUE_CREATE_FAILED --target issue --message "{error_code}: {error_message}" --action "Fix auth/network/template issues and manually retry Issue creation, or create/find an Issue and write issue_number"` to record a generic warning; then follow "Scenario C: Issue creation failed" output to surface `error_code` and `error_message`
 - Rule was a no-op (custom or empty platform): do not create comments, do not block the workflow, and do not write an Activity Log entry
 - task.md already has `issue_number`: the rule's prerequisite check skips creation; `create-task` proceeds directly to step 5
 
@@ -231,6 +231,9 @@ Next step - run requirements analysis:
   - Codex CLI: $analyze-task {task-ref}
 
 For later platform sync: after fixing auth / network / template issues, manually run the Issue creation flow in `.agents/rules/create-issue.md` for this task; or manually create/find an Issue and write `issue_number` into task.md so later skills can take over cascade sync.
+
+[ACTION REQUIRED] Workflow warnings are open:
+  - WW-N ISSUE_CREATE_FAILED (issue): Fix auth/network/template issues and manually retry Issue creation, or create/find an Issue and write issue_number
 ```
 
 

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

@@ -134,7 +134,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 处理结果：
 - 规则成功创建 Issue：`issue_number` 已按规则回写到 task.md；继续读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测，然后同步 task 评论并按规则设置 `status: waiting-for-triage`
-- 规则失败（认证 / 网络 / 模板解析等）：不回滚 task.md；不追加额外 Activity Log；按"场景 C：Issue 创建失败"输出向用户透出 `error_code` 与 `error_message`，让用户决定后续是否手动重试或写入 `issue_number`
+- 规则失败（认证 / 网络 / 模板解析等）：不回滚 task.md；不追加额外 Activity Log；先调用 `node .agents/scripts/workflow-warnings.js add .agents/workspace/active/{task-id} --step create-task --severity ACTION_REQUIRED --code ISSUE_CREATE_FAILED --target issue --message "{error_code}: {error_message}" --action "修复认证/网络/模板问题后手动重试 Issue 创建，或手动创建/找到 Issue 后写入 issue_number"` 记录通用告警；再按"场景 C：Issue 创建失败"输出向用户透出 `error_code` 与 `error_message`
 - 规则为 no-op（自定义或空平台）：不创建评论，不阻塞后续工作流，不写 Activity Log
 - task.md 已存在 `issue_number`：规则中的前置检查会跳过；`create-task` 直接进入步骤 5
 
@@ -230,6 +230,9 @@ Issue 创建失败：
   - Codex CLI：$analyze-task {task-ref}
 
 后续如需平台同步：修复认证/网络/模板问题后，可按 `.agents/rules/create-issue.md` 对当前任务手动执行一次 Issue 创建；或手动创建/查找 Issue，并把 `issue_number` 写入 task.md，后续技能会接管级联同步。
+
+[ACTION REQUIRED] Workflow warnings are open:
+  - WW-N ISSUE_CREATE_FAILED (issue): 修复认证/网络/模板问题后手动重试 Issue 创建，或手动创建/找到 Issue 后写入 issue_number
 ```
 
 

package/templates/.agents/skills/update-agent-infra/scripts/sync-templates.js

@@ -35,6 +35,7 @@ const DEFAULTS = {
       "gemini-cli",
       "opencode"
     ],
+    "refreshIntervalDays": 7,
     "dockerfile": null,
     "vm": {
       "cpu": null,
@@ -260,6 +261,12 @@ function listTemplateSkillNames(templateRoot) {
   return new Set(
     fs.readdirSync(templateSkillsDir, { withFileTypes: true })
       .filter((entry) => entry.isDirectory())
+      .filter((entry) => {
+        const skillDir = path.join(templateSkillsDir, entry.name);
+        return ['SKILL.md', 'SKILL.en.md', 'SKILL.zh-CN.md'].some((file) =>
+          fs.existsSync(path.join(skillDir, file))
+        );
+      })
       .map((entry) => entry.name)
   );
 }

package/templates/.agents/templates/task.en.md

@@ -64,6 +64,13 @@ pr_status: pending             # PR status: pending (default) | created (PR crea
 
 <!-- Humans record rulings for needs-human-decision decisions here and flip matching HD- rows in the Review Disagreement Ledger to human-decided. -->
 
+## Workflow Warnings
+
+<!-- Workflow degradation, platform sync failures, permission gaps, and related events. Keep the header when empty. -->
+
+| id | time | step | severity | code | status | target | message | action | resolved_at | resolution |
+|----|------|------|----------|------|--------|--------|---------|--------|-------------|------------|
+
 ## Activity Log
 
 <!-- Append a new entry for each workflow step. Do NOT overwrite previous entries. -->