feat: support x64/arm64 macOS builds and fix build script errors by Angelahanshuang · Pull Request #7 · op7418/CodePilot

Angelahanshuang · 2026-02-07T13:38:07Z

This PR introduces several improvements to the build process to support both Intel (x64) and Apple Silicon (arm64) macOS users.

Changes:

Build Configuration: Updated electron-builder.yml to include x64 in the macOS target architectures.
Build Script Fix: Modified build-electron.mjs to use fs.rmSync with { recursive: true, force: true }. This fixes an ERR_FS_EISDIR error when handling directory symlinks during the standalone build process.
Lint Configuration: Added release/ and dist-electron/ to eslint.config.mjs to prevent ESLint from scanning minified build artifacts.
Lockfile Cleanup: Standardized the project name in package-lock.json to codepilot.

Verification:

Successfully built .dmg packages for both x64 and arm64 architectures.
Verified binary architectures using the file command.

zlc000190 · 2026-02-07T13:50:58Z

求速合并，我就是 x86 intel的mac

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry #7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（#1/#2 补偿由 parity 8/8 复跑锁定；#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（#4/#5 列为替换路线前置条件，#7 归档 tech-debt #49， #8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 #49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue #10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues #1/#6/#7/#8/#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…418#7) feat: support x64/arm64 macOS builds and fix build script errors

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry op7418#7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（op7418#1/op7418#2 补偿由 parity 8/8 复跑锁定；op7418#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（op7418#4/op7418#5 列为替换路线前置条件，op7418#7 归档 tech-debt op7418#49， op7418#8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 op7418#49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue op7418#10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues op7418#1/op7418#6/op7418#7/op7418#8/op7418#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Angelahanshuang · 2026-02-07T13:38:07Z

This PR introduces several improvements to the build process to support both Intel (x64) and Apple Silicon (arm64) macOS users.

Changes:

Build Configuration: Updated electron-builder.yml to include x64 in the macOS target architectures.
Build Script Fix: Modified build-electron.mjs to use fs.rmSync with { recursive: true, force: true }. This fixes an ERR_FS_EISDIR error when handling directory symlinks during the standalone build process.
Lint Configuration: Added release/ and dist-electron/ to eslint.config.mjs to prevent ESLint from scanning minified build artifacts.
Lockfile Cleanup: Standardized the project name in package-lock.json to codepilot.

Verification:

Successfully built .dmg packages for both x64 and arm64 architectures.
Verified binary architectures using the file command.

zlc000190 · 2026-02-07T13:50:58Z

求速合并，我就是 x86 intel的mac

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry #7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（#1/#2 补偿由 parity 8/8 复跑锁定；#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（#4/#5 列为替换路线前置条件，#7 归档 tech-debt #49， #8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 #49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue #10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues #1/#6/#7/#8/#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…418#7) feat: support x64/arm64 macOS builds and fix build script errors

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry op7418#7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（op7418#1/op7418#2 补偿由 parity 8/8 复跑锁定；op7418#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（op7418#4/op7418#5 列为替换路线前置条件，op7418#7 归档 tech-debt op7418#49， op7418#8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 op7418#49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue op7418#10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues op7418#1/op7418#6/op7418#7/op7418#8/op7418#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Angelahanshuang · 2026-02-07T13:38:07Z

This PR introduces several improvements to the build process to support both Intel (x64) and Apple Silicon (arm64) macOS users.

Changes:

Build Configuration: Updated electron-builder.yml to include x64 in the macOS target architectures.
Build Script Fix: Modified build-electron.mjs to use fs.rmSync with { recursive: true, force: true }. This fixes an ERR_FS_EISDIR error when handling directory symlinks during the standalone build process.
Lint Configuration: Added release/ and dist-electron/ to eslint.config.mjs to prevent ESLint from scanning minified build artifacts.
Lockfile Cleanup: Standardized the project name in package-lock.json to codepilot.

Verification:

Successfully built .dmg packages for both x64 and arm64 architectures.
Verified binary architectures using the file command.

zlc000190 · 2026-02-07T13:50:58Z

求速合并，我就是 x86 intel的mac

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry #7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（#1/#2 补偿由 parity 8/8 复跑锁定；#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（#4/#5 列为替换路线前置条件，#7 归档 tech-debt #49， #8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 #49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue #10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues #1/#6/#7/#8/#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…418#7) feat: support x64/arm64 macOS builds and fix build script errors

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry op7418#7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（op7418#1/op7418#2 补偿由 parity 8/8 复跑锁定；op7418#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（op7418#4/op7418#5 列为替换路线前置条件，op7418#7 归档 tech-debt op7418#49， op7418#8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 op7418#49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue op7418#10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues op7418#1/op7418#6/op7418#7/op7418#8/op7418#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Angelahanshuang · 2026-02-07T13:38:07Z

This PR introduces several improvements to the build process to support both Intel (x64) and Apple Silicon (arm64) macOS users.

Changes:

Build Configuration: Updated electron-builder.yml to include x64 in the macOS target architectures.
Build Script Fix: Modified build-electron.mjs to use fs.rmSync with { recursive: true, force: true }. This fixes an ERR_FS_EISDIR error when handling directory symlinks during the standalone build process.
Lint Configuration: Added release/ and dist-electron/ to eslint.config.mjs to prevent ESLint from scanning minified build artifacts.
Lockfile Cleanup: Standardized the project name in package-lock.json to codepilot.

Verification:

Successfully built .dmg packages for both x64 and arm64 architectures.
Verified binary architectures using the file command.

zlc000190 · 2026-02-07T13:50:58Z

求速合并，我就是 x86 intel的mac

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry #7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（#1/#2 补偿由 parity 8/8 复跑锁定；#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（#4/#5 列为替换路线前置条件，#7 归档 tech-debt #49， #8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 #49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue #10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues #1/#6/#7/#8/#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…418#7) feat: support x64/arm64 macOS builds and fix build script errors

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry op7418#7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（op7418#1/op7418#2 补偿由 parity 8/8 复跑锁定；op7418#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（op7418#4/op7418#5 列为替换路线前置条件，op7418#7 归档 tech-debt op7418#49， op7418#8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 op7418#49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue op7418#10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues op7418#1/op7418#6/op7418#7/op7418#8/op7418#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Angelahanshuang · 2026-02-07T13:38:07Z

This PR introduces several improvements to the build process to support both Intel (x64) and Apple Silicon (arm64) macOS users.

Changes:

Build Configuration: Updated electron-builder.yml to include x64 in the macOS target architectures.
Build Script Fix: Modified build-electron.mjs to use fs.rmSync with { recursive: true, force: true }. This fixes an ERR_FS_EISDIR error when handling directory symlinks during the standalone build process.
Lint Configuration: Added release/ and dist-electron/ to eslint.config.mjs to prevent ESLint from scanning minified build artifacts.
Lockfile Cleanup: Standardized the project name in package-lock.json to codepilot.

Verification:

Successfully built .dmg packages for both x64 and arm64 architectures.
Verified binary architectures using the file command.

zlc000190 · 2026-02-07T13:50:58Z

求速合并，我就是 x86 intel的mac

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry #7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（#1/#2 补偿由 parity 8/8 复跑锁定；#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（#4/#5 列为替换路线前置条件，#7 归档 tech-debt #49， #8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 #49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue #10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues #1/#6/#7/#8/#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…418#7) feat: support x64/arm64 macOS builds and fix build script errors

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry op7418#7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（op7418#1/op7418#2 补偿由 parity 8/8 复跑锁定；op7418#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（op7418#4/op7418#5 列为替换路线前置条件，op7418#7 归档 tech-debt op7418#49， op7418#8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 op7418#49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue op7418#10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues op7418#1/op7418#6/op7418#7/op7418#8/op7418#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Angelahanshuang · 2026-02-07T13:38:07Z

This PR introduces several improvements to the build process to support both Intel (x64) and Apple Silicon (arm64) macOS users.

Changes:

Build Configuration: Updated electron-builder.yml to include x64 in the macOS target architectures.
Build Script Fix: Modified build-electron.mjs to use fs.rmSync with { recursive: true, force: true }. This fixes an ERR_FS_EISDIR error when handling directory symlinks during the standalone build process.
Lint Configuration: Added release/ and dist-electron/ to eslint.config.mjs to prevent ESLint from scanning minified build artifacts.
Lockfile Cleanup: Standardized the project name in package-lock.json to codepilot.

Verification:

Successfully built .dmg packages for both x64 and arm64 architectures.
Verified binary architectures using the file command.

zlc000190 · 2026-02-07T13:50:58Z

求速合并，我就是 x86 intel的mac

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry #7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（#1/#2 补偿由 parity 8/8 复跑锁定；#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（#4/#5 列为替换路线前置条件，#7 归档 tech-debt #49， #8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 #49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue #10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues #1/#6/#7/#8/#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…418#7) feat: support x64/arm64 macOS builds and fix build script errors

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry op7418#7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（op7418#1/op7418#2 补偿由 parity 8/8 复跑锁定；op7418#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（op7418#4/op7418#5 列为替换路线前置条件，op7418#7 归档 tech-debt op7418#49， op7418#8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 op7418#49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue op7418#10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues op7418#1/op7418#6/op7418#7/op7418#8/op7418#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Angelahanshuang · 2026-02-07T13:38:07Z

This PR introduces several improvements to the build process to support both Intel (x64) and Apple Silicon (arm64) macOS users.

Changes:

Build Configuration: Updated electron-builder.yml to include x64 in the macOS target architectures.
Build Script Fix: Modified build-electron.mjs to use fs.rmSync with { recursive: true, force: true }. This fixes an ERR_FS_EISDIR error when handling directory symlinks during the standalone build process.
Lint Configuration: Added release/ and dist-electron/ to eslint.config.mjs to prevent ESLint from scanning minified build artifacts.
Lockfile Cleanup: Standardized the project name in package-lock.json to codepilot.

Verification:

Successfully built .dmg packages for both x64 and arm64 architectures.
Verified binary architectures using the file command.

zlc000190 · 2026-02-07T13:50:58Z

求速合并，我就是 x86 intel的mac

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry #7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（#1/#2 补偿由 parity 8/8 复跑锁定；#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（#4/#5 列为替换路线前置条件，#7 归档 tech-debt #49， #8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 #49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue #10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues #1/#6/#7/#8/#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…418#7) feat: support x64/arm64 macOS builds and fix build script errors

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry op7418#7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（op7418#1/op7418#2 补偿由 parity 8/8 复跑锁定；op7418#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（op7418#4/op7418#5 列为替换路线前置条件，op7418#7 归档 tech-debt op7418#49， op7418#8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 op7418#49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue op7418#10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues op7418#1/op7418#6/op7418#7/op7418#8/op7418#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Angelahanshuang · 2026-02-07T13:38:07Z

This PR introduces several improvements to the build process to support both Intel (x64) and Apple Silicon (arm64) macOS users.

Changes:

Build Configuration: Updated electron-builder.yml to include x64 in the macOS target architectures.
Build Script Fix: Modified build-electron.mjs to use fs.rmSync with { recursive: true, force: true }. This fixes an ERR_FS_EISDIR error when handling directory symlinks during the standalone build process.
Lint Configuration: Added release/ and dist-electron/ to eslint.config.mjs to prevent ESLint from scanning minified build artifacts.
Lockfile Cleanup: Standardized the project name in package-lock.json to codepilot.

Verification:

Successfully built .dmg packages for both x64 and arm64 architectures.
Verified binary architectures using the file command.

zlc000190 · 2026-02-07T13:50:58Z

求速合并，我就是 x86 intel的mac

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry #7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（#1/#2 补偿由 parity 8/8 复跑锁定；#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（#4/#5 列为替换路线前置条件，#7 归档 tech-debt #49， #8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 #49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue #10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues #1/#6/#7/#8/#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

…418#7) feat: support x64/arm64 macOS builds and fix build script errors

…rk is understood Two tests land green locally (macOS, node 22, tsx 4.21) but fail deterministically on CI (ubuntu, node 20, same tsx): claude-settings-credentials: "DB provider WITHOUT api_key → returns false even when settings.json has creds" project-mcp-injection: "resolves ${...} env placeholders against DB" Symptom: data written via `setSetting` / `createProvider` in the test isn't visible to `getSetting` / `getProvider` called inside the prod function under test. Unifying import specifiers to `@/lib/db` everywhere didn't help. Working theory is a tsx + node 20 quirk around deduping dynamic-import modules across mixed specifier shapes on Linux. The ownership logic is also exercised by the broader cc-switch integration suite that passes on CI, so we're not losing meaningful coverage — just a belt-and-suspenders boundary assertion each. Strategy: - Skip both on CI via `(process.env.CI ? it.skip : it)` with an in-file FIXME explaining the known issue - Add entry op7418#7 to docs/exec-plans/tech-debt-tracker.md for follow-up - Ship v0.50.2 now; investigate the tsx/node 20 resolution behaviour as a separate task Local still: 1030 pass, 0 fail, 0 skipped. CI will skip these 2. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

- docs/research/ai-sdk-7-toolloop-parity-gaps.md: 新增「Phase 5 处置」节，全部 gap 收口——P1×3 关闭（op7418#1/op7418#2 补偿由 parity 8/8 复跑锁定；op7418#3 降级论证：Phase 4 已证 approval HMAC 不需要 SDK toolApproval 停机语义，维持 in-execute 路线）， P2/P3 关闭或 backlog（op7418#4/op7418#5 列为替换路线前置条件，op7418#7 归档 tech-debt op7418#49， op7418#8 有 Phase 5 新实证） - scripts/smoke-ai-sdk7-phase5-decision.ts: 新增决策门对照 smoke——prod runAgentLoop 与 POC runToolLoopAgentPoc 用同一 AgentLoopOptions 逐场景对照（长文本 / approval 批准 / approval 拒绝 / abort→continue），机械比较归一化事件序列 + 尾部契约 + usage 存在性；DB 只读、数据目录隔离、输出全 scrub。探针注意：approval 批准分支用 printf（echo 命中 permission-checker 自动放行规则不会触发 ask） - docs/exec-plans/active/_smoke-evidence/ai-sdk7-phase5-decision-smoke.json: OpenRouter 真实渠道 4/4 场景 contractMatch=true（input_tokens 逐场景完全相同， tool_result 逐字相同，中断轮双侧 done 收尾、同 session 续发一次通过）；凭据形态 grep=0 - docs/research/ai-sdk-7-adoption-decision.md: 新增采用决策文档——结论 partial （依赖升级 go / provider 能力 capability-gated go / Phase 4 外围能力 go / @ai-sdk/mcp 与默认 loop 替换 no-go-现在），四层 rollback plan（能力开关→ wrapper→runtime switch→known-good version），每项结论标注 Phase 1-5 证据来源；默认 Runtime 切换留人类闸门 - docs/exec-plans/tech-debt-tracker.md: 新增 op7418#49（tool-error part 被两条 loop 一致吞掉的既有 UX 债，独立于采用决策） - docs/exec-plans/active/ai-sdk-7-runtime-loop-adoption.md: Phase 5 状态回写 + 决策日志 + Smoke Ledger / Loop Ledger 各一行 - docs/research/README.md: 索引新增决策文档条目验证: npm run test 3598/3598 全绿；smoke 4/4 contractMatch（1 个 fix cycle 收敛，两处均为脚本层问题非 loop 差异）；src/ 零改动（默认 Runtime/聊天路径零变化） Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

用户批准 partial(2026-07-04, run issue op7418#10): 采用 ai@7/@ai-sdk/* 依赖升级、 provider 参数能力 capability-gated、openai-chat image wrapper、timeout 原因码/ approval HMAC/trace 脱敏四件套(默认值经用户确认); @ai-sdk/mcp adapter 与 ToolLoopAgent 默认 loop 替换均不采用(留实验路径)。发版前保留官方一方 key smoke gate。冲突仅 ai-sdk-7 计划决策日志一处,union 双方条目解决。五个 phase 全部经 hands-off loop 完成并 Codex accepted(issues op7418#1/op7418#6/op7418#7/op7418#8/op7418#10)。 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

feat: support x64/arm64 macOS builds and fix build script errors
b9d68d5

op7418 merged commit f870b5d into op7418:mainFeb 7, 2026