[2026-10-20] eagle: work/projects/vscode-migration/postmortem.md

work/projects/vscode-migration/postmortem.md

@@ -13,7 +13,7 @@ dri: Alex M
 
 **For what:** [Migration to fully VSCode-supported builds&debugging](https://app.asana.com/1/137249556945/project/1203301625297703/task/1209808486380252)
 **Started:** 2025-05-27 (task created 2025-03-27) · **Closed:** 2026-10-16 · **DRI:** Alex M
-**Zoom link:** <Zoom link>
+**Zoom link:** 
 
 Related notes: [[projects/vscode-migration/vscode-migration]] · [[projects/vscode-migration/findings]] · [[projects/vscode-migration/tech-design-spm-browser-package]] · [[projects/vscode-migration/tech-design-xcode-build-server]] · [[projects/vscode-migration/modularization-roadmap]]
 
@@ -35,7 +35,7 @@ The SPM build-time gains in the project description (−24% to −30% clean buil
 ## What went well that we can repeat in the future?
 
 - The prerequisites shipped as small, separate refactors (storyboards, target flags, membership, assets, strings). Each one improved the codebase on its own.
-- Tech design reviews worked. The first TD got specific objections, and a narrower, opt-in TD followed within two days.
+- Tech design reviews worked. The 2025 module-conversion TD was approved after its questions were answered. Its 2026 follow-up (the browser code as a Swift package) got specific objections, and a narrower, opt-in build-server TD followed the same day it was closed.
 - Dropping the CoreData code-model migration once Xcode 27's swift-build built the models as they are. That removed the riskiest change people raised on Sep 29.
 - I use the setup every day. On top of convenience compared to Xcode, it opens up remote debugging on older macOS versions (VMs).