diff --git a/work/projects/vscode-migration/tech-design-xcode-build-server.md b/work/projects/vscode-migration/tech-design-xcode-build-server.md
index 42319b52..e4cb730c 100644
--- a/work/projects/vscode-migration/tech-design-xcode-build-server.md
+++ b/work/projects/vscode-migration/tech-design-xcode-build-server.md
@@ -64,8 +64,7 @@ Add an opt-in VS Code setup to the repository: a workspace file and a few script
 - **Some rough edges:**
   - one platform per worktree at a time;
   - the first index of a new worktree takes ~5 minutes.
-- **Someone has to own it.** I will; the setup is small (a workspace file and ~6 scripts), and it's documented.
-- **Maintenance as Xcode, swift-build and the build server move.** Xcode updates or upstream changes can need updates to the fork or the setup. Mitigation: the people who use the setup do the updates, mostly with AI agents (the setup is small and has a README and tests). Xcode-only users and CI never depend on it.
+- **Someone has to own it.** I will; the setup is small (a workspace file and ~6 scripts), and it's documented. Breaking changes can be handled by a single AI agent run that can fully fix and validate the setup.
 
 ### Risks
 
@@ -86,7 +85,7 @@ Add an opt-in VS Code setup to the repository: a workspace file and a few script
   - builds from Xcode and VS Code don't rebuild each other's work.
 - Debugging: breakpoints in the macOS app and in the iOS app on a simulator.
 - The build server changes have unit tests.
-- Before announcing: two people try it on fresh machines in VS Code and Cursor, and we check that Xcode picks up a worktree built and indexed from VS Code without rebuilding.
+- Before documenting it for the team: two people try it on fresh machines in VS Code and Cursor, and we check that Xcode picks up a worktree built and indexed from VS Code without rebuilding.
 
 ## Additional Considerations