@fitlab-ai/agent-infra 0.6.0 → 0.6.2-alpha.1

package/templates/.agents/scripts/platform-adapters/platform-sync.github.js

@@ -5,6 +5,18 @@ import spawn from "cross-spawn";
 
 const CHECK_TYPE = "platform-sync";
 const DEFAULT_RETRY_DELAYS_MS = [3000, 10000];
+const FRONTMATTER_FIELD_MAP = {
+  priority: "Priority",
+  effort: "Effort",
+  start_date: "Start date",
+  target_date: "Target date"
+};
+const OPTION_LOCALIZATION = {
+  "紧急": "Urgent",
+  "高": "High",
+  "中": "Medium",
+  "低": "Low"
+};
 
 let activeShared = null;
 let repoRoot = "";
@@ -107,6 +119,7 @@ export function check({ taskDir, config, artifactFile }, shared) {
     checkPrAssignee,
     checkSyncedRequirements,
     checkIssueType,
+    checkIssueFields,
     checkMilestone
   ];
 
@@ -326,6 +339,27 @@ function fetchRemoteData(context) {
     }
   }
 
+  let issueFields;
+  if (context.config.verify_issue_fields && context.hasPush) {
+    const [owner, name] = context.upstreamRepo.split("/");
+    const issueFieldsResult = withRetry(() => ghJson([
+      "api",
+      "graphql",
+      "-f",
+      `query=${ISSUE_FIELDS_QUERY}`,
+      "-F",
+      `owner=${owner}`,
+      "-F",
+      `name=${name}`,
+      "-F",
+      `number=${context.issueNumber}`
+    ], context.taskDir));
+
+    if (issueFieldsResult.ok) {
+      issueFields = normalizeIssueFields(issueFieldsResult.value);
+    }
+  }
+
   let prLabels = null;
   let prMilestone;
   let prAssignees;
@@ -377,6 +411,7 @@ function fetchRemoteData(context) {
     prComments,
     prLabels,
     issueType,
+    issueFields,
     prMilestone,
     prAssignees
   };
@@ -703,6 +738,45 @@ function checkIssueType(context, remoteData) {
   return null;
 }
 
+function checkIssueFields(context, remoteData) {
+  if (!context.config.verify_issue_fields || !context.hasPush) {
+    return null;
+  }
+
+  if (remoteData.issueFields === undefined) {
+    return null;
+  }
+
+  for (const [metadataKey, fieldName] of Object.entries(FRONTMATTER_FIELD_MAP)) {
+    const expectedRaw = context.task.metadata[metadataKey];
+    if (isBlank(expectedRaw) || !remoteData.issueFields.pinnedNames.has(fieldName)) {
+      continue;
+    }
+
+    const actual = remoteData.issueFields.values.get(fieldName);
+    const expected = normalizeExpectedIssueField(metadataKey, expectedRaw);
+    if (!expected) {
+      continue;
+    }
+
+    if (!actual) {
+      return failResult(CHECK_TYPE,
+        `Issue #${context.issueNumber} field '${fieldName}' is missing, expected '${expected.value}'`,
+        "check_failed"
+      );
+    }
+
+    if (actual.kind !== expected.kind || actual.value !== expected.value) {
+      return failResult(CHECK_TYPE,
+        `Issue #${context.issueNumber} field '${fieldName}' is '${actual.value}', expected '${expected.value}'`,
+        "check_failed"
+      );
+    }
+  }
+
+  return null;
+}
+
 function checkPrAssignee(context, remoteData) {
   if (!context.config.verify_pr_assignee || !context.hasPush || !context.prNumber) {
     return null;
@@ -886,6 +960,69 @@ function mapTaskTypeToIssueType(taskType) {
   return mapping[taskType] || "Task";
 }
 
+const ISSUE_FIELDS_QUERY = `query($owner:String!,$name:String!,$number:Int!){repository(owner:$owner,name:$name){issue(number:$number){issueType{name pinnedFields{__typename ... on IssueFieldSingleSelect{id name} ... on IssueFieldDate{id name} ... on IssueFieldText{id name} ... on IssueFieldNumber{id name}}} issueFieldValues(first:50){nodes{__typename ... on IssueFieldSingleSelectValue{name optionId field{... on IssueFieldSingleSelect{name}}} ... on IssueFieldDateValue{value field{... on IssueFieldDate{name}}} ... on IssueFieldTextValue{value field{... on IssueFieldText{name}}} ... on IssueFieldNumberValue{value field{... on IssueFieldNumber{name}}}}}}}}`;
+
+function normalizeIssueFields(payload) {
+  const issue = payload?.data?.repository?.issue;
+  const pinnedFields = Array.isArray(issue?.issueType?.pinnedFields)
+    ? issue.issueType.pinnedFields
+    : [];
+  const values = Array.isArray(issue?.issueFieldValues?.nodes)
+    ? issue.issueFieldValues.nodes
+    : [];
+  const pinnedNames = new Set(
+    pinnedFields
+      .map((field) => typeof field?.name === "string" ? field.name : "")
+      .filter(Boolean)
+  );
+  const normalizedValues = new Map();
+
+  for (const value of values) {
+    const fieldName = value?.field?.name;
+    if (!fieldName) {
+      continue;
+    }
+
+    if (value.__typename === "IssueFieldSingleSelectValue") {
+      normalizedValues.set(fieldName, {
+        kind: "single-select",
+        value: normalizeOptionName(value.name)
+      });
+    } else if (value.__typename === "IssueFieldDateValue") {
+      normalizedValues.set(fieldName, {
+        kind: "date",
+        value: normalizeDateValue(value.value)
+      });
+    }
+  }
+
+  return { pinnedNames, values: normalizedValues };
+}
+
+function normalizeExpectedIssueField(metadataKey, rawValue) {
+  const value = String(rawValue || "").trim();
+  if (!value) {
+    return null;
+  }
+
+  if (metadataKey === "start_date" || metadataKey === "target_date") {
+    return { kind: "date", value: normalizeDateValue(value) };
+  }
+
+  return { kind: "single-select", value: normalizeOptionName(value) };
+}
+
+function normalizeOptionName(value) {
+  const normalized = String(value || "").trim();
+  return OPTION_LOCALIZATION[normalized] || normalized;
+}
+
+function normalizeDateValue(value) {
+  const normalized = String(value || "").trim();
+  const match = normalized.match(/^\d{4}-\d{2}-\d{2}/);
+  return match ? match[0] : normalized;
+}
+
 function arraysEqual(left, right) {
   if (left.length !== right.length) {
     return false;
@@ -928,14 +1065,14 @@ function computeExpectedInLabels(taskDir) {
     return { ok: true, labels: Array.from(labels).sort(), mode: "mapped" };
   }
 
-  const repoLabelsResult = ghJson([
+  const repoLabelsResult = withRetry(() => ghJson([
     "label",
     "list",
     "--limit",
     "200",
     "--json",
     "name"
-  ], taskDir);
+  ], taskDir));
   if (!repoLabelsResult.ok) {
     return repoLabelsResult;
   }
@@ -1015,10 +1152,10 @@ function resolveUpstreamRepo(taskDir) {
     return ownerRepo;
   }
 
-  const repoResult = ghJson([
+  const repoResult = withRetry(() => ghJson([
     "api",
     `repos/${ownerRepo.value}`
-  ], taskDir);
+  ], taskDir));
 
   if (!repoResult.ok) {
     return repoResult;
@@ -1053,12 +1190,12 @@ function resolveOwnerRepo(taskDir) {
 }
 
 function detectPermissions(upstreamRepo, taskDir) {
-  const permissionsResult = ghJson([
+  const permissionsResult = withRetry(() => ghJson([
     "api",
     `repos/${upstreamRepo}`,
     "--jq",
     ".permissions"
-  ], taskDir);
+  ], taskDir));
 
   if (!permissionsResult.ok) {
     return { hasTriage: false, hasPush: false };

package/templates/.agents/scripts/validate-artifact.js

@@ -22,12 +22,14 @@ const DEFAULT_REQUIRED_FIELDS = [
   "status",
   "created_at",
   "updated_at",
+  "agent_infra_version",
   "current_step",
   "assigned_to"
 ];
 
 const DEFAULT_FRESHNESS_MINUTES = 30;
 const DATE_TIME_PATTERN = /^\d{4}-\d{2}-\d{2}[T ]\d{2}:\d{2}:\d{2}(?:[+-]\d{2}:\d{2})?$/;
+const AGENT_INFRA_VERSION_PATTERN = /^v\d+\.\d+\.\d+(?:-[0-9A-Za-z.-]+)?(?:\+[0-9A-Za-z.-]+)?$/;
 const ACTIVITY_LOG_PATTERN = /^- (\d{4}-\d{2}-\d{2}[T ]\d{2}:\d{2}:\d{2}(?:[+-]\d{2}:\d{2})?) — \*\*(.+?)\*\* by (.+?) — (.+)$/;
 const BRANCH_SLUG_PATTERN = /^[a-z0-9]+(?:-[a-z0-9]+)*$/;
 
@@ -212,8 +214,24 @@ function checkTaskMeta({ taskDir, config }) {
   const metadata = task.metadata;
   const requiredFields = config.required_fields || DEFAULT_REQUIRED_FIELDS;
   const missingFields = requiredFields.filter((field) => isBlank(metadata[field]));
-  if (missingFields.length > 0) {
-    return failResult("task-meta", `Missing required fields: ${missingFields.join(", ")}`);
+  const blockingMissingFields = missingFields.filter((field) => field !== "agent_infra_version");
+  const warnings = [];
+  if (missingFields.includes("agent_infra_version")) {
+    warnings.push("field 'agent_infra_version' missing — historical task or skipped version stamp");
+  }
+  if (blockingMissingFields.length > 0) {
+    return failResult("task-meta", `Missing required fields: ${blockingMissingFields.join(", ")}`);
+  }
+
+  if (
+    !isBlank(metadata.agent_infra_version) &&
+    metadata.agent_infra_version !== "unknown" &&
+    !AGENT_INFRA_VERSION_PATTERN.test(metadata.agent_infra_version)
+  ) {
+    return failResult(
+      "task-meta",
+      `Invalid agent_infra_version: ${metadata.agent_infra_version}`
+    );
   }
 
   const invalidDates = ["created_at", "updated_at", "completed_at", "blocked_at", "cancelled_at"]
@@ -272,7 +290,12 @@ function checkTaskMeta({ taskDir, config }) {
     }
   }
 
-  return passResult("task-meta", `Task metadata valid (${requiredFields.length} required fields checked)`);
+  const warningSuffix = warnings.length > 0 ? `; warnings: ${warnings.join("; ")}` : "";
+  return passResult(
+    "task-meta",
+    `Task metadata valid (${requiredFields.length} required fields checked${warningSuffix})`,
+    warnings
+  );
 }
 
 function validateTaskBranch(metadata) {
@@ -683,8 +706,12 @@ function buildSingleCheckSummary(status) {
   return "0 passed, 1 failed";
 }
 
-function passResult(type, message) {
-  return { type, status: "pass", message };
+function passResult(type, message, warnings = []) {
+  const result = { type, status: "pass", message };
+  if (warnings.length > 0) {
+    result.warnings = warnings;
+  }
+  return result;
 }
 
 function failResult(type, message, failType = "check_failed") {

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

@@ -11,6 +11,8 @@ description: "Analyze a task and produce a requirements document"
 - Base the analysis strictly on the existing requirements, context, and source information in `task.md`
 - After executing this skill, you **must** immediately update task status in task.md
 
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
 ## Steps
 
 ### 1. Verify Prerequisites
@@ -110,6 +112,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `current_step`: requirement-analysis
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
+- `agent_infra_version`: value from `.agents/rules/version-stamp.md`
 - Record the analysis artifact for this round: `{analysis-artifact}` (Round `{analysis-round}`)
 - If the task template contains a `## Analysis` section, update it to link to `{analysis-artifact}`
 - Mark requirement-analysis as complete in workflow progress and include the actual round when the task template supports it

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

@@ -11,6 +11,8 @@ description: "分析任务并输出需求分析文档"
 - 严格基于 `task.md` 中已有的需求、上下文和来源信息展开分析
 - 执行本技能后，你**必须**立即更新 task.md 中的任务状态
 
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
 ## 执行步骤
 
 ### 1. 验证前置条件
@@ -110,6 +112,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `current_step`：requirement-analysis
 - `assigned_to`：{当前 AI 代理}
 - `updated_at`：{当前时间}
+- `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
 - 记录本轮分析产物：`{analysis-artifact}`（Round `{analysis-round}`）
 - 如任务模板包含 `## 分析` 段落，更新为指向 `{analysis-artifact}` 的链接
 - 在工作流进度中标记 requirement-analysis 为已完成，并注明实际轮次（如果任务模板支持）

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

@@ -9,6 +9,7 @@
         "status",
         "created_at",
         "updated_at",
+        "agent_infra_version",
         "current_step",
         "assigned_to"
       ],
@@ -37,6 +38,7 @@
       "verify_comment_content": true,
       "verify_task_comment_content": true,
       "verify_issue_type": true,
+      "verify_issue_fields": false,
       "verify_milestone": true,
       "expected_status_label_key": "pendingDesignWork",
       "expected_comment_marker_key": "artifact"

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

@@ -17,6 +17,8 @@ description: "Mark a task as blocked and record the reason"
 - **Resource issues**: Missing access, waiting for external team, blocked by another task
 - **Decision needed**: Architecture decision pending, stakeholder approval required
 
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
 ## Steps
 
 ### 1. Verify Task Exists
@@ -47,6 +49,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `status`: blocked
 - `blocked_at`: {current timestamp}
 - `updated_at`: {current timestamp}
+- `agent_infra_version`: value from `.agents/rules/version-stamp.md`
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Blocked** by {agent} — {one-line reason}

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

@@ -17,6 +17,8 @@ description: "标记任务为阻塞状态并记录原因"
 - **资源问题**：缺少访问权限、等待外部团队、被其他任务阻塞
 - **需要决策**：待定的架构决策、需要利益相关者批准
 
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
 ## 执行步骤
 
 ### 1. 验证任务存在
@@ -47,6 +49,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `status`：blocked
 - `blocked_at`：{当前时间戳}
 - `updated_at`：{当前时间戳}
+- `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Blocked** by {agent} — {一行原因}

package/templates/.agents/skills/block-task/config/verify.json

@@ -9,6 +9,7 @@
         "status",
         "created_at",
         "updated_at",
+        "agent_infra_version",
         "current_step",
         "assigned_to",
         "blocked_at"

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

@@ -11,6 +11,8 @@ description: "Cancel an unneeded task and move it"
 - Cancel only when the task no longer needs implementation, review, or follow-up work
 - When a valid `issue_number` exists, Issue sync is required
 
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
 ## Steps
 
 ### 1. Verify Task Exists
@@ -48,6 +50,7 @@ Update `task.md` in the task directory:
 - `cancelled_at`: {current timestamp}
 - `cancel_reason`: {cancellation reason}
 - `updated_at`: {current timestamp}
+- `agent_infra_version`: value from `.agents/rules/version-stamp.md`
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Cancelled** by {agent} — {one-line cancellation reason}

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

@@ -11,6 +11,8 @@ description: "取消不再需要的任务并转移"
 - 只有在确认该任务无需继续实现、审查或修复时才可取消
 - 有效 `issue_number` 存在时，Issue 同步属于必做项
 
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
 ## 执行步骤
 
 ### 1. 验证任务存在
@@ -48,6 +50,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `cancelled_at`：{当前时间戳}
 - `cancel_reason`：{取消原因}
 - `updated_at`：{当前时间戳}
+- `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
 - **追加**到 `## Activity Log`（不要覆盖之前记录）：
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Cancelled** by {agent} — {一行取消原因}

package/templates/.agents/skills/cancel-task/config/verify.json

@@ -9,6 +9,7 @@
         "status",
         "created_at",
         "updated_at",
+        "agent_infra_version",
         "current_step",
         "assigned_to",
         "cancelled_at",

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

@@ -7,6 +7,16 @@ description: "Commit the current changes to Git"
 
 Create a Git commit without overwriting user work and update the related task state when needed.
 
+When updating related `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
+## Common Rationalizations and Rebuttals
+
+| Rationalization | Rebuttal |
+|------|------|
+| "The tests already ran earlier, so I do not need to rerun them." | The staged content is the current truth; before committing, re-check `git status` and `git diff` instead of relying on memory. |
+| "`git add -A` is faster." | `git add -A` and `git add .` are forbidden; stage only explicitly listed files to avoid including unrelated changes. |
+| "This file has a copyright header, but the year can wait." | If you changed it, update the copyright year using `date +%Y`; this is a hard pre-commit check. |
+
 ## 1. Check Local Modifications (CRITICAL)
 
 Before any edit, inspect:

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

@@ -7,6 +7,16 @@ description: "提交当前变更到 Git"
 
 在不覆盖用户本地工作的前提下创建 Git commit，并在需要时更新关联任务状态。
 
+更新关联 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
+## 常见违规借口与反驳
+
+| 借口 | 反驳 |
+|------|------|
+| 「测试之前跑过了，不用重跑」 | 暂存内容是最新现实；提交前必须重新核对 `git status`/`git diff`，不能凭记忆。 |
+| 「`git add -A` 更省事」 | 禁止 `git add -A`/`git add .`；只暂存明确列出的文件，避免带入无关改动。 |
+| 「改了带版权头的文件，年份先不动」 | 改了就更新版权年份（动态取 `date +%Y`），这是提交前的硬性检查。 |
+
 ## 1. 检查本地修改（关键）
 
 在任何编辑前先检查：

package/templates/.agents/skills/commit/config/verify.json

@@ -9,6 +9,7 @@
         "status",
         "created_at",
         "updated_at",
+        "agent_infra_version",
         "current_step",
         "assigned_to"
       ]

package/templates/.agents/skills/commit/reference/task-status-update.en.md

@@ -2,6 +2,8 @@
 
 Read this file before choosing the post-commit task-state branch.
 
+Before updating task metadata, read `.agents/rules/version-stamp.md` and refresh `agent_infra_version` together with `updated_at`.
+
 ## Update the Related Task State
 
 Get the current time first:
@@ -53,6 +55,7 @@ Next step - complete and archive the task:
 
 If more work is still pending:
 - update `updated_at` in `task.md`
+- update `agent_infra_version` from `.agents/rules/version-stamp.md`
 - record what this commit finished
 - record what the next human or agent action is
 
@@ -61,6 +64,7 @@ If more work is still pending:
 If this commit hands work over to code review:
 - update `current_step` to `code-review`
 - update `updated_at`
+- update `agent_infra_version` from `.agents/rules/version-stamp.md`
 - mark implementation as finished in the workflow state
 
 Required next-step commands:
@@ -76,6 +80,7 @@ Next step - code review:
 
 If the next step is Pull Request creation:
 - update `updated_at`
+- update `agent_infra_version` from `.agents/rules/version-stamp.md`
 - record the PR plan in `task.md`
 
 Required next-step commands:

package/templates/.agents/skills/commit/reference/task-status-update.zh-CN.md

@@ -2,6 +2,8 @@
 
 在选择提交后的任务状态分支之前先读取本文件。
 
+更新任务元数据前，先读取 `.agents/rules/version-stamp.md`，并随 `updated_at` 一起刷新 `agent_infra_version`。
+
 ## 更新关联任务状态
 
 先获取当前时间：
@@ -53,6 +55,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 如果仍有工作待完成：
 - 更新 `task.md` 中的 `updated_at`
+- 按 `.agents/rules/version-stamp.md` 更新 `agent_infra_version`
 - 记录这次提交完成了什么
 - 记录下一位人类或 agent 需要继续做什么
 
@@ -61,6 +64,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 如果这次提交把工作移交给代码审查：
 - 将 `current_step` 更新为 `code-review`
 - 更新 `updated_at`
+- 按 `.agents/rules/version-stamp.md` 更新 `agent_infra_version`
 - 在工作流状态中标记实现阶段已完成
 
 必带下一步命令：
@@ -76,6 +80,7 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 如果下一步是创建 Pull Request：
 - 更新 `updated_at`
+- 按 `.agents/rules/version-stamp.md` 更新 `agent_infra_version`
 - 在 `task.md` 中记录 PR 计划
 
 必带下一步命令：

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

@@ -10,6 +10,8 @@ description: "Mark a task as completed and archive it"
 - This command updates task metadata AND physically moves the task directory
 - Do not move a task that has incomplete workflow steps unless forced
 
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
 ## Steps
 
 ### 1. Verify Task Exists
@@ -58,8 +60,10 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 Update `.agents/workspace/active/{task-id}/task.md`:
 - `status`: completed
+- `current_step`: completed
 - `completed_at`: {current timestamp}
 - `updated_at`: {current timestamp}
+- `agent_infra_version`: value from `.agents/rules/version-stamp.md`
 - Mark all workflow steps as complete
 - Verify and check off all items in `## Completion Checklist` (change `- [ ]` to `- [x]`)
 - **Append** to `## Activity Log` (do NOT overwrite previous entries):

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

@@ -10,6 +10,8 @@ description: "标记任务完成并归档"
 - 本命令更新任务元数据并物理移动任务目录
 - 除非强制执行，不要转移有未完成工作流步骤的任务
 
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
 ## 执行步骤
 
 ### 1. 验证任务存在
@@ -58,8 +60,10 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 
 更新 `.agents/workspace/active/{task-id}/task.md`：
 - `status`：completed
+- `current_step`：completed
 - `completed_at`：{当前时间戳}
 - `updated_at`：{当前时间戳}
+- `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
 - 标记所有工作流步骤为已完成
 - 逐项验证并勾选 `## 完成检查清单` 中的所有条目（将 `- [ ]` 改为 `- [x]`）
 - **追加**到 `## Activity Log`（不要覆盖之前的记录）：

package/templates/.agents/skills/complete-task/config/verify.json

@@ -9,6 +9,7 @@
         "status",
         "created_at",
         "updated_at",
+        "agent_infra_version",
         "current_step",
         "assigned_to",
         "completed_at"
@@ -29,6 +30,7 @@
       "verify_task_comment_content": true,
       "sync_checked_requirements": true,
       "verify_issue_type": true,
+      "verify_issue_fields": false,
       "verify_milestone": true,
       "expected_comment_marker_key": "summary"
     }

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

@@ -7,6 +7,10 @@ description: "Create a Pull Request to a target branch"
 
 Create a Pull Request and, when task-related, sync the essential metadata and reviewer summary immediately.
 
+## Boundary / Critical Rules
+
+Version stamp rule: when creating or updating `task.md` frontmatter, read `.agents/rules/version-stamp.md` first and write or refresh `agent_infra_version`.
+
 ## Execution Flow
 
 ### 1. Parse Command Arguments
@@ -72,7 +76,7 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
-If `{task-id}` is available, update task.md with `pr_number`, `updated_at`, and append the PR Created Activity Log entry including metadata-sync and summary results.
+If `{task-id}` is available, update task.md with `pr_number`, `updated_at`, `agent_infra_version`, and append the PR Created Activity Log entry including metadata-sync and summary results.
 
 ### 9. Verification Gate
 

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

@@ -7,6 +7,10 @@ description: "创建 Pull Request 到目标分支"
 
 创建 Pull Request，并在与任务关联时立即补齐核心元数据和 reviewer 摘要。
 
+## 行为边界 / 关键规则
+
+版本戳规则：创建或更新 `task.md` frontmatter 时，先读取 `.agents/rules/version-stamp.md`，并写入或刷新 `agent_infra_version`。
+
 ## 执行流程
 
 ### 1. 解析命令参数
@@ -72,7 +76,7 @@ description: "创建 Pull Request 到目标分支"
 date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
-如果获取到了 `{task-id}`，更新 task.md 的 `pr_number`、`updated_at`，并追加 PR Created 的 Activity Log，记录元数据同步和摘要发布结果。
+如果获取到了 `{task-id}`，更新 task.md 的 `pr_number`、`updated_at`、`agent_infra_version`，并追加 PR Created 的 Activity Log，记录元数据同步和摘要发布结果。
 
 ### 9. 完成校验
 

package/templates/.agents/skills/create-pr/config/verify.json

@@ -9,6 +9,7 @@
         "status",
         "created_at",
         "updated_at",
+        "agent_infra_version",
         "current_step",
         "assigned_to"
       ]