@fitlab-ai/agent-infra 0.11.15 → 0.12.0

package/templates/.agents/rules/release-commands.en.md

@@ -19,6 +19,9 @@ The result contains `history`, `pullRequests`, `closingIssues`, and commit `auth
 - Render an identity as `@login` only when `resolution` is `platform-user` or `platform-noreply` and `login` is non-empty.
 - Exclude `resolution: unresolved` identities from the release-note contributor list. Never infer a login from a name, email address, domain, brand, or same-named platform account, and never substitute a guessed personal or organization account.
 - Do not publish unresolved identity emails or identity-verification TODOs in Release notes. Record any required investigation outside the release workflow without creating a platform mention.
+- Use plain-text `@login` mentions in Release notes; do not wrap mentions in Markdown links.
+- **Dependabot-specific normalization**: Typed context may return the same Dependabot automation account as `app/dependabot` or `dependabot[bot]`. For these resolved identities, render release-note items and Contributors as plain-text `@dependabot`, and merge counts under the normalized `@dependabot`. Do not output `@app/dependabot` or `@dependabot[bot]`, and do not turn `@dependabot` into a Markdown link.
+- This Dependabot mapping is an explicit exception for this project's Release notes. Use the typed `login` for all other identities; do not infer mappings from brands or similar names.
 
 ## Stage Release Notes
 

package/templates/.agents/rules/release-commands.zh-CN.md

@@ -19,6 +19,9 @@ agent-infra-internal platform-release-notes context \
 - 只有 `resolution` 为 `platform-user` 或 `platform-noreply` 且 `login` 非空的身份可以渲染为 `@login`。
 - `resolution: unresolved` 的身份不得进入发布说明的贡献者列表；不得从 Name、邮箱、域名、品牌或同名平台账号推断 login，也不得替换成推测的个人或组织账号。
 - 不得把未解析身份的邮箱或身份确认 TODO 写入可发布的 Release notes。需要调查时仅在发布流程外记录，不得产生平台 mention。
+- Release notes 中的 mention 使用纯文本 `@login`，不要用 Markdown 链接包装 mention。
+- **Dependabot 专用规范化**：typed context 可能将同一 Dependabot 自动化账号返回为 `app/dependabot` 或 `dependabot[bot]`。对于 `resolution` 已解析的这些身份，发布说明条目和 Contributors 统一使用纯文本 `@dependabot`；按规范化后的 `@dependabot` 合并计数。不要输出 `@app/dependabot` 或 `@dependabot[bot]`，也不要把 `@dependabot` 改成 Markdown 链接。
+- 该 Dependabot 映射是本项目发布说明的明确例外；其他身份继续使用 typed `login`，不得按品牌或相似名称类推。
 
 ## Stage Release notes
 

package/templates/.agents/rules/task-management.en.md

@@ -86,8 +86,6 @@ Other skills continue past deferrable writes according to their local delivery g
 
 **Human counts** (`ai task log`): review step rows fold two human counts into the NOTE verdict text, comma-separated, right after `blockers/major/minor`, with fixed English labels `Manual-validation: {e}, Human-decision: {h}`. `Human-decision` (`{h}`) maps canonical step prefixes (`Review Analysis` / `Review Plan` / `Review Code`) to `analysis` / `plan` / `code`, then counts current pending rows in `## Review Disagreement Ledger` / `## 审查分歧账本` for that stage with `status = needs-human-decision`, excluding rows already marked `human-decided`. `Manual-validation` (`{e}`) parses the `Manual-validation: {n}` source field from the review done note (normalized to the same field when displayed), defaulting to `0`. Non-review rows carry no human counts.
 
-**Gate** (`checkActivityLog`): when computing the "latest action / freshness" it skips `[started]` lines (ascending-order and format checks still cover every line), so a started marker never satisfies a skill's `expected_action_pattern`.
-
 **Skills that write started**: every workflow skill that **appends entries to a task's `## Activity Log`** writes started, so the STARTED column stays uniformly complete across the whole `ai task log` table. Two forms, depending on whether task.md already exists:
 
 - **Standard form (task.md already exists)** — append the started line when that round's real work begins (after prerequisites, before the first artifact action) and the done line on completion:

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

@@ -89,8 +89,6 @@
 
 **人工计数**（`ai task log`）：审查步骤行把两项人工计数并入 NOTE 的 verdict 文本，逗号分隔、紧随 `blockers/major/minor`，固定英文标签 `Manual-validation: {e}, Human-decision: {h}`。`Human-decision`（`{h}`）按 canonical 步骤名前缀（`Review Analysis` / `Review Plan` / `Review Code`）映射到 `analysis` / `plan` / `code`，统计 `## 审查分歧账本` 中对应阶段 `status = needs-human-decision` 的当前待裁决数量，不包含已 `human-decided` 的行；`Manual-validation`（`{e}`）解析 review done note 中的 `Manual-validation: {n}` 源字段（展示时归一化为同一字段），缺失为 `0`。非审查步骤不附加人工计数。
 
-**gate**（`checkActivityLog`）：计算「最新 action / freshness」时跳过 `[started]` 行（升序与格式校验仍覆盖全部行），故 started 标记不会污染各 SKILL 的 `expected_action_pattern`。
-
 **写 started 的 SKILL**：所有**会向某个任务的 `## 活动日志` 追加条目**的工作流 SKILL 都写 started，保证 `ai task log` 整张表的 STARTED 列一致完整。两种写法按技能是否已有 task.md 区分：
 
 - **常规写法（task.md 已存在）**——在「该轮实质工作开始时」（前置条件确认后、第一个产出动作前）追加 started 行，完成时写 done 行：

package/templates/.agents/rules/task-short-id.en.md

@@ -87,9 +87,9 @@ fi
 ## Storage
 
 Short ids are pure local state, persisted only in the registry
-`.agents/workspace/active/.short-ids.json`; task.md does not hold the short id:
+`<task-workspace>/active/.short-ids.json`; task.md does not hold the short id:
 
-- Path: `<repo-root>/.agents/workspace/active/.short-ids.json`
+- Path: `<task-workspace>/active/.short-ids.json`
 - Schema: `{ "version": 1, "ids": { "01": "TASK-20260609-192644", "02": "TASK-…" } }`
 - Keys are zero-padded decimal strings of `task.shortIdLength` digits; values are
   full `TASK-…` task ids.

package/templates/.agents/rules/task-short-id.zh-CN.md

@@ -75,9 +75,9 @@ fi
 
 ## 存储位置
 
-短号是纯本地状态，唯一持久化在注册表 `.agents/workspace/active/.short-ids.json`，task.md 不持有短号：
+短号是纯本地状态，唯一持久化在注册表 `<task-workspace>/active/.short-ids.json`，task.md 不持有短号：
 
-- 路径：`<repo-root>/.agents/workspace/active/.short-ids.json`
+- 路径：`<task-workspace>/active/.short-ids.json`
 - Schema：`{ "version": 1, "ids": { "01": "TASK-20260609-192644", "02": "TASK-…" } }`
 - key 是零填充到 `task.shortIdLength` 位的字符串，value 是完整 `TASK-…` task id
 - 自动 git ignore（active 工作区整体 ignore；无需新增 ignore 条目）

package/templates/.agents/scripts/task-short-id.js

@@ -57,22 +57,16 @@ if (args.includes("--help") || args.includes("-h")) {
 }
 const repoRoot = findRepoRoot(process.cwd());
 const forwarded = [...args];
-if (!forwarded.includes("--active-dir")) {
-  if (!repoRoot) {
-    fs.writeSync(2, "Error: cannot determine active task directory\n");
-    process.exit(1);
-  }
-  forwarded.push("--active-dir", path.join(repoRoot, ".agents", "workspace", "active"));
-}
 if (!forwarded.includes("--short-id-length")) {
   forwarded.push("--short-id-length", String(configuredWidth(repoRoot)));
 }
 const sourceCli = findSourceCli();
 const installedCli = resolveCommand("agent-infra-internal");
 const child = sourceCli
-  ? spawnSync(process.execPath, ["--experimental-strip-types", sourceCli, "task-short-id", ...forwarded], { encoding: "utf8" })
+  ? spawnSync(process.execPath, ["--experimental-strip-types", sourceCli, "task-short-id", ...forwarded], { cwd: repoRoot || process.cwd(), encoding: "utf8" })
   : spawnSync(installedCli, ["task-short-id", ...forwarded], {
       encoding: "utf8",
+      cwd: repoRoot || process.cwd(),
       shell: process.platform === "win32" && /\.(?:bat|cmd)$/i.test(installedCli)
     });
 if (child.error) {

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

@@ -57,7 +57,7 @@ After resolving the artifact context and before this round's first artifact acti
 ### 1. Verify Prerequisites
 
 Check required files:
-- `.agents/workspace/active/{task-id}/task.md` - Task file
+- `<task-workspace>/active/{task-id}/task.md` - Task file
 
 Note: `{task-id}` format is `TASK-{yyyyMMdd-HHmmss}`, for example `TASK-20260306-143022`
 
@@ -119,7 +119,7 @@ Runs after Step 0 state check and Step 3 (questioning is an external-state actio
      - otherwise (no pending question) → pick the single highest-value question (acceptance criteria > scope > ambiguity) and write `## Brainstorming`: `status: asking`, `pending_question: <question>`, `question_count += 1`.
   2. If `start_date` is empty, write today (`date +%F`), then run `agent-infra-internal task-event {task-id} analyze.awaiting-input --agent {standard-agent-token} --question {question_count}` so the core updates base metadata and Activity Log.
   3. Issue sync (when a valid `platform_issue_identity` exists, skip on any failure): run `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}` to update only the **task comment**; keep the `status` label at `pending-design-work`; do **not** publish an analysis artifact comment.
-  4. Verification (replaces the step 8 artifact gate): `agent-infra-internal task-verify {task-id} analyze.awaiting-input --format text` (the early-exit set `current_step: requirement-analysis` and wrote `start_date`, so it should pass); also keep `rg -n 'Analyze Task \(Brainstorming\)' .agents/workspace/active/{task-id}/task.md` and the task-comment sync evidence. Do **not** run the artifact gate, nor `check activity-log` / `check platform-sync` (both bind to the analysis artifact path).
+  4. Verification (replaces the step 8 artifact gate): `agent-infra-internal task-verify {task-id} analyze.awaiting-input --format text` (the early-exit set `current_step: requirement-analysis` and wrote `start_date`, so it should pass); also keep `rg -n 'Analyze Task \(Brainstorming\)' <task-workspace>/active/{task-id}/task.md` and the task-comment sync evidence. Do **not** run the artifact gate, nor `check activity-log` / `check platform-sync` (both bind to the analysis artifact path).
   5. User output: show only the current **single question** plus how to answer/continue (re-trigger `analyze-task {task-ref}` with the answer).
   6. **STOP** and wait for the answer. The next trigger returns to this step.
 
@@ -148,7 +148,7 @@ The skeleton contains identity metadata, stable section markers, and required he
 
 > Steps 6–9 are the **Scenario A (normal output)** path. **Scenario B (ask and early-exit)** already finished its state update, task-comment sync, and verification inside step 4 and STOPped, so it does not enter these steps.
 
-Create `.agents/workspace/active/{task-id}/{analysis-artifact}`.
+Create `<task-workspace>/active/{task-id}/{analysis-artifact}`.
 
 ## Output Template
 
@@ -221,7 +221,7 @@ Create `.agents/workspace/active/{task-id}/{analysis-artifact}`.
 
 ### 7. Update Task Status
 
-Update `.agents/workspace/active/{task-id}/task.md`:
+Update `<task-workspace>/active/{task-id}/task.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
@@ -290,7 +290,7 @@ Summary:
 - Risk level: {assessment}
 
 Output file:
-- Analysis report: .agents/workspace/active/{task-id}/{analysis-artifact}
+- Analysis report: <task-workspace>/active/{task-id}/{analysis-artifact}
 
 Next step - continue on the selected path:
 {next-step-commands}
@@ -299,7 +299,7 @@ Next step - continue on the selected path:
 ## Completion Checklist
 
 - [ ] Read and understood the task file and source information
-- [ ] Created analysis document `.agents/workspace/active/{task-id}/{analysis-artifact}`
+- [ ] Created analysis document `<task-workspace>/active/{task-id}/{analysis-artifact}`
 - [ ] Updated `current_step` to requirement-analysis in task.md
 - [ ] Updated `updated_at` to the current time in task.md
 - [ ] Updated `assigned_to` in task.md

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

@@ -60,7 +60,7 @@ agent-infra-internal task-event {task-id} analyze.started --agent {standard-agen
 ### 1. 验证前置条件
 
 检查必要文件：
-- `.agents/workspace/active/{task-id}/task.md` - 任务文件
+- `<task-workspace>/active/{task-id}/task.md` - 任务文件
 
 注意：`{task-id}` 格式为 `TASK-{yyyyMMdd-HHmmss}`，例如 `TASK-20260306-143022`
 
@@ -122,7 +122,7 @@ agent-infra-internal task-event {task-id} analyze.started --agent {standard-agen
      - 否则（无待答问题）→ 选最高价值的一个问题（验收标准 > 范围 > 歧义），写入 `## Brainstorming`：`status: asking`、`pending_question: <问题>`、`question_count += 1`。
   2. 若 `start_date` 为空，写入当日日期（`date +%F`）；随后执行 `agent-infra-internal task-event {task-id} analyze.awaiting-input --agent {standard-agent-token} --question {question_count}`，由核心统一更新基础 frontmatter 和 Activity Log。
   3. Issue 同步（存在有效 `platform_issue_identity` 时，任一失败跳过）：调用 `agent-infra-internal platform-comment sync {task-id} --kind task --agent {standard-agent-token}` 更新 **task 评论**；`status` label 维持 `pending-design-work`；**不**发布分析产物评论。
-  4. 校验（替代步骤 8 的 artifact gate）：`agent-infra-internal task-verify {task-id} analyze.awaiting-input --format text`（早退已置 `current_step: requirement-analysis` 且已写入 `start_date`，预期通过）；并保留 `rg -n 'Analyze Task \(Brainstorming\)' .agents/workspace/active/{task-id}/task.md` 与 task 评论同步证据。**不**跑 artifact gate，也不跑 `check activity-log` / `check platform-sync`（二者绑定分析产物路径）。
+  4. 校验（替代步骤 8 的 artifact gate）：`agent-infra-internal task-verify {task-id} analyze.awaiting-input --format text`（早退已置 `current_step: requirement-analysis` 且已写入 `start_date`，预期通过）；并保留 `rg -n 'Analyze Task \(Brainstorming\)' <task-workspace>/active/{task-id}/task.md` 与 task 评论同步证据。**不**跑 artifact gate，也不跑 `check activity-log` / `check platform-sync`（二者绑定分析产物路径）。
   5. 用户输出：只展示当前**单个问题** + 如何回答/继续（再次触发 `analyze-task {task-ref}` 并附答案）。
   6. **STOP**，等待回答。下一次触发回到本步骤。
 
@@ -151,7 +151,7 @@ agent-infra-internal task-artifact {task-id} init --family analysis --artifact {
 
 > 步骤 6–9 属**场景 A（正常产出）**路径。**场景 B（提问早退）**已在步骤 4 内完成状态更新、task 评论同步与校验并 STOP，不进入这些步骤。
 
-创建 `.agents/workspace/active/{task-id}/{analysis-artifact}`。
+创建 `<task-workspace>/active/{task-id}/{analysis-artifact}`。
 
 ## 输出模板
 
@@ -228,7 +228,7 @@ agent-infra-internal task-artifact {task-id} init --family analysis --artifact {
 
 ### 7. 更新任务状态
 
-更新 `.agents/workspace/active/{task-id}/task.md`：
+更新 `<task-workspace>/active/{task-id}/task.md`：
 - 仅更新优先级、Brainstorming、审查响应等本技能拥有的业务内容；产物链接、阶段与完成日志由 completed 事件统一登记
 - 在追加工作流 Activity Log 条目之前，基于分析结果（业务影响、风险、依赖、阻塞条件）重估 `priority`。若重估值与 `task.md` 当前值不一致：
   - 用新值覆盖 frontmatter 的 `priority` 字段
@@ -288,7 +288,7 @@ agent-infra-internal task-verify {task-id} analyze.completed --artifact {analysi
 - 风险等级：{评估}
 
 产出文件：
-- 分析报告：.agents/workspace/active/{task-id}/{analysis-artifact}
+- 分析报告：<task-workspace>/active/{task-id}/{analysis-artifact}
 
 下一步 - 按所选路径继续：
 {next-step-commands}
@@ -297,7 +297,7 @@ agent-infra-internal task-verify {task-id} analyze.completed --artifact {analysi
 ## 完成检查清单
 
 - [ ] 阅读并理解了任务文件和来源信息
-- [ ] 创建了分析文档 `.agents/workspace/active/{task-id}/{analysis-artifact}`
+- [ ] 创建了分析文档 `<task-workspace>/active/{task-id}/{analysis-artifact}`
 - [ ] 更新了 task.md 中的 `current_step` 为 requirement-analysis
 - [ ] 更新了 task.md 中的 `updated_at` 为当前时间
 - [ ] 更新了 task.md 中的 `assigned_to`

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

@@ -21,7 +21,6 @@
       "schema": "analysis"
     },
     "activity-log": {
-      "expected_action_pattern": "(Analyze Task|Requirement Analysis) \\(Round \\d+\\)"
     },
     "platform-sync": {
       "when": "platform_issue_identity_exists"

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

@@ -21,7 +21,6 @@
       "schema": "analysis"
     },
     "activity-log": {
-      "expected_action_pattern": "(Analyze Task|Requirement Analysis) \\(Round \\d+\\)"
     },
     "platform-sync": {
       "when": "platform_issue_identity_exists"

package/templates/.agents/skills/archive-tasks/SKILL.en.md

@@ -7,16 +7,16 @@ description: >
 
 # Archive Completed Tasks
 
-Archive completed tasks from `.agents/workspace/completed/` into `.agents/workspace/archive/YYYY/MM/DD/TASK-xxx/local/` and rebuild a three-level archive index. Local task materials live in `local/` with a path-sorted `contents.sha256`; the TASK root contains no ordinary files.
-- root manifest: `.agents/workspace/archive/manifest.md`
-- yearly manifest: `.agents/workspace/archive/YYYY/manifest.md`
-- monthly manifest: `.agents/workspace/archive/YYYY/MM/manifest.md`
+Archive completed tasks from `<task-workspace>/completed/` into `<task-workspace>/archive/YYYY/MM/DD/TASK-xxx/local/` and rebuild a three-level archive index. Local task materials live in `local/` with a path-sorted `contents.sha256`; the TASK root contains no ordinary files.
+- root manifest: `<task-workspace>/archive/manifest.md`
+- yearly manifest: `<task-workspace>/archive/YYYY/manifest.md`
+- monthly manifest: `<task-workspace>/archive/YYYY/MM/manifest.md`
 
 ## Execution Flow
 
 ### 1. Verify the environment
 
-Confirm that `.agents/workspace/completed/` exists, then choose one of these four invocation modes:
+Confirm that `<task-workspace>/completed/` exists, then choose one of these four invocation modes:
 - no arguments: archive every completed task
 - `--days N`: keep the most recent `N` days and archive older tasks
 - `--before YYYY-MM-DD`: archive only tasks completed before the given date

package/templates/.agents/skills/archive-tasks/SKILL.zh-CN.md

@@ -7,16 +7,16 @@ description: >
 
 # 归档已完成任务
 
-将 `.agents/workspace/completed/` 中的已完成任务归档到 `.agents/workspace/archive/YYYY/MM/DD/TASK-xxx/local/`，并重建三级归档索引。TASK 本地材料位于 `local/`，含按路径排序的 `contents.sha256`；TASK 根目录不存放普通文件。
-- 根 manifest：`.agents/workspace/archive/manifest.md`
-- 年 manifest：`.agents/workspace/archive/YYYY/manifest.md`
-- 月 manifest：`.agents/workspace/archive/YYYY/MM/manifest.md`
+将 `<task-workspace>/completed/` 中的已完成任务归档到 `<task-workspace>/archive/YYYY/MM/DD/TASK-xxx/local/`，并重建三级归档索引。TASK 本地材料位于 `local/`，含按路径排序的 `contents.sha256`；TASK 根目录不存放普通文件。
+- 根 manifest：`<task-workspace>/archive/manifest.md`
+- 年 manifest：`<task-workspace>/archive/YYYY/manifest.md`
+- 月 manifest：`<task-workspace>/archive/YYYY/MM/manifest.md`
 
 ## 执行流程
 
 ### 1. 验证环境
 
-确认 `.agents/workspace/completed/` 存在，并根据用户输入选择以下四种调用方式之一：
+确认 `<task-workspace>/completed/` 存在，并根据用户输入选择以下四种调用方式之一：
 - 无参数：归档全部已完成任务
 - `--days N`：保留最近 `N` 天，仅归档更早的任务
 - `--before YYYY-MM-DD`：仅归档指定日期之前的任务

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

@@ -4,7 +4,15 @@ set -e
 
 SCRIPT_DIR=$(CDPATH= cd "$(dirname "$0")" && pwd)
 REPO_ROOT=$(CDPATH= cd "$SCRIPT_DIR/../../../.." && pwd)
-WORKSPACE_ROOT="$REPO_ROOT/.agents/workspace"
+if [ -f "$REPO_ROOT/bin/internal-cli.sh" ]; then
+  WORKSPACE_RESULT=$(CDPATH= cd "$REPO_ROOT" && sh "$REPO_ROOT/bin/internal-cli.sh" task-workspace resolve --boundary host)
+elif command -v agent-infra-internal >/dev/null 2>&1; then
+  WORKSPACE_RESULT=$(CDPATH= cd "$REPO_ROOT" && agent-infra-internal task-workspace resolve --boundary host)
+else
+  printf 'archive-tasks: agent-infra-internal task-workspace resolver is unavailable\n' >&2
+  exit 1
+fi
+WORKSPACE_ROOT=$(printf '%s' "$WORKSPACE_RESULT" | node -e 'let input="";process.stdin.setEncoding("utf8");process.stdin.on("data",chunk=>input+=chunk);process.stdin.on("end",()=>{const result=JSON.parse(input);if(result.status!=="resolved"||typeof result.root!=="string")process.exit(1);process.stdout.write(result.root);});')
 COMPLETED_DIR="$WORKSPACE_ROOT/completed"
 ARCHIVE_DIR="$WORKSPACE_ROOT/archive"
 MANIFEST_PATH="$ARCHIVE_DIR/manifest.md"
@@ -586,4 +594,4 @@ echo
 echo "Summary:"
 printf -- '- Archived: %s\n' "$archived_count"
 printf -- '- Skipped: %s\n' "$skipped_count"
-printf -- '- Manifest: %s\n' ".agents/workspace/archive/manifest.md"
+printf -- '- Manifest: %s\n' "$ARCHIVE_DIR/manifest.md"

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

@@ -38,7 +38,7 @@ After prerequisites pass, Step 3 declares one lifecycle intent that atomically w
 
 ### 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`
 
@@ -68,7 +68,7 @@ Confirm `targetState=blocked`, the target path, and the committed short-id effec
 ### 5. Preserve Recovery Identity
 
 ```bash
-ls .agents/workspace/blocked/{task-id}/task.md
+ls <task-workspace>/blocked/{task-id}/task.md
 ```
 
 ### 6. Sync to Issue (Optional)
@@ -111,7 +111,7 @@ Task {task-id} marked as blocked.
 
 Blocking reason: {summary}
 Required to unblock: {what's needed}
-Archived to: .agents/workspace/blocked/{task-id}/
+Archived to: <task-workspace>/blocked/{task-id}/
 
 Optional: clean up this task's sandbox
 (The task is blocked and moved to blocked/; task-bound sandboxes are protected from automatic `ai sandbox rm --unbound` cleanup. If cleanup is necessary, manually verify the container, control manifest, and worktree identity first.)
@@ -129,7 +129,7 @@ Next step - check task status after unblocking:
 
 - [ ] Analyzed and documented the blocking reason
 - [ ] Updated task.md with blocked status and blocking information
-- [ ] Moved task directory to `.agents/workspace/blocked/`
+- [ ] Moved task directory to `<task-workspace>/blocked/`
 - [ ] Verified move succeeded
 - [ ] Informed user how to unblock
 

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

@@ -37,7 +37,7 @@ description: >
 ## 执行步骤
 ### 1. 验证任务存在
 
-检查任务是否存在于 `.agents/workspace/active/{task-id}/`。
+检查任务是否存在于 `<task-workspace>/active/{task-id}/`。
 
 注意：`{task-id}` 格式为 `TASK-{yyyyMMdd-HHmmss}`，例如 `TASK-20260306-143022`
 
@@ -62,10 +62,10 @@ agent-infra-internal task-lifecycle {task-id} block --agent {standard-agent-toke
 
 ### 4. 验证本地终态
 
-确认结构化结果的 `targetState=blocked`、目标路径为 `.agents/workspace/blocked/{task-id}`、短号效果已提交，并检查：
+确认结构化结果的 `targetState=blocked`、目标路径为 `<task-workspace>/blocked/{task-id}`、短号效果已提交，并检查：
 
 ```bash
-ls .agents/workspace/blocked/{task-id}/task.md
+ls <task-workspace>/blocked/{task-id}/task.md
 ```
 
 ### 5. 保留恢复身份
@@ -110,7 +110,7 @@ agent-infra-internal task-verify {task-id} block-task.completed --format text
 
 阻塞原因：{摘要}
 解除阻塞所需：{需要什么}
-归档路径：.agents/workspace/blocked/{task-id}/
+归档路径：<task-workspace>/blocked/{task-id}/
 
 可选：清理本任务的沙箱
 （任务已阻塞并移到 blocked/，task-bound 沙箱受保护，不会被 `ai sandbox rm --unbound` 自动删除；如确需清理，请先人工核对容器、控制清单和工作树身份。）
@@ -128,7 +128,7 @@ agent-infra-internal task-verify {task-id} block-task.completed --format text
 
 - [ ] 分析并记录了阻塞原因
 - [ ] 更新了 task.md 的阻塞状态和阻塞信息
-- [ ] 将任务目录移动到 `.agents/workspace/blocked/`
+- [ ] 将任务目录移动到 `<task-workspace>/blocked/`
 - [ ] 验证了移动成功
 - [ ] 告知了用户如何解除阻塞
 

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

@@ -18,7 +18,6 @@
       "require_blocked_at": true
     },
     "activity-log": {
-      "expected_action_pattern": "(Block Task|Blocked)"
     },
     "platform-sync": {
       "when": "platform_issue_identity_exists"

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

@@ -33,9 +33,9 @@ After prerequisites pass, Step 3 declares one lifecycle intent that atomically c
 ### 1. Verify Task Exists
 
 Check these directories in order:
-- `.agents/workspace/active/{task-id}/`
-- `.agents/workspace/blocked/{task-id}/`
-- `.agents/workspace/completed/{task-id}/`
+- `<task-workspace>/active/{task-id}/`
+- `<task-workspace>/blocked/{task-id}/`
+- `<task-workspace>/completed/{task-id}/`
 
 Handling rules:
 - If found in `active/` or `blocked/`: continue
@@ -69,7 +69,7 @@ Confirm `targetState=completed`, terminal fields, and the short-id effect from t
 ### 5. Verify the Move
 
 ```bash
-ls .agents/workspace/completed/{task-id}/task.md
+ls <task-workspace>/completed/{task-id}/task.md
 ```
 
 Confirm the task directory was moved successfully.
@@ -120,7 +120,7 @@ Task {task-id} cancelled; task directory moved to completed/.
 
 Cancellation reason: {reason}
 Status label: {status-label or skipped}
-Target path: .agents/workspace/completed/{task-id}/
+Target path: <task-workspace>/completed/{task-id}/
 
 Optional: clean up this task's sandbox
 (The task is completed and archived; the sandbox container and per-branch config directory are not reclaimed automatically. Run this if you no longer need them:)
@@ -136,7 +136,7 @@ Next step - inspect the moved task:
 ## Completion Checklist
 
 - [ ] Recorded the cancellation reason and updated task.md
-- [ ] Moved the task directory into `.agents/workspace/completed/`
+- [ ] Moved the task directory into `<task-workspace>/completed/`
 - [ ] Completed Issue sync when an Issue exists
 - [ ] Ran and passed the verification gate
 - [ ] Showed the full next-step command set to the user

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

@@ -32,9 +32,9 @@ description: >
 ### 1. 验证任务存在
 
 依次检查以下目录：
-- `.agents/workspace/active/{task-id}/`
-- `.agents/workspace/blocked/{task-id}/`
-- `.agents/workspace/completed/{task-id}/`
+- `<task-workspace>/active/{task-id}/`
+- `<task-workspace>/blocked/{task-id}/`
+- `<task-workspace>/completed/{task-id}/`
 
 处理规则：
 - 如果在 `active/` 或 `blocked/` 中找到：继续
@@ -68,7 +68,7 @@ agent-infra-internal task-lifecycle {task-id} cancel --agent {standard-agent-tok
 ### 5. 验证转移
 
 ```bash
-ls .agents/workspace/completed/{task-id}/task.md
+ls <task-workspace>/completed/{task-id}/task.md
 ```
 
 确认任务目录已成功移动。
@@ -117,7 +117,7 @@ agent-infra-internal task-verify {task-id} cancel-task.completed --format text
 
 取消原因：{reason}
 状态标签：{status-label 或 skipped}
-目标路径：.agents/workspace/completed/{task-id}/
+目标路径：<task-workspace>/completed/{task-id}/
 
 可选：清理本任务的沙箱
 （任务已完成并归档，沙箱容器和 per-branch 配置目录不会自动回收。如果不再需要可执行：）
@@ -133,7 +133,7 @@ ai sandbox rm {task-id}
 ## 完成检查清单
 
 - [ ] 已记录取消原因并更新 task.md
-- [ ] 已将任务目录移动到 `.agents/workspace/completed/`
+- [ ] 已将任务目录移动到 `<task-workspace>/completed/`
 - [ ] 已在存在 Issue 时完成 Issue 同步
 - [ ] 已运行 gate 校验并通过
 - [ ] 已通过统一 helper 渲染已选场景的下一步命令

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

@@ -19,7 +19,6 @@
       "require_cancelled_at": true
     },
     "activity-log": {
-      "expected_action_pattern": "(Cancel Task|Cancelled)"
     },
     "platform-sync": {
       "when": "platform_issue_identity_exists"

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

@@ -126,7 +126,7 @@ agent-infra-internal task-artifact {task-id} init --family code --artifact {code
 
 The skeleton contains identity metadata, stable section markers, and required headings only; real implementation and verification content is required before the completion gate can pass. On a preflight or finalization structural error, follow `.agents/rules/local-artifact-repair.md` to correct the formal artifact directly and rerun the same entry point; current structure, qualification, and summary facts are the only gate.
 
-Create `.agents/workspace/active/{task-id}/{code-artifact}`.
+Create `<task-workspace>/active/{task-id}/{code-artifact}`.
 
 > Read `reference/report-template.md` before writing the report.
 

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

@@ -75,7 +75,7 @@ agent-infra-internal task-snapshot {task-id} --format text
 ### 1. 验证前置条件
 
 先检查：
-- `.agents/workspace/active/{task-id}/task.md`
+- `<task-workspace>/active/{task-id}/task.md`
 
 如果缺少任务文件，立即停止。生命周期输入由步骤 4 的核心查询按已选路径验证；技能不得预先固定要求方案产物。
 
@@ -165,7 +165,7 @@ agent-infra-internal task-artifact {task-id} init --family code --artifact {code
 
 骨架只包含身份元数据、稳定 section marker 和必需标题；必须填入真实实现与验证内容后才能通过完成门禁。preflight 或 finalizer 返回结构错误时，按 `.agents/rules/local-artifact-repair.md` 直接修正正式产物并重跑原入口；当前结构、资格和摘要事实是唯一门禁。
 
-创建 `.agents/workspace/active/{task-id}/{code-artifact}`。
+创建 `<task-workspace>/active/{task-id}/{code-artifact}`。
 
 > 报告结构、必填章节和完整模板见 `reference/report-template.md`。写报告前先读取 `reference/report-template.md`。
 
@@ -207,7 +207,7 @@ echo "$finalizer"
 
 ### 11. 更新任务状态
 
-更新 `.agents/workspace/active/{task-id}/task.md`：
+更新 `<task-workspace>/active/{task-id}/task.md`：
 - 审查 `## 需求` 段落，仅把本轮已由代码实现且有测试通过支撑的条目从 `- [ ]` 勾为 `- [x]`
 - 产物链接、阶段与完成日志由 completed 事件统一登记
 - 完成业务内容更新后声明完成事件：

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

@@ -21,7 +21,6 @@
     },
     "implementation-input": {},
     "activity-log": {
-      "expected_action_pattern": "(Code Task|Code) \\(Round \\d+(?:(?:, fix for review-code(?:-r\\d+)?\\.md)|(?:, decision II-[1-9]\\d*))?\\)"
     },
     "review-ledger": {
       "stage_scope": [

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

@@ -21,7 +21,6 @@
     },
     "implementation-input": {},
     "activity-log": {
-      "expected_action_pattern": "(Code Task|Code) \\(Round \\d+(?:(?:, fix for review-code(?:-r\\d+)?\\.md)|(?:, decision II-[1-9]\\d*))?\\)"
     },
     "review-ledger": {
       "stage_scope": [

package/templates/.agents/skills/code-task/reference/output-template.en.md

@@ -13,7 +13,7 @@ Summary:
 - All tests passed: {yes/no}
 
 Output files:
-- Code report: .agents/workspace/active/{task-id}/{code-artifact}
+- Code report: <task-workspace>/active/{task-id}/{code-artifact}
 
 Next step - code review:
 {next-step-commands}

package/templates/.agents/skills/code-task/reference/output-template.zh-CN.md

@@ -13,7 +13,7 @@
 - 所有测试通过：{是/否}
 
 产出文件：
-- 实现报告：.agents/workspace/active/{task-id}/{code-artifact}
+- 实现报告：<task-workspace>/active/{task-id}/{code-artifact}
 
 下一步 - 代码审查：
 {next-step-commands}

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

@@ -71,7 +71,7 @@ Example:
 }
 ```
 
-Taskless direct mode omits `taskRef`; direct task-bound commits use push delivery. The core owns repository/worktree mutation locking, task locking when bound, path and sensitive-file checks, staged scope, HEAD/tree, branch/ref, commit, push, protected-branch policy, warnings, and idempotency.
+Taskless direct mode omits `taskRef`; direct task-bound commits use push delivery. Both modes execute serially at the caller boundary; the core still owns path and sensitive-file checks, staged scope, HEAD/tree, branch/ref, commit, push, protected-branch policy, warnings, and idempotency.
 
 - Create at most one local commit for explicit changes.
 - If there are no changes but HEAD is ahead and delivery is requested, perform push-only and do not create an empty commit.

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

@@ -71,7 +71,7 @@ agent-infra-internal git-workflow commit --input {commit-operation.json}
 }
 ```
 
-taskless direct 省略 `taskRef`；direct task-bound commit 使用 push delivery。core 统一负责 repository/worktree mutation lock、task lock（仅 task-bound）、路径和敏感文件、staged scope、HEAD/tree、branch/ref、commit、push、保护分支、warning 和幂等校验。
+taskless direct 省略 `taskRef`；direct task-bound commit 使用 push delivery。两种模式都按调用方串行执行；core 仍负责路径和敏感文件、staged scope、HEAD/tree、branch/ref、commit、push、保护分支、warning 和幂等校验。
 
 - 有明确修改时最多创建一个本地 commit。
 - 无修改但需要交付本地领先的 HEAD 时只执行 push-only，不创建空 commit。

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

@@ -15,7 +15,6 @@
       ]
     },
     "activity-log": {
-      "expected_action_pattern": "Commit"
     },
     "platform-sync": {
       "when": "pr_fact_bound"

package/templates/.agents/skills/commit/reference/commit-orchestration.en.md

@@ -4,12 +4,12 @@ Commit, push, result mapping, and task finalization use one `commit-operation.ex
 
 ## Entry modes
 
-- `mode=direct`: explicit user invocation is the authorization. Task-bound direct may read task facts but does not require a delegation receipt; taskless direct is allowed only for `TASK_CONTEXT_NOT_FOUND` and skips task facts, review, task lock, checkpoint, and task.md finalization.
+- `mode=direct`: explicit user invocation is the authorization. Task-bound direct may read task facts but does not require a delegation receipt; taskless direct is allowed only for `TASK_CONTEXT_NOT_FOUND` and skips task facts, review, checkpoint, and task.md finalization.
 - `mode=orchestrated` is removed: standalone commit is no longer a lifecycle delegation stage. This mode returns `ORCHESTRATED_COMMIT_REMOVED` without writing Git; the code stage closes through a local checkpoint.
 
 ## Shared order
 
-1. Acquire the repository/worktree mutation lock; task-bound execution also acquires the task lock.
+1. Direct commits execute serially at the caller boundary.
 2. Validate the repository, current branch, explicit paths, sensitive paths, staged scope, expected HEAD/tree, remote, and full heads ref.
 3. Validate direct-mode authorization.
 4. Create at most one local commit; with no changes, allow push-only and never create an empty commit.

package/templates/.agents/skills/commit/reference/commit-orchestration.zh-CN.md

@@ -4,12 +4,12 @@ commit、push、结果映射和任务收尾使用同一个 `commit-operation.exe
 
 ## 入口模式
 
-- `mode=direct`：用户显式调用授权。task-bound direct 可读取 task facts，但不要求 delegation receipt；taskless direct 只在 `TASK_CONTEXT_NOT_FOUND` 时允许，并跳过 task facts、review、task lock、checkpoint 和 task.md 收尾。
+- `mode=direct`：用户显式调用授权。task-bound direct 可读取 task facts，但不要求 delegation receipt；taskless direct 只在 `TASK_CONTEXT_NOT_FOUND` 时允许，并跳过 task facts、review、checkpoint 和 task.md 收尾。
 - `mode=orchestrated` 已移除：独立 commit 不再是生命周期 delegation stage；调用该模式返回 `ORCHESTRATED_COMMIT_REMOVED`，不写 Git。生命周期 code 阶段完成后由 local checkpoint 直接收口。
 
 ## 共享执行顺序
 
-1. 获取 repository/worktree mutation lock；task-bound 额外获取 task lock。
+1. direct commit 按调用方串行执行。
 2. 验证 repository、当前 branch、明确 paths、敏感路径、staged scope、expected HEAD/tree、remote 和 full heads ref。
 3. 完成 direct 模式授权校验。
 4. 最多创建一个本地 commit；无修改时只允许 push-only，不创建空 commit。