@fitlab-ai/agent-infra 0.11.15 → 0.12.0

package/templates/.agents/skills/commit/reference/pr-summary-sync.en.md

@@ -4,6 +4,6 @@ Run only when `{task-id}` is valid and task.md has a `bound/verified` `pr_delive
 
 1. Run `agent-infra-internal platform-pr summary-context {task-id}` to obtain canonical inputs and report status; rebuild a stale/missing sidecar through the `change-report` flow for the current head.
 2. Generate the plain summary body per `.agents/rules/pr-sync.md`, with exactly one `<!-- canonical-pr-change-report -->` placeholder, and write it to a temporary file.
-3. Run `agent-infra-internal platform-pr summary-sync {task-id} --agent {standard-agent-token} --body-file {summary-body-file} --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json --result no_op`. The commit path only synchronizes an existing PR summary and neither creates nor reuses a PR, so `no_op` explicitly represents the unchanged PR identity.
+3. Run `agent-infra-internal platform-pr summary-sync {task-id} --agent {standard-agent-token} --body-file {summary-body-file} --change-report-file <task-workspace>/active/{task-id}/pr-change-report.json --result no_op`. The commit path only synchronizes an existing PR summary and neither creates nor reuses a PR, so `no_op` explicitly represents the unchanged PR identity.
 
 Failure records a warning but never blocks or rolls back the completed commit. `no-op` maps to `summary skipped (no diff)`.

package/templates/.agents/skills/commit/reference/pr-summary-sync.zh-CN.md

@@ -4,6 +4,6 @@
 
 1. 调用 `agent-infra-internal platform-pr summary-context {task-id}` 获取 canonical 聚合输入和报告状态；sidecar stale/missing 时先按 `change-report` 流程重建当前 head 报告。
 2. 按 `.agents/rules/pr-sync.md` 生成只含一次 `<!-- canonical-pr-change-report -->` 的纯摘要正文并写入临时文件。
-3. 调用 `agent-infra-internal platform-pr summary-sync {task-id} --agent {standard-agent-token} --body-file {summary-body-file} --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json --result no_op`。commit 路径只同步已有 PR 摘要，不创建或复用 PR，因此固定使用 `no_op` 表示 PR 身份未变化。
+3. 调用 `agent-infra-internal platform-pr summary-sync {task-id} --agent {standard-agent-token} --body-file {summary-body-file} --change-report-file <task-workspace>/active/{task-id}/pr-change-report.json --result no_op`。commit 路径只同步已有 PR 摘要，不创建或复用 PR，因此固定使用 `no_op` 表示 PR 身份未变化。
 
 同步失败只记录 warning，不阻塞或回滚已经完成的 commit。`no-op` 回传 `summary skipped (no diff)`。

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

@@ -59,7 +59,7 @@ complete-manual-validation [--task <ref> | -t <ref>] [{pr-ref}] {verification-su
 ### 2. Verify Prerequisites
 
 Check:
-- `.agents/workspace/active/{task-id}/task.md`
+- `<task-workspace>/active/{task-id}/task.md`
 - a valid PR: prefer explicit `{pr-ref}`, otherwise read verified `pr_delivery_fact.identity.number` from task.md frontmatter
 
 Stop if the task is missing, the validation summary is missing, or no valid PR can be resolved.
@@ -96,7 +96,7 @@ Follow `reference/summary-update.md` to validate the PR binding, obtain canonica
 ```bash
 agent-infra-internal manual-validation transaction {task-id} \
   --artifact {manual-validation-artifact} \
-  --summary-file {summary-body-file} --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json \
+  --summary-file {summary-body-file} --change-report-file <task-workspace>/active/{task-id}/pr-change-report.json \
   --agent {standard-agent-token} --result no_op
 ```
 

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

@@ -59,7 +59,7 @@ complete-manual-validation [--task <ref> | -t <ref>] [{pr-ref}] {verification-su
 ### 2. 验证前置条件
 
 检查：
-- `.agents/workspace/active/{task-id}/task.md`
+- `<task-workspace>/active/{task-id}/task.md`
 - 有效 PR：优先使用显式 `{pr-ref}`，否则读取 task.md frontmatter 的 verified `pr_delivery_fact.identity.number`
 
 如果任务不存在、验证说明缺失，或无法解析有效 PR，立即停止。
@@ -96,7 +96,7 @@ prepare 必须先幂等登记 `manual-validation.started`，再写入 prepared t
 ```bash
 agent-infra-internal manual-validation transaction {task-id} \
   --artifact {manual-validation-artifact} \
-  --summary-file {summary-body-file} --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json \
+  --summary-file {summary-body-file} --change-report-file <task-workspace>/active/{task-id}/pr-change-report.json \
   --agent {standard-agent-token} --result no_op
 ```
 

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

@@ -28,7 +28,6 @@
       ]
     },
     "activity-log": {
-      "expected_action_pattern": "Complete Manual Validation"
     },
     "review-ledger": {
       "stage_scope": [

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

@@ -28,7 +28,6 @@
       ]
     },
     "activity-log": {
-      "expected_action_pattern": "Complete Manual Validation"
     },
     "review-ledger": {
       "stage_scope": [

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

@@ -19,7 +19,7 @@ agent-infra-internal manual-validation transaction {task-id} --prepare \
 agent-infra-internal manual-validation transaction {task-id} \
   --artifact {manual-validation-artifact} \
   --summary-file {summary-body-file} \
-  --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json \
+  --change-report-file <task-workspace>/active/{task-id}/pr-change-report.json \
   --agent {standard-agent-token} --result no_op
 ```
 

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

@@ -19,7 +19,7 @@ agent-infra-internal manual-validation transaction {task-id} --prepare \
 agent-infra-internal manual-validation transaction {task-id} \
   --artifact {manual-validation-artifact} \
   --summary-file {summary-body-file} \
-  --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json \
+  --change-report-file <task-workspace>/active/{task-id}/pr-change-report.json \
   --agent {standard-agent-token} --result no_op
 ```
 

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

@@ -50,7 +50,7 @@ On the normal path, complete business updates, platform sync, and the pre-comple
 
 ### 1. Verify Task Exists
 
-Check that the task exists in `.agents/workspace/active/{task-id}/`.
+Check that the task exists in `<task-workspace>/active/{task-id}/`.
 
 Note: `{task-id}` format is `TASK-{yyyyMMdd-HHmmss}`, e.g. `TASK-20260306-143022`
 
@@ -102,7 +102,7 @@ Run /create-pr --task {task-ref} first, then complete; --skip-pr is not accepted
 ```
 
 Before lifecycle, verify only the hard gates:
-- [ ] Task identity, active state, concurrency locks, and local atomic lifecycle operations are available
+- [ ] Task identity, active-state validation, and local atomic lifecycle operations are available
 - [ ] Required-PR delivery is satisfied when `prFlow=required`
 - [ ] Other business evidence (workflow, review, commit, tests, disagreement ledger, manual validation, and platform sync) is recorded or can be checked after lifecycle; manual validation requires a committed transaction, receipt, current artifact digest, and an identity-bearing completion log
 
@@ -174,11 +174,11 @@ 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.
+This event runs only the required-PR delivery hard preflight; host finalization still enforces identity validation 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.
 
-`--force` cannot lift identity, concurrency, local atomicity, or required-PR hard gates; failures there must stop. Other review, manual-validation, and platform evidence is recorded by terminal verification as warning/pending and can be repaired by retrying.
+`--force` cannot lift identity validation, local atomicity, or required-PR hard gates; failures there must stop. Other review, manual-validation, and platform evidence is recorded by terminal verification as warning/pending and can be repaired by retrying.
 
 ### 6. Run the Host Finalization Entry Point
 
@@ -209,7 +209,7 @@ Task {task-id} completed; task directory moved to completed/.
 Task info:
 - Title: {title}
 - Completed at: {timestamp}
-- Target path: .agents/workspace/completed/{task-id}/
+- Target path: <task-workspace>/completed/{task-id}/
 
 Deliverables:
 - {List of key outputs: files modified, tests added, etc.}
@@ -227,7 +227,7 @@ ai sandbox rm {task-id}  # or use the task's retained short id
 
 - [ ] Verified all workflow steps are complete
 - [ ] Updated task.md with completed status and timestamp
-- [ ] Moved task directory to `.agents/workspace/completed/`
+- [ ] Moved task directory to `<task-workspace>/completed/`
 - [ ] Verified move succeeded
 - [ ] Informed user of completion
 
@@ -242,7 +242,7 @@ ai sandbox rm {task-id}  # or use the task's retained short id
 
 2. **Rollback**: If a task was incorrectly moved:
    ```bash
-   mv .agents/workspace/completed/{task-id} .agents/workspace/active/{task-id}
+   mv <task-workspace>/completed/{task-id} <task-workspace>/active/{task-id}
    ```
    Then update task.md status back to `active`.
 

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

@@ -49,7 +49,7 @@ agent-infra-internal task-snapshot {task-id} --format text
 ## 执行步骤
 ### 1. 验证任务存在
 
-检查任务是否存在于 `.agents/workspace/active/{task-id}/`。
+检查任务是否存在于 `<task-workspace>/active/{task-id}/`。
 
 注意：`{task-id}` 格式为 `TASK-{yyyyMMdd-HHmmss}`，例如 `TASK-20260306-143022`
 
@@ -101,7 +101,7 @@ agent-infra-internal platform-pr resolve-external {task-id} --agent {standard-ag
 ```
 
 生命周期前只验证硬门禁：
-- [ ] task 身份、active 状态、并发锁和本地原子生命周期操作可用
+- [ ] task 身份、active 状态校验和本地原子生命周期操作可用
 - [ ] `prFlow=required` 时已满足 required-PR delivery
 - [ ] 其余业务证据（工作流、审查、提交、测试、分歧账本、人工校验和平台同步）已记录或可在生命周期后校验；人工验证只能由 committed transaction、receipt、当前 artifact 摘要和带 identity 的通过日志满足
 
@@ -125,7 +125,7 @@ Please satisfy the hard prerequisite first, then retry complete-task.
 
 ### 3. 完成业务内容更新
 
-在 `.agents/workspace/active/{task-id}/task.md` 中只更新生命周期核心不负责的业务内容：
+在 `<task-workspace>/active/{task-id}/task.md` 中只更新生命周期核心不负责的业务内容：
 - 新增或更新 `## 状态核对` 段，记录第 0 步审计命令、任务/产物范围、关键结果和未覆盖部分；正常成功不复制完整目录清单或 `task.md` 尾部，失败、阻塞、身份不一致或争议时附决定性原文行，放在 `## 活动日志` 之前
 - 标记所有工作流步骤为已完成
 - 逐项验证并勾选 `## 完成检查清单` 中的所有条目（将 `- [ ]` 改为 `- [x]`）
@@ -173,11 +173,11 @@ 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 后停止。
+该事件只执行 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 决定。
 
-`--force` 不能解除身份、并发、本地原子性或 required-PR hard gate；这些能力失败时必须停止。其余审查、人工校验和平台证据由 terminal verification 记录为 warning/pending，并通过后续重试恢复。
+`--force` 不能解除身份校验、本地原子性或 required-PR hard gate；这些能力失败时必须停止。其余审查、人工校验和平台证据由 terminal verification 记录为 warning/pending，并通过后续重试恢复。
 
 ### 6. 执行宿主 finalization 入口
 
@@ -208,7 +208,7 @@ complete 保留短号映射。它只会在受管 sandbox 清理确认容器已
 任务信息：
 - 标题：{title}
 - 完成时间：{timestamp}
-- 目标路径：.agents/workspace/completed/{task-id}/
+- 目标路径：<task-workspace>/completed/{task-id}/
 
 交付物：
 - {关键产出列表：修改的文件、添加的测试等}
@@ -226,7 +226,7 @@ ai sandbox rm {task-id}  # 或使用本任务仍保留的短号
 
 - [ ] 验证了所有工作流步骤已完成
 - [ ] 更新了 task.md 的完成状态和时间戳
-- [ ] 将任务目录移动到 `.agents/workspace/completed/`
+- [ ] 将任务目录移动到 `<task-workspace>/completed/`
 - [ ] 验证了转移成功
 - [ ] 告知了用户完成情况
 
@@ -241,7 +241,7 @@ ai sandbox rm {task-id}  # 或使用本任务仍保留的短号
 
 2. **回滚**：如果任务被错误转移：
    ```bash
-   mv .agents/workspace/completed/{task-id} .agents/workspace/active/{task-id}
+   mv <task-workspace>/completed/{task-id} <task-workspace>/active/{task-id}
    ```
    然后将 task.md 中的状态改回 `active`。
 

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

@@ -18,7 +18,6 @@
       "require_completed_at": true
     },
     "activity-log": {
-      "expected_action_pattern": "(Complete Task|Completed)"
     },
     "completion-checklist": {
       "require_all_checked": true

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

@@ -18,7 +18,6 @@
       "require_completed_at": true
     },
     "activity-log": {
-      "expected_action_pattern": "(Complete Task|Completed)"
     },
     "completion-checklist": {
       "require_all_checked": true

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

@@ -47,7 +47,7 @@ No Pull Request is required; run instead:
 
 Parse the task scope first: an optional `--task <ref>` or `-t <ref>` selects `{task-id}`; a positional task ref is not interpreted. The remaining positional argument, when present, is `{target-branch}`.
 
-If `{task-id}` is provided, read `.agents/workspace/active/{task-id}/task.md` to load task metadata such as `platform_issue_identity` and `type`.
+If `{task-id}` is provided, read `<task-workspace>/active/{task-id}/task.md` to load task metadata such as `platform_issue_identity` and `type`.
 If `{task-id}` is omitted, try to resolve it from the current session context; if it still cannot be determined, skip task-association logic in later steps.
 
 ### 2. Determine the Target Branch
@@ -68,7 +68,7 @@ Run `agent-infra-internal task-delivery {task-id} deliver --agent {standard-agen
 
 ### 5. Create or Recover the PR
 
-Read `.agents/rules/issue-pr-commands.md`, write the title and body to temporary files, then invoke its `platform-pr create` intent. Under the task lock, core uses remote branch and exact head/base/PR identity facts: one existing PR is reused and bound, zero creates, and multiple matches fail deterministically. Review artifacts and task sync records are not create-pr prerequisites, and replays must not create duplicate PRs.
+Read `.agents/rules/issue-pr-commands.md`, write the title and body to temporary files, then invoke its `platform-pr create` intent. Core uses remote branch and exact head/base/PR identity facts: one existing PR is reused and bound, zero creates, and multiple matches fail deterministically. Review artifacts and task sync records are not create-pr prerequisites, and replays must not create duplicate PRs.
 
 If `{task-id}` is available and the related task provides `platform_issue_identity`, keep `Closes #{issue-number}` or the provider-equivalent closing keyword in the PR body when supported.
 
@@ -86,7 +86,7 @@ The core renderer owns the report section. It is part of the reviewer summary be
 
 Read the latest context artifacts when they exist: `plan.md` / `plan-r{N}.md`, `review-plan.md` / `review-plan-r{N}.md`, `code.md` / `code-r{N}.md`, and `review-code.md` / `review-code-r{N}.md`.
 
-Aggregate a reviewer-facing summary from those artifacts with exactly one `<!-- canonical-pr-change-report -->` placeholder, and maintain a single idempotent summary comment via the hidden marker. Pass `--change-report-file .agents/workspace/active/{task-id}/pr-change-report.json` and the same `--result {primary-result}` to `summary-sync`; a sync substep must not infer whether the PR was created or reused.
+Aggregate a reviewer-facing summary from those artifacts with exactly one `<!-- canonical-pr-change-report -->` placeholder, and maintain a single idempotent summary comment via the hidden marker. Pass `--change-report-file <task-workspace>/active/{task-id}/pr-change-report.json` and the same `--result {primary-result}` to `summary-sync`; a sync substep must not infer whether the PR was created or reused.
 
 > Canonical context, aggregation, and the `summary-sync` call live in `reference/comment-publish.md`, which points to `.agents/rules/pr-sync.md`. Read that reference before publishing.
 

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

@@ -47,7 +47,7 @@ description: >
 
 先解析 task scope：可选的 `--task <ref>` 或 `-t <ref>` 绑定 `{task-id}`；位置 task ref 不再解释。剩余的可选位置参数绑定为 `{target-branch}`。
 
-如果提供了 `{task-id}`，读取 `.agents/workspace/active/{task-id}/task.md` 获取任务信息（例如 `platform_issue_identity`、`type` 等）。
+如果提供了 `{task-id}`，读取 `<task-workspace>/active/{task-id}/task.md` 获取任务信息（例如 `platform_issue_identity`、`type` 等）。
 如果未提供，可从当前 session 上下文获取；仍无法确定 `{task-id}` 时，后续步骤中的任务关联逻辑跳过。
 
 ### 2. 确定目标分支
@@ -68,7 +68,7 @@ description: >
 
 ### 5. 创建或恢复 PR
 
-执行前先读取 `.agents/rules/issue-pr-commands.md`，把标题和正文写入临时文件，并调用其中的 `platform-pr create` intent。core 在任务锁内按 remote branch、head/base 和 PR 身份事实执行：唯一既有 PR 会复用并绑定，零个才创建，多个稳定失败；review 或 task sync 记录不作为创建 PR 的前置门禁，重放不得产生重复 PR。
+执行前先读取 `.agents/rules/issue-pr-commands.md`，把标题和正文写入临时文件，并调用其中的 `platform-pr create` intent。core 按 remote branch、head/base 和 PR 身份事实执行：唯一既有 PR 会复用并绑定，零个才创建，多个稳定失败；review 或 task sync 记录不作为创建 PR 的前置门禁，重放不得产生重复 PR。
 
 如果获取到 `{task-id}` 且对应任务提供了 `platform_issue_identity`，在 provider 支持 numeric closing reference 时必须在 PR 正文中保留 `Closes #{issue-number}` 或 provider 等价关闭关键字。
 
@@ -86,7 +86,7 @@ description: >
 
 读取最新的上下文产物：`plan.md` / `plan-r{N}.md`、`review-plan.md` / `review-plan-r{N}.md`、`code.md` / `code-r{N}.md`、`review-code.md` / `review-code-r{N}.md`（存在时）。
 
-基于这些产物聚合 reviewer 摘要，正文只放一次 `<!-- canonical-pr-change-report -->` 占位符，再使用隐藏标记维护唯一且幂等的摘要评论。调用 `summary-sync` 时传入 `--change-report-file .agents/workspace/active/{task-id}/pr-change-report.json`，并继续传递同一个 `--result {primary-result}`；不得根据同步子步骤猜测 PR 是创建还是复用。
+基于这些产物聚合 reviewer 摘要，正文只放一次 `<!-- canonical-pr-change-report -->` 占位符，再使用隐藏标记维护唯一且幂等的摘要评论。调用 `summary-sync` 时传入 `--change-report-file <task-workspace>/active/{task-id}/pr-change-report.json`，并继续传递同一个 `--result {primary-result}`；不得根据同步子步骤猜测 PR 是创建还是复用。
 
 > canonical context、摘要聚合和 `summary-sync` 调用见 `reference/comment-publish.md`（其引用 `.agents/rules/pr-sync.md`）。发布摘要前先读取该 reference。
 

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

@@ -15,7 +15,6 @@
       ]
     },
     "activity-log": {
-      "expected_action_pattern": "(Create PR|PR Created)"
     },
     "platform-sync": {
       "when": "platform_issue_identity_exists"

package/templates/.agents/skills/create-pr/reference/change-report.en.md

@@ -65,4 +65,4 @@ Briefly explain:
 - whether any change cannot be traced directly to the PR goal and may be unnecessary; if none, state the evidence; every check must cite file and line evidence;
 - when a test fixture is much larger than production changes, what risk it covers instead of judging it only by size.
 
-Do not write the `### PR Code Changes` section in the caller. Put exactly one `<!-- canonical-pr-change-report -->` placeholder in the plain body and let `summary-sync --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json --result {primary-result}` replace it through the core renderer. Do not create a second PR comment for this report.
+Do not write the `### PR Code Changes` section in the caller. Put exactly one `<!-- canonical-pr-change-report -->` placeholder in the plain body and let `summary-sync --change-report-file <task-workspace>/active/{task-id}/pr-change-report.json --result {primary-result}` replace it through the core renderer. Do not create a second PR comment for this report.

package/templates/.agents/skills/create-pr/reference/change-report.zh-CN.md

@@ -65,4 +65,4 @@ canonical 汇总中的固定分类把 `docs/`、Markdown/MDX/reStructuredText
 - 是否存在与 PR 目标无法直接对应、疑似不必要的变化；若没有，明确说明判断依据；每项结论必须给出文件和行号证据；
 - 若某个测试 fixture 明显大于生产改动，解释它覆盖的风险，而不是仅以行数评价。
 
-调用方不要自行写入 `### PR 代码增减`。把恰好包含一次 `<!-- canonical-pr-change-report -->` 的普通摘要正文交给 `summary-sync --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json --result {primary-result}`，由 core renderer 替换并发布。报告不另建第二条 PR 评论。
+调用方不要自行写入 `### PR 代码增减`。把恰好包含一次 `<!-- canonical-pr-change-report -->` 的普通摘要正文交给 `summary-sync --change-report-file <task-workspace>/active/{task-id}/pr-change-report.json --result {primary-result}`，由 core renderer 替换并发布。报告不另建第二条 PR 评论。

package/templates/.agents/skills/create-pr/reference/comment-publish.en.md

@@ -7,7 +7,7 @@ Write the plain summary body, containing exactly one `<!-- canonical-pr-change-r
 ```bash
 agent-infra-internal platform-pr summary-sync {task-id} \
   --agent {standard-agent-token} --body-file {summary-body-file} \
-  --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json \
+  --change-report-file <task-workspace>/active/{task-id}/pr-change-report.json \
   --result {primary-result}
 ```
 

package/templates/.agents/skills/create-pr/reference/comment-publish.zh-CN.md

@@ -7,7 +7,7 @@
 ```bash
 agent-infra-internal platform-pr summary-sync {task-id} \
   --agent {standard-agent-token} --body-file {summary-body-file} \
-  --change-report-file .agents/workspace/active/{task-id}/pr-change-report.json \
+  --change-report-file <task-workspace>/active/{task-id}/pr-change-report.json \
   --result {primary-result}
 ```
 

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

@@ -118,10 +118,10 @@ If no historical release notes exist, use the following default Markdown format:
      - Issue reporters from typed `closingIssues[].author`
    - **Contribution count**: `PR count + co-authored commit count` for the same identity, merged across both sources
    - **`@login` mapping**: follow the identity safety boundary in `.agents/rules/release-commands.md`
-     - For `platform-user` or `platform-noreply` with a non-empty `login`, use the lowercased `login`
+     - For `platform-user` or `platform-noreply` with a non-empty `login`, follow the mention mapping in `.agents/rules/release-commands.md`
      - Exclude `unresolved` identities from the contributor list; never infer a login from a name, email address, domain, brand, or same-named platform account
      - Merge all Name variants carrying the same typed login before counting and sorting
-     - Preserve bot identities as-is, for example `dependabot[bot]`
+     - Use plain-text `@login` mentions in Release notes, without Markdown links; map Dependabot typed logins to `@dependabot` according to the rule
      - Do not add unresolved identity emails, placeholder mentions, or identity-verification TODOs to publishable notes
    - **Sorting**: descending by contribution count, then lexicographically by login for ties
    - **Deduplication**: use the final mapped `@login` as the key

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

@@ -118,10 +118,10 @@ agent-infra-internal platform-release-notes context \
      - Issue reporters：来自步骤 3 typed context 的 `closingIssues[].author`
    - **贡献数定义**：`该人的 PR 数 + 该人作为 co-author 的 commit 数`（同一身份跨来源合并计数）
    - **`@login` 映射**：遵循 `.agents/rules/release-commands.md` 的身份安全边界
-     - `resolution` 为 `platform-user` 或 `platform-noreply` 且 `login` 非空时，采用小写 `login`
+     - `resolution` 为 `platform-user` 或 `platform-noreply` 且 `login` 非空时，遵循 `.agents/rules/release-commands.md` 的 mention 映射
      - `resolution` 为 `unresolved` 时从贡献者列表中排除；不得从 Name、邮箱、域名、品牌或同名平台账号推断 login
      - 同一 typed login 的所有 Name 变体必须归并后再计数与排序
-     - Bot 身份保留原样（如 `dependabot[bot]`）
+     - Release notes 的 `@login` 一律使用纯文本，不用 Markdown 链接包装；Dependabot typed login 按规则映射为 `@dependabot`
      - 不得在可发布 notes 中加入未解析身份的邮箱、占位 mention 或身份确认 TODO
    - **排序**：按贡献数降序；贡献数相同时按 login 字典序
    - **去重**：以最终映射后的 `@login` 为键

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

@@ -180,7 +180,7 @@ Task information:
 - Issue: #{issue-number} {issue_url}
 
 Output file:
-- Task file: .agents/workspace/active/{task-id}/task.md
+- Task file: <task-workspace>/active/{task-id}/task.md
 
 Next step - run requirements analysis:
 {next-step-commands}
@@ -199,7 +199,7 @@ Task information:
 - Workflow: {workflow}
 
 Output file:
-- Task file: .agents/workspace/active/{task-id}/task.md
+- Task file: <task-workspace>/active/{task-id}/task.md
 
 Next step - run requirements analysis:
 {next-step-commands}
@@ -223,7 +223,7 @@ Issue creation failed:
 - Local task.md was kept and not rolled back
 
 Output file:
-- Task file: .agents/workspace/active/{task-id}/task.md
+- Task file: <task-workspace>/active/{task-id}/task.md
 
 Next step - run requirements analysis:
 {next-step-commands}
@@ -239,7 +239,7 @@ For later platform sync: after fixing auth / network / template issues, manually
 ## Completion Checklist
 
 - [ ] Wrote one candidate and invoked `agent-infra-internal task-create`
-- [ ] The host created `.agents/workspace/active/{task-id}/task.md`
+- [ ] The host created `<task-workspace>/active/{task-id}/task.md`
 - [ ] Wrote and checked `## Task Input` source and state semantics according to `reference/context-capture.md`
 - [ ] The returned task id and short id passed completion verification
 - [ ] Tried cascading Issue creation through `.agents/rules/create-issue.md`; if it failed, kept task.md and recorded the reason

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

@@ -177,7 +177,7 @@ agent-infra-internal task-verify {task-id} create-task.completed --format text
 - Issue：#{issue-number} {issue_url}
 
 产出文件：
-- 任务文件：.agents/workspace/active/{task-id}/task.md
+- 任务文件：<task-workspace>/active/{task-id}/task.md
 
 下一步 - 执行需求分析：
 {next-step-commands}
@@ -196,7 +196,7 @@ agent-infra-internal task-verify {task-id} create-task.completed --format text
 - 工作流：{workflow}
 
 产出文件：
-- 任务文件：.agents/workspace/active/{task-id}/task.md
+- 任务文件：<task-workspace>/active/{task-id}/task.md
 
 下一步 - 执行需求分析：
 {next-step-commands}
@@ -220,7 +220,7 @@ Issue 创建失败：
 - 本地 task.md 已保留，未回滚
 
 产出文件：
-- 任务文件：.agents/workspace/active/{task-id}/task.md
+- 任务文件：<task-workspace>/active/{task-id}/task.md
 
 下一步 - 执行需求分析：
 {next-step-commands}
@@ -236,7 +236,7 @@ Issue 创建失败：
 ## 完成检查清单
 
 - [ ] 只生成一次结构化 candidate 并调用 `agent-infra-internal task-create`
-- [ ] 宿主创建了任务文件 `.agents/workspace/active/{task-id}/task.md`
+- [ ] 宿主创建了任务文件 `<task-workspace>/active/{task-id}/task.md`
 - [ ] 已按 `reference/context-capture.md` 写入并复核 `## 任务输入` 的来源与状态语义
 - [ ] 响应中的任务 ID 和短号已通过完成校验
 - [ ] 已按 `.agents/rules/create-issue.md` 尝试级联创建 Issue；失败时保留 task.md 并记录原因

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

@@ -18,7 +18,6 @@
       "expected_status": "active"
     },
     "activity-log": {
-      "expected_action_pattern": "(Create Task|Task Created)"
     },
     "platform-sync": {
       "when": "platform_issue_identity_exists",

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

@@ -48,7 +48,7 @@ Extract key information:
 
 Check whether a task for this alert already exists. If not, create one:
 
-Directory: `.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+Directory: `<task-workspace>/active/TASK-{yyyyMMdd-HHmmss}/`
 
 Task metadata:
 ```yaml

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

@@ -48,7 +48,7 @@ description: >
 
 检查是否已存在该告警的任务。如果不存在，创建：
 
-目录：`.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+目录：`<task-workspace>/active/TASK-{yyyyMMdd-HHmmss}/`
 
 任务元数据：
 ```yaml

package/templates/.agents/skills/import-codescan/config/verify.json

@@ -17,7 +17,6 @@
       "expected_status": "active"
     },
     "activity-log": {
-      "expected_action_pattern": "(Import Codescan|Import Code Scanning Alert)"
     },
     "platform-sync": null
   }

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

@@ -45,11 +45,11 @@ Extract key information:
 
 ### 2. Create the Task Directory and File
 
-Check whether `.agents/workspace/active/` already has a task for this alert.
+Check whether `<task-workspace>/active/` already has a task for this alert.
 - If found, **reuse the existing task by default**; do not ask the user. State clearly in the final notice: "Reused existing task `{task-id}`; not re-imported." If the user wants to re-import, they must first archive or delete the existing task
 - If not found, create a new task
 
-Create directory: `.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+Create directory: `<task-workspace>/active/TASK-{yyyyMMdd-HHmmss}/`
 
 Task metadata must include:
 ```yaml
@@ -118,7 +118,7 @@ Task information:
 - Task ID: {task-id} (short id {task-ref})
 
 Output file:
-- Task file: .agents/workspace/active/{task-id}/task.md
+- Task file: <task-workspace>/active/{task-id}/task.md
 
 Next step:
 {next-step-commands}

package/templates/.agents/skills/import-dependabot/SKILL.zh-CN.md

@@ -45,11 +45,11 @@ description: >
 
 ### 2. 创建任务目录和文件
 
-检查 `.agents/workspace/active/` 中是否已存在该告警的任务。
+检查 `<task-workspace>/active/` 中是否已存在该告警的任务。
 - 如果找到，**默认复用现有任务**，不询问用户；在最终告知中明确「已复用现有任务 `{task-id}`，未重新导入」。如需重新导入，需先归档/删除已有任务
 - 如果未找到，创建新任务
 
-创建目录：`.agents/workspace/active/TASK-{yyyyMMdd-HHmmss}/`
+创建目录：`<task-workspace>/active/TASK-{yyyyMMdd-HHmmss}/`
 
 任务元数据需包含：
 ```yaml
@@ -116,7 +116,7 @@ agent-infra-internal task-verify {task-id} import-dependabot.completed --format
 - 任务 ID：{task-id}（短号 {task-ref}）
 
 产出文件：
-- 任务文件：.agents/workspace/active/{task-id}/task.md
+- 任务文件：<task-workspace>/active/{task-id}/task.md
 
 下一步：
 {next-step-commands}

package/templates/.agents/skills/import-dependabot/config/verify.json

@@ -17,7 +17,6 @@
       "expected_status": "active"
     },
     "activity-log": {
-      "expected_action_pattern": "(Import Dependabot|Import Dependabot Alert)"
     },
     "platform-sync": null
   }

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

@@ -63,7 +63,7 @@ Strip only the first layer, and only when the leading token is a `prefix-types`
 
 ### 2. Check for an Existing Task
 
-2.1 Search `.agents/workspace/active/` for an existing task linked to this Issue.
+2.1 Search `<task-workspace>/active/` for an existing task linked to this Issue.
 - If found, **reuse the existing task by default** (Scenario A); do not ask the user. State clearly in the final notice: "Reused existing task `{task-id}`; not re-imported." If the user wants to re-import, they must first archive or delete the existing task and run this skill again
 - If not found, continue to 2.2
 
@@ -93,7 +93,7 @@ date +%Y%m%d-%H%M%S
 
 3.2 Write the task directory and `task.md`.
 
-- Create the directory: `.agents/workspace/active/{task-id}/`
+- Create the directory: `<task-workspace>/active/{task-id}/`
 - Use the `.agents/templates/task.md` template to create `task.md`
 - For Scenario C, prefer `type`, `workflow`, `branch`, and `milestone` from the remote frontmatter; infer missing or damaged fields from Issue labels and current rules
 - Always write `current_step` as `requirement-analysis`; do not restore the remote original `current_step`
@@ -132,7 +132,7 @@ Get the current time:
 date "+%Y-%m-%d %H:%M:%S%z" | sed 's/\([+-][0-9][0-9]\)\([0-9][0-9]\)$/\1:\2/'
 ```
 
-Update `.agents/workspace/active/{task-id}/task.md`:
+Update `<task-workspace>/active/{task-id}/task.md`:
 - `current_step`: requirement-analysis
 - `assigned_to`: {current AI agent}
 - `updated_at`: {current time}
@@ -193,7 +193,7 @@ Task information:
 - Workflow: {workflow}
 
 Output file:
-- Task file: .agents/workspace/active/{task-id}/task.md
+- Task file: <task-workspace>/active/{task-id}/task.md
 
 Next step - run requirements analysis:
 {next-step-commands}
@@ -203,7 +203,7 @@ Next step - run requirements analysis:
 
 ## Completion Checklist
 
-- [ ] Created the task file `.agents/workspace/active/{task-id}/task.md`
+- [ ] Created the task file `<task-workspace>/active/{task-id}/task.md`
 - [ ] Provider wrote the Issue identity to `platform_issue_identity` in task.md
 - [ ] Updated `current_step` to requirement-analysis
 - [ ] Updated `updated_at` to the current time