@fitlab-ai/agent-infra 0.9.11 → 0.9.13

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

@@ -74,6 +74,10 @@ const DEFAULTS = {
   "task": {
     "shortIdLength": 2
   },
+  "delivery": {
+    "remote": "origin",
+    "baseRef": "main"
+  },
   "labels": {
     "in": {}
   },

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

@@ -39,8 +39,8 @@ After prerequisites pass and before this round's first artifact action, append a
 
 Resolve the target PR number `{pr#}` and an optional `{task-id}` via these deterministic branches:
 
-- Scenario A (argument omitted): reverse-lookup the active task from the current branch, then read its `pr_number`.
-- Scenario B (omitted task ref or `--task/-t`, **task-anchored primary path**): resolve the full `{task-id}` via "Task Context Resolution" and read `.agents/workspace/active/{task-id}/task.md` for `pr_number` as `{pr#}`; if `pr_number` is empty, follow "Error Handling" to prompt running `create-pr` first, then stop.
+- Scenario A (argument omitted): reverse-lookup the active task from the current branch, then read its verified `pr_delivery_fact.identity.number`.
+- Scenario B (omitted task ref or `--task/-t`, **task-anchored primary path**): resolve the full `{task-id}` via "Task Context Resolution" and read `.agents/workspace/active/{task-id}/task.md` for verified `pr_delivery_fact.identity.number` as `{pr#}`; if the fact is unbound, follow "Error Handling" to prompt running `create-pr` first, then stop.
 - Scenario C (`--pr <number>` or a PR URL): use that PR number directly as `{pr#}`; then determine `{task-id}` via "Reverse-lookup task".
 - Reverse-lookup task (scenarios A / C): use task context/query capabilities to find the unique active task bound to `{pr#}`. If none exists, stop and request binding first; the typed checks intent does not create a second taskless state machine.
 
@@ -48,13 +48,13 @@ Resolve the target PR number `{pr#}` and an optional `{task-id}` via these deter
 
 Before running this step, read `reference/monitor-and-heal.md` and `.agents/rules/pr-checks-commands.md`.
 
-Initialize `repairCommits=[]` and `rebaseAttempts=0`. Run `agent-infra-internal platform-checks watch {task-id} --interval-seconds 30 --deadline-seconds 1800`, then route only by `readiness.state`: `ready` to step 7, `conflicting|checks-failed` to step 3, and `pending|timed-out|cancelled` to step 4.
+Initialize `repairCommits=[]` and `rebaseAttempts=0`. Before readiness in every round, run `platform-pr summary-context`, rebuild the task-bound `pr-change-report.json` for the authoritative PR head using the shared PR change-report contract, and refresh the single summary with a body containing one `<!-- canonical-pr-change-report -->` placeholder via `summary-sync --change-report-file ... --result no_op --strict`. `--strict` preserves report or summary refresh failures as `failed/blocked` instead of treating warnings as success. A report or summary refresh failure must not enter the ready/complete exit; use step 4. After the refresh, run `agent-infra-internal platform-checks watch {task-id} --interval-seconds 30 --deadline-seconds 1800`, then route only by `readiness.state`: `ready` to step 7, `conflicting|checks-failed` to step 3, and `pending|timed-out|cancelled` to step 4.
 
 ### 3. Self-Heal Loop
 
 Before running this step, read the "Self-Heal Decision Tree" of `reference/monitor-and-heal.md` and "Resolve a Failing Run id and Pull Logs" of `.agents/rules/pr-checks-commands.md`.
 
-For `checks-failed`, minimally fix a locatable code-layer failure, test, and publish through the existing commit/push intents. For `conflicting`, follow the reference's same-repository, clean-tree, head/base identity, rebase, full-test, and `git-workflow push-rebased` exact-lease flow, capped at two attempts. Append only remotely verified SHAs, then watch the new head again; any failed safety check goes to step 4.
+For `checks-failed`, minimally fix a locatable code-layer failure, test, and publish through the existing commit/push intents. For `conflicting`, follow the reference's same-repository, clean-tree, head/base identity, rebase, full-test, and `git-workflow push-rebased` exact-lease flow, capped at two attempts. Append only remotely verified SHAs; after any external push, self-heal commit, or rebase changes the head, refresh the report and summary before watching the new head again; any failed safety check goes to step 4.
 
 ### 4. Help Exit (Produce-Then-Stop)
 
@@ -74,7 +74,7 @@ Update `.agents/workspace/active/{task-id}/task.md`:
 - `assigned_to`: {current agent}
 - `updated_at`: {current time}
 - `agent_infra_version`: per `.agents/rules/version-stamp.md`
-- **Do not change** `pr_status` (keep `created`) or `current_step`
+- **Do not change** `pr_delivery_fact` or `current_step`
 - **Append** to `## Activity Log` (do not overwrite prior entries; `{N}` = number of existing Watch PR entries for this task + 1):
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Watch PR (Round {N})** by {agent} — {success: PR ready, repair commits: {k} [{SHA summary}] / blocked: blocked: {summary}}
@@ -148,6 +148,6 @@ Stop immediately after the checklist. The green exit waits for the user to run `
 
 ## Error Handling
 
-- Cannot locate a PR (task short id resolves but task.md has no `pr_number`, and no `--pr` was passed and the current branch has no PR): prompt "Run `create-pr` first, or specify the PR with `--pr <number>`", then stop.
+- Cannot locate a PR (task short id resolves but task.md has no verified bound `pr_delivery_fact`, and no `--pr` was passed and the current branch has no PR): prompt "Run `create-pr` first, or specify the PR with `--pr <number>`", then stop.
 - Platform CLI not authenticated or API unavailable: prompt that manual intervention is needed, then stop.
 - Short-id resolution failure: pass through `task-short-id.js`'s exit code and error message; do not rewrite it.

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

@@ -39,8 +39,8 @@ description: >
 
 按以下确定性分支解析出目标 PR 号 `{pr#}` 与可选 `{task-id}`：
 
-- 场景 A（省略入参）：从当前分支反查 active task；定位后读取其 `pr_number`。
-- 场景 B（省略 task ref 或 `--task/-t`，**任务锚定主路径**）：按「任务上下文解析」取得完整 `{task-id}`。读 `.agents/workspace/active/{task-id}/task.md` 取 `pr_number` 作为 `{pr#}`；`pr_number` 为空时按「错误处理」提示先 `create-pr`，停止。
+- 场景 A（省略入参）：从当前分支反查 active task；定位后读取其 verified `pr_delivery_fact.identity.number`。
+- 场景 B（省略 task ref 或 `--task/-t`，**任务锚定主路径**）：按「任务上下文解析」取得完整 `{task-id}`。读 `.agents/workspace/active/{task-id}/task.md` 取 verified `pr_delivery_fact.identity.number` 作为 `{pr#}`；fact 未绑定时按「错误处理」提示先 `create-pr`，停止。
 - 场景 C（`--pr <number>` 或 PR URL）：直接取该 PR 号为 `{pr#}`；随后按「反查任务」确定 `{task-id}`。
 - 反查任务（场景 A / C）：通过任务上下文/任务查询取得与 `{pr#}` 唯一绑定的 active task。未命中时停止并提示先绑定 PR；typed checks intent 不建立第二套无任务状态机。
 
@@ -48,13 +48,13 @@ description: >
 
 执行此步骤前，先读取 `reference/monitor-and-heal.md` 与 `.agents/rules/pr-checks-commands.md`。
 
-进入本轮时初始化 `repairCommits=[]` 与 `rebaseAttempts=0`。调用 `agent-infra-internal platform-checks watch {task-id} --interval-seconds 30 --deadline-seconds 1800`，只按结构化 `readiness.state` 分流：`ready` 进入步骤 7，`conflicting` 或 `checks-failed` 进入步骤 3，`pending|timed-out|cancelled` 进入步骤 4。
+进入本轮时初始化 `repairCommits=[]` 与 `rebaseAttempts=0`。每轮 readiness 前先调用 `platform-pr summary-context`，按共享 PR change-report contract 以当前权威 PR head 重建任务绑定的 `pr-change-report.json`，再用含唯一 `<!-- canonical-pr-change-report -->` 占位符的正文调用 `summary-sync --change-report-file ... --result no_op --strict` 刷新同一条摘要。`--strict` 将报告或摘要刷新失败保留为 `failed/blocked`，不得把 warning 当作成功；刷新失败时不得进入 ready/complete 出口，按步骤 4 记录阻塞。刷新完成后调用 `agent-infra-internal platform-checks watch {task-id} --interval-seconds 30 --deadline-seconds 1800`，只按结构化 `readiness.state` 分流：`ready` 进入步骤 7，`conflicting` 或 `checks-failed` 进入步骤 3，`pending|timed-out|cancelled` 进入步骤 4。
 
 ### 3. 自愈循环
 
 执行此步骤前，先读取 `reference/monitor-and-heal.md` 的「自愈决策树」与 `.agents/rules/pr-checks-commands.md` 的「解析失败 run id 并拉日志」。
 
-`checks-failed` 只对可定位代码层失败做最小修复和测试，再用既有 commit/push intent 发布。`conflicting` 严格执行 reference 的同仓库、干净工作树、head/base 身份、rebase、完整测试与 `git-workflow push-rebased` 精确 lease 流程；上限 2 次。仅记录远端复核成功的 SHA，随后重新监控新 head；任一安全检查失败转步骤 4。
+`checks-failed` 只对可定位代码层失败做最小修复和测试，再用既有 commit/push intent 发布。`conflicting` 严格执行 reference 的同仓库、干净工作树、head/base 身份、rebase、完整测试与 `git-workflow push-rebased` 精确 lease 流程；上限 2 次。仅记录远端复核成功的 SHA；任何外部 push、自愈 commit 或 rebase 改变 head 后，先按本轮报告→摘要顺序刷新，再重新监控新 head；任一安全检查失败转步骤 4。
 
 ### 4. 求助出口（产出后停止）
 
@@ -74,7 +74,7 @@ date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 - `assigned_to`：{当前代理}
 - `updated_at`：{当前时间}
 - `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
-- **不改** `pr_status`（保持 `created`）与 `current_step`
+- **不改** `pr_delivery_fact` 与 `current_step`
 - **追加**到 `## 活动日志`（不要覆盖之前的记录；`{N}` = 本任务已有 Watch PR 条目数 + 1）：
   ```
   - {YYYY-MM-DD HH:mm:ss±HH:MM} — **Watch PR (Round {N})** by {agent} — {成功：PR ready, repair commits: {k} [{sha 摘要}] / 阻塞：blocked: {简述}}
@@ -148,6 +148,6 @@ agent-infra-internal task-verify {task-id} watch-pr.completed --format text
 
 ## 错误处理
 
-- 无法定位 PR（任务短号命中但 task.md 无 `pr_number`，且未传 `--pr`、当前分支也无 PR）：提示「请先运行 `create-pr`，或用 `--pr <number>` 指定 PR」，停止。
+- 无法定位 PR（任务短号命中但 task.md 无 verified bound `pr_delivery_fact`，且未传 `--pr`、当前分支也无 PR）：提示「请先运行 `create-pr`，或用 `--pr <number>` 指定 PR」，停止。
 - 平台 CLI 未认证或 API 不可用：提示需人工介入，停止。
 - 短号解析失败：透传 `task-short-id.js` 的退出码与错误信息，不重写。

package/templates/.agents/skills/watch-pr/reference/monitor-and-heal.en.md

@@ -11,6 +11,12 @@ After the watch command, route by structured `readiness.state`:
 - `conflicting`: the platform explicitly reports a head/base conflict → rebase healing in SKILL step 3.
 - `pending|timed-out|cancelled`: no reliable success fact exists → SKILL step 4.
 
+## Summary Refresh Boundary
+
+Before readiness in every round, and after an external push, self-heal commit, or successful rebase changes the PR head, rerun `summary-context` → mechanical report and six-check precheck → `platform-pr change-report` → `summary-sync --change-report-file ... --result no_op --strict` with exactly one `<!-- canonical-pr-change-report -->` placeholder. `--strict` preserves report or summary refresh failures as `failed/blocked` so warnings cannot reach the ready/complete route. The core revalidates the sidecar against the authoritative PR snapshot, task-intent digest, and complete patch; missing, stale, invalid, bypassed, or raced publication must not continue to a ready/complete route and must enter the help exit with a warning.
+
+When rebuilding the precheck, each of the six `rationale` fields must state the corresponding high-level finding and include at least one path, line range, and concise `detail` as evidence. `change-composition` must describe where responsibilities are concentrated; compatibility, legacy-path, redundancy, and scope checks must state their actual results separately, without reused generic boilerplate. Use the deployed skill's language for rationales and evidence details; Chinese skill deployments must use Chinese.
+
 ## Self-Heal Decision Tree
 
 ```text

package/templates/.agents/skills/watch-pr/reference/monitor-and-heal.zh-CN.md

@@ -11,6 +11,12 @@
 - `conflicting`：平台明确当前 head 与 base 冲突 → SKILL 步骤 3 的 rebase 自愈。
 - `pending|timed-out|cancelled`：mergeability/checks 未形成可靠成功事实 → SKILL 步骤 4。
 
+## 摘要刷新边界
+
+每轮 readiness 之前，以及外部 push、自愈 commit 或 rebase 成功改变 PR head 之后，必须重新执行 `summary-context` → 机械报告与六项 precheck → `platform-pr change-report` → 含一次 `<!-- canonical-pr-change-report -->` 的 `summary-sync --change-report-file ... --result no_op --strict`。`--strict` 将报告或摘要刷新失败保留为 `failed/blocked`，不允许 warning 穿透到 ready/complete 路由。core 以权威 PR snapshot、任务意图 digest 和完整 patch 重新校验 sidecar；报告缺失、stale、invalid、占位符绕过或发布竞态时，不得继续 ready/complete 路由，转入求助出口并登记 warning。
+
+每轮重建 precheck 时，六项 `rationale` 都必须是对应检查的实际高层结论，并各带至少一条路径、行号和简短 `detail` 证据；`change-composition` 要说明职责集中位置，兼容、旧路径、冗余和范围检查要分别说明实际结果，禁止复用泛化套话。理由和证据详情遵循当前已部署技能的语言，中文技能必须使用中文。
+
 ## 自愈决策树
 
 ```text

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

@@ -13,7 +13,11 @@ start_date:                     # Optional Issue field for Feature: YYYY-MM-DD
 target_date:                    # Optional Issue field for Feature: YYYY-MM-DD
 current_step: requirement-analysis # requirement-analysis | requirement-analysis-review | technical-design | technical-design-review | code | code-review | completed
 assigned_to:                   # claude | codex | antigravity | opencode | human
-pr_status: pending             # PR status: pending (default) | created (PR created) | skipped (explicitly skipped)
+pr_delivery_fact: '{"version":1,"state":"unbound","reason":"initial"}'
+delivery_remote: origin        # Git remote used to deliver the task branch
+delivery_base_ref: main        # Target branch for the task PR
+checkpoint_commit:             # Most recent local checkpoint commit
+delivery_remote_head:          # Most recent successfully delivered task branch SHA
 ---
 
 # Task: [Title]
@@ -92,7 +96,24 @@ pr_status: pending             # PR status: pending (default) | created (PR crea
 <!-- 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 |
-|----|------|------|----------|------|--------|--------|---------|--------|-------------|------------|
+|----|------|------|----------|------|--------|---------|--------|-------------|------------|------------|
+
+## Rework Intent
+
+| intent_id | finding_id | source_artifact | source_sha256 | target | status | declared_at | consumed_at |
+|-----------|------------|----------------|---------------|--------|--------|-------------|-------------|
+
+## Artifact Invalidation
+
+### Operations
+
+| operation_id | source_family | source_artifact | source_round | source_sha256 | status | processed | total | created_at | updated_at | completed_at | error |
+|--------------|---------------|-----------------|--------------|---------------|--------|-----------|-------|------------|------------|--------------|-------|
+
+### Targets
+
+| target_id | operation_id | target_kind | target_family | target_artifact | target_round | target_sha256 | status | reason_code | updated_at |
+|-----------|--------------|-------------|---------------|-----------------|--------------|---------------|--------|-------------|------------|
 
 ## Activity Log
 

package/templates/.agents/templates/task.zh-CN.md

@@ -13,7 +13,11 @@ start_date:                     # Feature 可选 Issue 字段：YYYY-MM-DD
 target_date:                    # Feature 可选 Issue 字段：YYYY-MM-DD
 current_step: requirement-analysis # requirement-analysis | requirement-analysis-review | technical-design | technical-design-review | code | code-review | completed
 assigned_to:                   # claude | codex | antigravity | opencode | human
-pr_status: pending             # PR 状态：pending（默认）| created（已创建 PR）| skipped（显式跳过）
+pr_delivery_fact: '{"version":1,"state":"unbound","reason":"initial"}'
+delivery_remote: origin        # 任务分支交付使用的 Git remote
+delivery_base_ref: main        # 任务 PR 的目标分支
+checkpoint_commit:             # 最近一次本地 checkpoint commit
+delivery_remote_head:          # 最近一次成功交付到 remote 的任务分支 SHA
 ---
 
 # 任务：[标题]
@@ -92,7 +96,24 @@ pr_status: pending             # PR 状态：pending（默认）| created（已
 <!-- 工作流降级、平台同步失败、权限不足等需要后续注意的事件写入此段。无告警时保留表头即可。 -->
 
 | id | time | step | severity | code | status | target | message | action | resolved_at | resolution |
-|----|------|------|----------|------|--------|--------|---------|--------|-------------|------------|
+|----|------|------|----------|------|--------|---------|--------|-------------|------------|------------|
+
+## 返工意图
+
+| intent_id | finding_id | source_artifact | source_sha256 | target | status | declared_at | consumed_at |
+|-----------|------------|----------------|---------------|--------|--------|-------------|-------------|
+
+## 产物失效记录
+
+### Operations
+
+| operation_id | source_family | source_artifact | source_round | source_sha256 | status | processed | total | created_at | updated_at | completed_at | error |
+|--------------|---------------|-----------------|--------------|---------------|--------|-----------|-------|------------|------------|--------------|-------|
+
+### Targets
+
+| target_id | operation_id | target_kind | target_family | target_artifact | target_round | target_sha256 | status | reason_code | updated_at |
+|-----------|--------------|-------------|---------------|-----------------|--------------|---------------|--------|-------------|------------|
 
 ## 活动日志
 

package/templates/.agents/workflows/bug-fix.en.yaml

@@ -3,7 +3,7 @@
 #
 # Note: whether a step's `pr_tasks` list counts toward workflow progress follows the "PR path" rule:
 # `.agents/.airc.json:prFlow="required"` always counts; `prFlow="disabled"` never counts;
-# when the field is absent, exclude only if task.md's `pr_status=skipped`, otherwise count
+# when the field is absent, exclude only if task.md's `pr_delivery_fact.state=skipped`, otherwise count
 # (see .agents/skills/complete-task/SKILL.md).
 
 name: bug-fix
@@ -126,6 +126,7 @@ steps:
       - Add a regression test that fails without the fix
       - Fix findings from the latest code-review artifact when in fix mode
       - Verify existing tests still pass
+      - Create a local checkpoint commit after tests pass
       - Ensure code follows project conventions
     inputs:
       - Approved fix plan
@@ -177,21 +178,21 @@ steps:
       - Code review report
       - Findings list, if any
 
-  - name: commit
-    description: Finalize the defect fix and create a pull request (the PR portion runs only on the PR path).
+  - name: delivery
+    description: Deliver the approved checkpoint as a pull request, then complete the task after merge and final gates.
     recommended_agents:
       - claude
       - human
     tasks:
-      - Ensure all tests pass
-      - Write a commit message that references the defect or Issue
-      - Move the task to completed
+      - Verify the current HEAD still equals the approved checkpoint
+      - Confirm the task-bound delivery remote and base branch remain valid
+      - Move the task to completed after PR merge and final gates
     pr_tasks:
       - Create a pull request with a defect-fix description
       - Link the PR to the defect report Issue
     inputs:
-      - Final bug-fix branch
+      - Approved local checkpoint
       - Task workspace
     outputs:
-      - Completed task workspace under .agents/workspace/completed/
       - Pull request (only on the PR path)
+      - Completed task workspace under .agents/workspace/completed/ after merge and final gates

package/templates/.agents/workflows/bug-fix.zh-CN.yaml

@@ -3,7 +3,7 @@
 #
 # 注：步骤中的 `pr_tasks` 列表按「走 PR 路径」判定是否计入工作流进度：
 # `.agents/.airc.json:prFlow="required"` 始终计入；`prFlow="disabled"` 不计入；
-# 字段缺省时仅当 task.md 的 `pr_status=skipped` 排除，否则计入（详见 .agents/skills/complete-task/SKILL.md）。
+# 字段缺省时仅当 task.md 的 `pr_delivery_fact.state=skipped` 排除，否则计入（详见 .agents/skills/complete-task/SKILL.md）。
 
 name: bug-fix
 description: 诊断和修复缺陷的工作流。
@@ -125,6 +125,7 @@ steps:
       - 添加在没有修复时会失败的回归测试
       - 修复最新 code-review 产物中要求处理的问题（如处于修复模式）
       - 验证现有测试仍然通过
+      - 测试通过后创建本地 checkpoint commit
       - 确保代码遵循项目规范
     inputs:
       - 已通过审查的修复方案
@@ -176,21 +177,21 @@ steps:
       - 代码审查报告
       - 问题列表（如有）
 
-  - name: commit
-    description: 最终确认缺陷修复并创建拉取请求（PR 部分仅在走 PR 路径时执行）。
+  - name: delivery
+    description: 将已审查的 checkpoint 交付为 PR，并在合并及最终门禁通过后完成任务。
     recommended_agents:
       - claude
       - human
     tasks:
-      - 确保所有测试通过
-      - 编写引用缺陷/Issue 的提交信息
-      - 将任务移至已完成
+      - 验证当前 HEAD 仍等于已审查的 checkpoint
+      - 确认任务绑定的交付 remote 和目标分支仍有效
+      - 在 PR 合并及最终门禁通过后将任务移至已完成
     pr_tasks:
       - 创建包含缺陷修复描述的拉取请求
       - 将 PR 关联到缺陷报告 Issue
     inputs:
-      - 最终缺陷修复分支
+      - 已审查的本地 checkpoint
       - 任务文件
     outputs:
-      - 已完成的任务文件（位于 .agents/workspace/completed/）
       - 拉取请求（仅走 PR 路径时）
+      - 已完成的任务文件（PR 合并和最终门禁通过后）

package/templates/.agents/workflows/feature-development.en.yaml

@@ -3,7 +3,7 @@
 #
 # Note: whether a step's `pr_tasks` list counts toward workflow progress follows the "PR path" rule:
 # `.agents/.airc.json:prFlow="required"` always counts; `prFlow="disabled"` never counts;
-# when the field is absent, exclude only if task.md's `pr_status=skipped`, otherwise count
+# when the field is absent, exclude only if task.md's `pr_delivery_fact.state=skipped`, otherwise count
 # (see .agents/skills/complete-task/SKILL.md).
 
 name: feature-development
@@ -126,6 +126,7 @@ steps:
       - Write unit tests
       - Write integration tests when applicable
       - Fix findings from the latest code-review artifact when in fix mode
+      - Create a local checkpoint commit after tests pass
       - Ensure code follows project conventions
     inputs:
       - Approved technical design
@@ -177,21 +178,21 @@ steps:
       - Code review report
       - Findings to fix
 
-  - name: commit
-    description: Finalize changes and create a pull request (the PR portion runs only on the PR path).
+  - name: delivery
+    description: Deliver the approved checkpoint as a pull request, then complete the task after merge and final gates.
     recommended_agents:
       - claude
       - human
     tasks:
-      - Ensure all tests pass
-      - Write a clear commit message following conventions
-      - Move the task to completed
+      - Verify the current HEAD still equals the approved checkpoint
+      - Confirm the task-bound delivery remote and base branch remain valid
+      - Move the task to completed after PR merge and final gates
     pr_tasks:
       - Create a pull request with an appropriate description
       - Link the PR to the related Issue
     inputs:
-      - Final implementation branch
+      - Approved local checkpoint
       - Task workspace
     outputs:
-      - Completed task workspace under .agents/workspace/completed/
       - Pull request (only on the PR path)
+      - Completed task workspace under .agents/workspace/completed/ after merge and final gates

package/templates/.agents/workflows/feature-development.zh-CN.yaml

@@ -3,7 +3,7 @@
 #
 # 注：步骤中的 `pr_tasks` 列表按「走 PR 路径」判定是否计入工作流进度：
 # `.agents/.airc.json:prFlow="required"` 始终计入；`prFlow="disabled"` 不计入；
-# 字段缺省时仅当 task.md 的 `pr_status=skipped` 排除，否则计入（详见 .agents/skills/complete-task/SKILL.md）。
+# 字段缺省时仅当 task.md 的 `pr_delivery_fact.state=skipped` 排除，否则计入（详见 .agents/skills/complete-task/SKILL.md）。
 
 name: feature-development
 description: 开发新功能的端到端工作流。
@@ -125,6 +125,7 @@ steps:
       - 编写单元测试
       - 编写集成测试（如适用）
       - 修复最新 code-review 产物中要求处理的问题（如处于修复模式）
+      - 测试通过后创建本地 checkpoint commit
       - 确保代码遵循项目规范
     inputs:
       - 已通过审查的技术设计
@@ -176,21 +177,21 @@ steps:
       - 代码审查报告
       - 待修复问题列表
 
-  - name: commit
-    description: 最终确认变更并创建拉取请求（PR 部分仅在走 PR 路径时执行）。
+  - name: delivery
+    description: 将已审查的 checkpoint 交付为 PR，并在合并及最终门禁通过后完成任务。
     recommended_agents:
       - claude
       - human
     tasks:
-      - 确保所有测试通过
-      - 按规范编写清晰的提交信息
-      - 将任务移至已完成
+      - 验证当前 HEAD 仍等于已审查的 checkpoint
+      - 确认任务绑定的交付 remote 和目标分支仍有效
+      - 在 PR 合并及最终门禁通过后将任务移至已完成
     pr_tasks:
       - 创建包含适当描述的拉取请求
       - 将 PR 关联到相关 Issue
     inputs:
-      - 最终实现分支
+      - 已审查的本地 checkpoint
       - 任务文件
     outputs:
-      - 已完成的任务文件（位于 .agents/workspace/completed/）
       - 拉取请求（仅走 PR 路径时）
+      - 已完成的任务文件（PR 合并和最终门禁通过后）

package/templates/.agents/workflows/refactoring.en.yaml

@@ -3,7 +3,7 @@
 #
 # Note: whether a step's `pr_tasks` list counts toward workflow progress follows the "PR path" rule:
 # `.agents/.airc.json:prFlow="required"` always counts; `prFlow="disabled"` never counts;
-# when the field is absent, exclude only if task.md's `pr_status=skipped`, otherwise count
+# when the field is absent, exclude only if task.md's `pr_delivery_fact.state=skipped`, otherwise count
 # (see .agents/skills/complete-task/SKILL.md).
 
 name: refactoring
@@ -128,6 +128,7 @@ steps:
       - Verify tests after each step
       - Fix findings from the latest code-review artifact when in fix mode
       - Update affected docs or comments
+      - Create a local checkpoint commit after tests pass
       - Ensure code follows project conventions
     inputs:
       - Approved refactoring plan
@@ -181,21 +182,21 @@ steps:
       - Code review report
       - Findings list, if any
 
-  - name: commit
-    description: Finalize the refactoring and create a pull request (the PR portion runs only on the PR path).
+  - name: delivery
+    description: Deliver the approved checkpoint as a pull request, then complete the task after merge and final gates.
     recommended_agents:
       - claude
       - human
     tasks:
-      - Ensure all tests pass
-      - Write a clear commit message explaining the refactoring
-      - Move the task to completed
+      - Verify the current HEAD still equals the approved checkpoint
+      - Confirm the task-bound delivery remote and base branch remain valid
+      - Move the task to completed after PR merge and final gates
     pr_tasks:
       - Create a pull request with detailed changes
       - Link the PR to the related Issue
     inputs:
-      - Final refactoring branch
+      - Approved local checkpoint
       - Task workspace
     outputs:
-      - Completed task workspace under .agents/workspace/completed/
       - Pull request (only on the PR path)
+      - Completed task workspace under .agents/workspace/completed/ after merge and final gates

package/templates/.agents/workflows/refactoring.zh-CN.yaml

@@ -3,7 +3,7 @@
 #
 # 注：步骤中的 `pr_tasks` 列表按「走 PR 路径」判定是否计入工作流进度：
 # `.agents/.airc.json:prFlow="required"` 始终计入；`prFlow="disabled"` 不计入；
-# 字段缺省时仅当 task.md 的 `pr_status=skipped` 排除，否则计入（详见 .agents/skills/complete-task/SKILL.md）。
+# 字段缺省时仅当 task.md 的 `pr_delivery_fact.state=skipped` 排除，否则计入（详见 .agents/skills/complete-task/SKILL.md）。
 
 name: refactoring
 description: 安全且结构化的代码重构工作流。
@@ -127,6 +127,7 @@ steps:
       - 每步后验证测试通过
       - 修复最新 code-review 产物中要求处理的问题（如处于修复模式）
       - 更新受影响的文档或注释
+      - 测试通过后创建本地 checkpoint commit
       - 确保代码遵循项目规范
     inputs:
       - 已通过审查的重构计划
@@ -180,21 +181,21 @@ steps:
       - 代码审查报告
       - 问题列表（如有）
 
-  - name: commit
-    description: 最终确认重构并创建拉取请求（PR 部分仅在走 PR 路径时执行）。
+  - name: delivery
+    description: 将已审查的 checkpoint 交付为 PR，并在合并及最终门禁通过后完成任务。
     recommended_agents:
       - claude
       - human
     tasks:
-      - 确保所有测试通过
-      - 编写清晰的提交信息说明重构内容
-      - 将任务移至已完成
+      - 验证当前 HEAD 仍等于已审查的 checkpoint
+      - 确认任务绑定的交付 remote 和目标分支仍有效
+      - 在 PR 合并及最终门禁通过后将任务移至已完成
     pr_tasks:
       - 创建包含详细变更描述的拉取请求
       - 将 PR 关联到相关 Issue
     inputs:
-      - 最终重构分支
+      - 已审查的本地 checkpoint
       - 任务文件
     outputs:
-      - 已完成的任务文件（位于 .agents/workspace/completed/）
       - 拉取请求（仅走 PR 路径时）
+      - 已完成的任务文件（PR 合并和最终门禁通过后）

package/templates/.github/workflows/pr-label.yml

@@ -20,36 +20,17 @@ jobs:
       - name: Checkout base branch
         uses: actions/checkout@v7
 
+      - name: Set up Node.js
+        uses: actions/setup-node@v7
+        with:
+          node-version: 22.9.0
+
       - name: Sync in-labels
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           PR_NUMBER: ${{ github.event.pull_request.number }}
-        run: |
-          changed_files=$(gh api "repos/$GITHUB_REPOSITORY/pulls/$PR_NUMBER/files" \
-            --paginate --jq '.[].filename' | jq -Rn '[inputs]')
-
-          should_labels=$(jq -rn \
-            --argjson files "$changed_files" \
-            --argjson mapping "$(jq '.labels.in // {}' .agents/.airc.json)" \
-            '$mapping
-            | to_entries
-            | map(select(.value | any(. as $prefix | $files | any(startswith($prefix)))))
-            | map("in: " + .key)
-            | .[]?')
-
-          set -- \
-            --repo "$GITHUB_REPOSITORY" \
-            --pr "$PR_NUMBER" \
-            --prefix "in: "
-
-          while IFS= read -r label; do
-            [ -z "$label" ] && continue
-            set -- "$@" --target "$label"
-          done <<EOF
-          $should_labels
-          EOF
-
-          .github/scripts/sync-labels-to-set.sh "$@"
+          AGENT_INFRA_VERSION: 0.9.13-alpha.0
+        run: npm exec --yes --package="@fitlab-ai/agent-infra@$AGENT_INFRA_VERSION" -- agent-infra-internal platform-pr sync-in-labels --pr "$PR_NUMBER" --cwd "$GITHUB_WORKSPACE"
 
       - name: Assign PR creator if unassigned
         env:

package/templates/.agents/rules/create-issue.github.en.md

@@ -1,14 +0,0 @@
-# Issue Creation
-
-> `--agent` values are defined in `.agents/rules/task-management.md` under “Collaborator Token Specification”.
-
-After `create-task` writes task.md, create and initialize the Issue through declarative internal intents:
-
-```bash
-agent-infra-internal platform-issue create {task-id} --agent {standard-agent-token}
-agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} --status waiting-for-triage --assignees current --milestone initial --issue-type --fields
-```
-
-The core reads only persisted task identity, title, type, description, and requirements, and reuses deterministic `ai task issue-body` rendering. It owns template selection, upstream/capabilities, duplicate prevention, POST outcome boundaries, response validation, and atomic `issue_number` binding.
-
-`planned|applied|no-op|degraded` exit 0, `failed` exits 1, and `blocked` exits 2. Callers must not fall back to direct `gh issue` or GraphQL orchestration.

package/templates/.agents/rules/create-issue.github.zh-CN.md

@@ -1,27 +0,0 @@
-# Issue 创建
-
-> `--agent` 取值见 `.agents/rules/task-management.md`「合作者 token 规范」。
-
-当 `create-task` 完成本地 `task.md` 落盘后，通过声明式内部命令创建 Issue：
-
-```bash
-agent-infra-internal platform-issue create {task-id} --agent {standard-agent-token}
-```
-
-命令只从已落盘 task.md 读取身份、标题、类型、描述与需求，并复用 `ai task issue-body` 的确定性正文渲染。它负责模板选择、upstream/capability、已有绑定检查、非幂等 POST 边界、响应身份校验及通过任务写入内核回写 `issue_number`。
-
-创建后的初始元数据使用同一适配层同步：
-
-```bash
-agent-infra-internal platform-issue sync {task-id} --agent {standard-agent-token} \
-  --status waiting-for-triage --assignees current --milestone initial --issue-type --fields
-```
-
-## 结果处理
-
-- `planned|applied|no-op|degraded`：exit 0；调用方按 operations 继续评论同步。
-- `failed`：exit 1；调用方登记 `ISSUE_CREATE_FAILED` warning，不伪造绑定。
-- `blocked`：exit 2；认证、网络或创建 outcome 不确定，调用方保留远端 identity 证据并停止盲目重试。
-- 已绑定有效 Issue 时只验证绑定并返回 no-op，绝不重复创建。
-
-自定义或空平台返回 no-op/degraded；调用方不得回退到直接 `gh issue` 或 GraphQL 编排。

package/templates/.agents/rules/issue-pr-commands.github.en.md

@@ -1,34 +0,0 @@
-# PR Platform Intents
-
-> `--agent` values are defined in `.agents/rules/task-management.md` under “Collaborator Token Specification”.
-
-PR lookup, creation, binding, and metadata synchronization go through typed internal intents. Skills decide branches and write titles/bodies; they do not assemble platform commands.
-
-## Inspect
-
-```bash
-agent-infra-internal platform-pr inspect {task-id}
-```
-
-## Create or recover
-
-```bash
-agent-infra-internal platform-pr create {task-id} \
-  --agent {standard-agent-token} --base {target-branch} --head {current-branch} \
-  --title-file {title-file} --body-file {body-file}
-```
-
-The core performs exact upstream/head/base lookup. One match is reused, zero creates, and multiple matches fail closed. Unknown create outcomes are reconciled by exact identity. `--dry-run` returns only the plan.
-
-## Bind and synchronize
-
-```bash
-agent-infra-internal platform-pr bind {task-id} --pr {pr-number} --agent {standard-agent-token}
-
-agent-infra-internal platform-pr sync {task-id} \
-  --agent {standard-agent-token} --metadata --closing-issue
-```
-
-Conflicting bindings do not change `task.md`. Metadata comes from the linked Issue, permission-bound items degrade independently, and an already-created PR is never rolled back.
-
-Statuses `planned|applied|no-op|degraded` exit 0, `failed` exits 1, and `blocked` exits 2.