@fitlab-ai/agent-infra 0.8.0 → 0.8.2

package/templates/.agents/skills/review-code/reference/report-template.en.md

@@ -24,7 +24,7 @@ Use this template when writing `review-code.md` or `review-code-r{N}.md`.
 - **Review Baseline Commit**: {raw git rev-parse HEAD} (baseline for the complete-task post-review commit gate; see `.agents/rules/review-handshake.md`)
 - **Reviewed Diff Fingerprint**: {raw node .agents/scripts/review-diff-fingerprint.js worktree HEAD}
 - **Overall Verdict**: {Approved / Changes Requested / Rejected} (pick exactly one; combined phrases will fail the verify gate)
-- **Findings (AI-actionable)**: 0 blockers, 0 majors, 0 minors / **env-blocked**: 0
+- **Findings (AI-actionable)**: 0 blockers, 0 majors, 0 minors / **Manual validation**: 0
 
 ## Findings
 
@@ -48,17 +48,17 @@ Use this template when writing `review-code.md` or `review-code-r{N}.md`.
 **File**: `{file-path}:{line-number}`
 **Suggestion**: {improvement suggestion}
 
-## Environment-Blocked Findings
+## Manual Validation Items
 
 > Items the AI agent cannot close in the current execution environment; they do not participate in the next code round. Maintainers carry them in the PR description as a "manual verification required" checklist.
 
-#### 1. {environment-blocked finding title}
+#### 1. {manual validation item title}
 **File**: `{file-path}:{line-number}` (if applicable)
 **Description**: {details}
 **Required Environment**: {e.g. Docker sandbox / macOS host / privileged root / third-party account}
 **Manual Verification Steps**: {steps for the human verifier}
 
-> If this round has no env-blocked findings, keep the section heading and write "None".
+> If this round has no Manual validation items, keep the section heading and write "None".
 
 
 ## Review Disagreement Ledger Writeback

package/templates/.agents/skills/review-code/reference/report-template.zh-CN.md

@@ -24,7 +24,7 @@
 - **审查基线提交**：{git rev-parse HEAD 原文}（complete-task 的 post-review commit 门禁基线；详见 `.agents/rules/review-handshake.md`）
 - **审查差异指纹**：{node .agents/scripts/review-diff-fingerprint.js worktree HEAD 原文}
 - **总体结论**：{通过 / 需要修改 / 拒绝}（恰取一个；禁止写组合短语，否则 verify gate 失败）
-- **发现（AI 可处理）**：0 阻塞项，0 主要，0 次要 / **env-blocked**：0
+- **发现（AI 可处理）**：0 阻塞项，0 主要，0 次要 / **人工校验**：0
 
 ## 问题清单
 
@@ -48,17 +48,17 @@
 **文件**：`{file-path}:{line-number}`
 **建议**：{improvement suggestion}
 
-## 环境性遗留
+## 人工校验项
 
 > AI agent 在本执行环境无法闭环的项；不参与下一轮 refine。维护者在 PR description 中以「待人工验证」清单承接。
 
-#### 1. {环境性项标题}
+#### 1. {人工校验项标题}
 **文件**：`{file-path}:{line-number}`（如适用）
 **说明**：{details}
 **所需环境**：{e.g. Docker 沙箱 / macOS host / 特权 root / 第三方账号}
 **待人工执行的验证步骤**：{steps for the human verifier}
 
-> 如本轮无 env-blocked 项，保留段落标题并写「（无）」。
+> 如本轮无人工校验项，保留段落标题并写「（无）」。
 
 
 ## 审查分歧账本回写

package/templates/.agents/skills/review-code/reference/review-criteria.en.md

@@ -30,7 +30,7 @@ Follow the `code-review` step in `.agents/workflows/feature-development.yaml`.
 3. **Actionable**: suggest a concrete fix
 4. **Severity-based**: clearly distinguish blockers, major issues, and minor issues
 
-## Environment-Blocked Classification
+## Manual Validation Classification
 
 Some findings cannot be closed by an AI agent in the current execution environment, for example:
 
@@ -41,11 +41,11 @@ Some findings cannot be closed by an AI agent in the current execution environme
 
 **Decision tree**: "Can the AI agent close this item independently without changing the environment?"
 - Yes -> blocker / major / minor, based on risk
-- No -> **env-blocked** (a meta-category, not part of severity ordering)
+- No -> **manual-validation** (a manual-validation meta-category, not part of severity ordering)
 
-Where env-blocked items go:
-- Record them in an independent review report section named "Environment-Blocked Findings"
-- Include them at the end of the numeric summary, for example `(+ 1 env-blocked)`
+Where manual-validation items go:
+- Record them in an independent review report section named "Manual Validation Items"
+- Record the done-note source field as `Manual-validation: 1`; `ai task log` normalizes it into review rows
 - Do **not** include them in the code-task fix loop; maintainers carry them in the PR description under manual verification
 
 Also inspect `git diff`, the latest code artifact, latest technical-plan review artifact, and `task.md` Activity Log so the report reflects the full change context.

package/templates/.agents/skills/review-code/reference/review-criteria.zh-CN.md

@@ -30,7 +30,7 @@
 3. **可执行**：给出明确可落地的修复建议
 4. **按严重程度分类**：明确区分 blocker、major 和 minor
 
-## 环境性遗留分类
+## 人工校验项分类
 
 某些发现项是 AI agent 在本执行环境**无法闭环**的，例如：
 
@@ -41,11 +41,11 @@
 
 **分类决策树**：「AI agent 能否在不改环境的前提下独立闭环这一项？」
 - 是 -> blocker / major / minor 之一（按风险定档）
-- 否 -> **env-blocked**（元类目，不参与严重程度排序）
+- 否 -> **manual-validation**（人工校验元类目，不参与严重程度排序）
 
-env-blocked 项的去向：
-- 写入 review 报告独立段落「环境性遗留」
-- 在数字摘要末尾附带显示（如 `(+ 1 env-blocked)`）
+manual-validation 项的去向：
+- 写入 review 报告独立段落「人工校验项」
+- 在 done note 中写入源字段 `Manual-validation: 1`；`ai task log` 归一化展示到 review 行
 - **不**进入 code-task 修复循环；维护者在 PR description 中以「待人工验证」清单形式承接
 
 同时检查 `git diff`、最新实现产物、最新技术方案审查产物和 `task.md` Activity Log，确保报告反映完整的变更上下文。

package/templates/.agents/skills/review-plan/SKILL.en.md

@@ -77,9 +77,9 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 ```
 
 Set `current_step` to `technical-design-review`, refresh task metadata, and append:
-`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Plan (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {review-artifact}`
+`- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Plan (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}, Manual-validation: {n} → {review-artifact}`
 
-`env-blocked` is the data source for the `Manual-verify` count folded into review rows in `ai task log`; do not add a parallel manual-verification field.
+`manual-validation` is the data source for the `Manual-validation` count folded into review rows in `ai task log`; do not add a parallel manual-verification field.
 
 If task.md has a valid `issue_number`, read `.agents/rules/issue-sync.md`, sync the task comment, and publish the `{review-artifact}` comment.
 

package/templates/.agents/skills/review-plan/SKILL.zh-CN.md

@@ -88,9 +88,9 @@ date "+%Y-%m-%d %H:%M:%S%:z"
 - `updated_at`：{当前时间}
 - `agent_infra_version`：按 `.agents/rules/version-stamp.md` 取值
 - 追加：
-  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Plan (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}[ (+ {n} env-blocked)] → {review-artifact}`
+  `- {YYYY-MM-DD HH:mm:ss±HH:MM} — **Review Plan (Round {N})** by {agent} — Verdict: {Approved/Changes Requested/Rejected}, blockers: {n}, major: {n}, minor: {n}, Manual-validation: {n} → {review-artifact}`
 
-`env-blocked` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-verify`）计数的数据源；不要新增并行人工验证字段。
+`manual-validation` 是 `ai task log` 中 review 行「人工校验点」（EN `Manual-validation`）计数的数据源；不要新增并行人工验证字段。
 
 如果 task.md 中存在有效的 `issue_number`，执行前先读取 `.agents/rules/issue-sync.md`，完成 upstream 仓库检测和权限检测，然后同步 task 评论并发布 `{review-artifact}` 评论。
 

package/templates/.agents/skills/review-plan/config/verify.en.json

@@ -20,7 +20,7 @@
       "required_sections": [
         "Review Summary",
         "Findings",
-        "Environment-Blocked Findings",
+        "Manual Validation Items",
         "Conclusion and Recommendations",
         "State Check",
         "Evidence",

package/templates/.agents/skills/review-plan/config/verify.zh-CN.json

@@ -20,7 +20,7 @@
       "required_sections": [
         "审查摘要",
         "问题清单",
-        "环境性遗留",
+        "人工校验项",
         "结论与建议",
         "状态核对",
         "证据原文",

package/templates/.agents/skills/review-plan/reference/output-templates.en.md

@@ -4,8 +4,8 @@ Read this file before presenting the final review result to the user.
 
 ## Select exactly one output scenario
 
-Evaluate in this order (**env-blocked count does not participate in selection**):
-1. If `Blocker = 0`, `Major = 0`, and `Minor = 0`, use Scenario A, regardless of env-blocked count
+Evaluate in this order (**manual-validation count does not participate in selection**):
+1. If `Blocker = 0`, `Major = 0`, and `Minor = 0`, use Scenario A, regardless of manual-validation count
 2. If `Blocker = 0` and (`Major > 0` or `Minor > 0`), use Scenario B
 3. If `Blocker > 0` and the issues can be handled by one focused revision, use Scenario C
 4. If the technical plan needs major redesign, broad rewriting, or a restart, use Scenario D
@@ -14,7 +14,7 @@ Rules:
 - Do not skip scenario selection
 - Do not mix text from multiple scenarios
 - If `Blocker > 0`, never use an approved template
-- Never count env-blocked items as blocker / major / minor or use them to trigger Scenario B/C/D
+- Never count manual-validation items as blocker / major / minor or use them to trigger Scenario B/C/D
 - The selected scenario must include all TUI command formats
 - The count line always shows 4 numbers: the first three (Blockers / Major / Minor) must be 0 to proceed; the fourth, `Human-decision` (`{h}`), is the number of rows in task.md `## 审查分歧账本` with `stage=plan` and `status=needs-human-decision` — a "pending human ruling" item that need not be zero and does not participate in scenario selection. When `{h} > 0`, before the selected scenario's "Next steps" commands you must expand each pending ruling per the "Pending human-decision pre-block" in `.agents/rules/next-step-output.md` and prompt to resolve them first
 
@@ -30,8 +30,8 @@ Next step - write code:
   - Gemini CLI: /agent-infra:code-task {task-ref}
   - Codex CLI: $code-task {task-ref}
 
-[When env-blocked > 0, append:]
-Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /plan-task.
+[When manual-validation > 0, append:]
+Reminder: manual-validation items belong in the PR description manual verification checklist and should not trigger /plan-task.
 ```
 
 ### Scenario B: Approved with findings
@@ -51,8 +51,8 @@ Or proceed directly to coding:
   - Gemini CLI: /agent-infra:code-task {task-ref}
   - Codex CLI: $code-task {task-ref}
 
-[When env-blocked > 0, append:]
-Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /plan-task.
+[When manual-validation > 0, append:]
+Reminder: manual-validation items belong in the PR description manual verification checklist and should not trigger /plan-task.
 ```
 
 ### Scenario C: Changes requested
@@ -67,8 +67,8 @@ Next step - revise technical plan:
   - Gemini CLI: /agent-infra:plan-task {task-ref}
   - Codex CLI: $plan-task {task-ref}
 
-[When env-blocked > 0, append:]
-Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /plan-task.
+[When manual-validation > 0, append:]
+Reminder: manual-validation items belong in the PR description manual verification checklist and should not trigger /plan-task.
 ```
 
 ### Scenario D: Rejected
@@ -83,6 +83,6 @@ Next step - redesign:
   - Gemini CLI: /agent-infra:plan-task {task-ref}
   - Codex CLI: $plan-task {task-ref}
 
-[When env-blocked > 0, append:]
-Reminder: env-blocked items belong in the PR description manual verification checklist and should not trigger /plan-task.
+[When manual-validation > 0, append:]
+Reminder: manual-validation items belong in the PR description manual verification checklist and should not trigger /plan-task.
 ```

package/templates/.agents/skills/review-plan/reference/output-templates.zh-CN.md

@@ -4,8 +4,8 @@
 
 ## 选择唯一输出场景
 
-按以下顺序判断（**注意：env-blocked 数量不参与判断**）：
-1. 如果 `Blocker = 0` 且 `Major = 0` 且 `Minor = 0`，使用场景 A（不管 env-blocked 是否 > 0）
+按以下顺序判断（**注意：manual-validation 数量不参与判断**）：
+1. 如果 `Blocker = 0` 且 `Major = 0` 且 `Minor = 0`，使用场景 A（不管 manual-validation 是否 > 0）
 2. 如果 `Blocker = 0` 且（`Major > 0` 或 `Minor > 0`），使用场景 B
 3. 如果 `Blocker > 0`，且问题可以通过一次聚焦修复解决，使用场景 C
 4. 如果技术方案需要重大重构、大范围重写或整体重来，使用场景 D
@@ -14,7 +14,7 @@
 - 不要跳过场景判断步骤
 - 不要混用不同场景的文案
 - 只要 `Blocker > 0`，就绝对不能输出通过模板
-- env-blocked 项绝对不能被计入 blocker / major / minor 计数，也不能用作触发场景 B/C/D 的依据
+- manual-validation 项绝对不能被计入 blocker / major / minor 计数，也不能用作触发场景 B/C/D 的依据
 - 所选场景中必须包含所有 TUI 命令格式
 - 计数行固定显示 4 个数字：前三项（阻塞 / 主要 / 次要）必须为 0 才进下一步；第四项 `人工裁决`（`{h}`）= task.md `## 审查分歧账本` 中 `stage=plan` 且 `status=needs-human-decision` 的行数，是「待人裁」项、不要求归零，也不参与场景判断。当 `{h} > 0` 时，必须在选定场景的「下一步」命令之前，按 `.agents/rules/next-step-output.md`「人工裁决待办前置块」逐项展开裁决项并提示先完成裁决
 
@@ -30,8 +30,8 @@
   - Gemini CLI：/agent-infra:code-task {task-ref}
   - Codex CLI：$code-task {task-ref}
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
 ```
 
 ### 场景 B：通过但有问题
@@ -51,8 +51,8 @@
   - Gemini CLI：/agent-infra:code-task {task-ref}
   - Codex CLI：$code-task {task-ref}
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
 ```
 
 ### 场景 C：需要修改
@@ -67,8 +67,8 @@
   - Gemini CLI：/agent-infra:plan-task {task-ref}
   - Codex CLI：$plan-task {task-ref}
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
 ```
 
 ### 场景 D：拒绝
@@ -83,6 +83,6 @@
   - Gemini CLI：/agent-infra:plan-task {task-ref}
   - Codex CLI：$plan-task {task-ref}
 
-[当 env-blocked > 0 时，在最后附加一行：]
-提醒：env-blocked 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
+[当 manual-validation > 0 时，在最后附加一行：]
+提醒：manual-validation 项需在 PR description 的「待人工验证」清单中承接，不应触发 /plan-task。
 ```

package/templates/.agents/skills/review-plan/reference/report-template.en.md

@@ -22,7 +22,7 @@ Use this template when writing `review-plan.md` or `review-plan-r{N}.md`.
 - **Review Time**: {timestamp}
 - **Scope**: {file-count and major modules}
 - **Overall Verdict**: {Approved / Changes Requested / Rejected}
-- **Findings (AI-actionable)**: 0 blockers, 0 majors, 0 minors / **env-blocked**: 0
+- **Findings (AI-actionable)**: 0 blockers, 0 majors, 0 minors / **Manual validation**: 0
 
 ## Findings
 
@@ -46,17 +46,17 @@ Use this template when writing `review-plan.md` or `review-plan-r{N}.md`.
 **File**: `{file-path}:{line-number}`
 **Suggestion**: {improvement suggestion}
 
-## Environment-Blocked Findings
+## Manual Validation Items
 
 > Items the AI agent cannot close in the current execution environment; they do not participate in the next plan round. Maintainers carry them in the PR description as a "manual verification required" checklist.
 
-#### 1. {environment-blocked finding title}
+#### 1. {manual validation item title}
 **File**: `{file-path}:{line-number}` (if applicable)
 **Description**: {details}
 **Required Environment**: {e.g. Docker sandbox / macOS host / privileged root / third-party account}
 **Manual Verification Steps**: {steps for the human verifier}
 
-> If this round has no env-blocked findings, keep the section heading and write "None".
+> If this round has no Manual validation items, keep the section heading and write "None".
 
 
 ## Review Disagreement Ledger Writeback

package/templates/.agents/skills/review-plan/reference/report-template.zh-CN.md

@@ -22,7 +22,7 @@
 - **审查时间**：{timestamp}
 - **审查范围**：{file-count and major modules}
 - **总体结论**：{通过 / 需要修改 / 拒绝}
-- **发现（AI 可处理）**：0 阻塞项，0 主要，0 次要 / **env-blocked**：0
+- **发现（AI 可处理）**：0 阻塞项，0 主要，0 次要 / **人工校验**：0
 
 ## 问题清单
 
@@ -46,17 +46,17 @@
 **文件**：`{file-path}:{line-number}`
 **建议**：{improvement suggestion}
 
-## 环境性遗留
+## 人工校验项
 
 > AI agent 在本执行环境无法闭环的项；不参与下一轮 refine。维护者在 PR description 中以「待人工验证」清单承接。
 
-#### 1. {环境性项标题}
+#### 1. {人工校验项标题}
 **文件**：`{file-path}:{line-number}`（如适用）
 **说明**：{details}
 **所需环境**：{e.g. Docker 沙箱 / macOS host / 特权 root / 第三方账号}
 **待人工执行的验证步骤**：{steps for the human verifier}
 
-> 如本轮无 env-blocked 项，保留段落标题并写「（无）」。
+> 如本轮无人工校验项，保留段落标题并写「（无）」。
 
 
 ## 审查分歧账本回写

package/templates/.agents/skills/review-plan/reference/review-criteria.en.md

@@ -29,7 +29,7 @@ Follow the `design-review` step in `.agents/workflows/feature-development.yaml`.
 3. **Actionable**: suggest a concrete fix
 4. **Severity-based**: clearly distinguish blockers, major issues, and minor issues
 
-## Environment-Blocked Classification
+## Manual Validation Classification
 
 Some findings cannot be closed by an AI agent in the current execution environment, for example:
 
@@ -40,11 +40,11 @@ Some findings cannot be closed by an AI agent in the current execution environme
 
 **Decision tree**: "Can the AI agent close this item independently without changing the environment?"
 - Yes -> blocker / major / minor, based on risk
-- No -> **env-blocked** (a meta-category, not part of severity ordering)
+- No -> **manual-validation** (a manual-validation meta-category, not part of severity ordering)
 
-Where env-blocked items go:
-- Record them in an independent review report section named "Environment-Blocked Findings"
-- Include them at the end of the numeric summary, for example `(+ 1 env-blocked)`
+Where manual-validation items go:
+- Record them in an independent review report section named "Manual Validation Items"
+- Record the done-note source field as `Manual-validation: 1`; `ai task log` normalizes it into review rows
 - Do **not** include them in the code-task fix loop; maintainers carry them in the PR description under manual verification
 
 Also inspect the latest technical plan artifact, latest requirement-analysis review artifact, and `task.md` Activity Log so the report reflects the full design context.

package/templates/.agents/skills/review-plan/reference/review-criteria.zh-CN.md

@@ -29,7 +29,7 @@
 3. **可执行**：给出明确可落地的修复建议
 4. **按严重程度分类**：明确区分 blocker、major 和 minor
 
-## 环境性遗留分类
+## 人工校验项分类
 
 某些发现项是 AI agent 在本执行环境**无法闭环**的，例如：
 
@@ -40,11 +40,11 @@
 
 **分类决策树**：「AI agent 能否在不改环境的前提下独立闭环这一项？」
 - 是 -> blocker / major / minor 之一（按风险定档）
-- 否 -> **env-blocked**（元类目，不参与严重程度排序）
+- 否 -> **manual-validation**（人工校验元类目，不参与严重程度排序）
 
-env-blocked 项的去向：
-- 写入 review 报告独立段落「环境性遗留」
-- 在数字摘要末尾附带显示（如 `(+ 1 env-blocked)`）
+manual-validation 项的去向：
+- 写入 review 报告独立段落「人工校验项」
+- 在 done note 中写入源字段 `Manual-validation: 1`；`ai task log` 归一化展示到 review 行
 - **不**进入 code-task 修复循环；维护者在 PR description 中以「待人工验证」清单形式承接
 
 同时检查最新技术方案产物、最新需求分析审查产物和 `task.md` Activity Log，确保报告反映完整的设计上下文。

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

@@ -29,6 +29,7 @@ const DEFAULTS = {
       "node22"
     ],
     "tools": [
+      "agent-infra",
       "claude-code",
       "codex",
       "gemini-cli",
@@ -86,6 +87,9 @@ const DEFAULTS = {
 };
 
 const PACKAGE_NAME = '@fitlab-ai/agent-infra';
+const AGENT_INFRA_SANDBOX_TOOL = 'agent-infra';
+const LEGACY_DEFAULT_SANDBOX_TOOLS = ['claude-code', 'codex', 'gemini-cli', 'opencode'];
+const DEFAULT_SANDBOX_TOOLS = [AGENT_INFRA_SANDBOX_TOOL, ...LEGACY_DEFAULT_SANDBOX_TOOLS];
 // Add a new identifier here only after shipping matching .{platform}. template variants.
 const KNOWN_PLATFORMS = new Set(['github']);
 const KNOWN_LANGUAGES = new Set(['en', 'zh-CN']);
@@ -123,6 +127,26 @@ function isPathOwnedByDisabledTUI(rel, enabledSet) {
   return false;
 }
 
+function isLegacyDefaultSandboxTools(value) {
+  if (!Array.isArray(value) || value.length !== LEGACY_DEFAULT_SANDBOX_TOOLS.length) {
+    return false;
+  }
+  const tools = new Set(value);
+  return LEGACY_DEFAULT_SANDBOX_TOOLS.every(tool => tools.has(tool));
+}
+
+function migrateSandboxTools(cfg) {
+  const tools = cfg.sandbox?.tools;
+  if (!isLegacyDefaultSandboxTools(tools)) {
+    return false;
+  }
+  cfg.sandbox = {
+    ...cfg.sandbox,
+    tools: [...DEFAULT_SANDBOX_TOOLS]
+  };
+  return true;
+}
+
 function norm(p) { return p.replace(/\\/g, '/'); }
 
 function normDir(p) {
@@ -1296,6 +1320,7 @@ function syncTemplates(projectRoot, templateRootOverride) {
   ) > 0;
 
   const prevVersion = cfg.templateVersion;
+  const sandboxToolsMigrated = migrateSandboxTools(cfg);
 
   cfg.files.managed = managed;
   cfg.files.merged  = merged;
@@ -1303,7 +1328,7 @@ function syncTemplates(projectRoot, templateRootOverride) {
   cfg.templateVersion = version;
   delete cfg.templateSource;
 
-  report.configUpdated = hasChanges || prevVersion !== version || hadTemplateSource;
+  report.configUpdated = hasChanges || prevVersion !== version || hadTemplateSource || sandboxToolsMigrated;
 
   fs.writeFileSync(cfgPath, JSON.stringify(cfg, null, 2) + '\n', 'utf8');