[2026-10-16] eagle: work/projects/vscode-migration/tech-design-xcode-build-server.md work/projects/vscode-migration/vscode-migration.md work/projects/vscode-migration/xcode-build-server.md

work/projects/vscode-migration/tech-design-xcode-build-server.md

@@ -11,7 +11,7 @@ The personal [mallexxx/sourcekit-xcode-bsp fork](https://github.com/mallexxx/sou
 
 The reusable harness now lives at `/Users/admin/Developer/xcode-editor-tools`: generic code, README integration instructions, configurable workspace/project/schemes/targets, examples, MIT license, tests and CI workflow. No local paths or Apple browser identifiers are in its source. Project-specific settings live privately at `/Users/admin/DuckDuckGo/apple-browsers.git/.git/xcode-editor/config.json`; shared local `core.hooksPath` selects `.git/xcode-editor/hooks`. All 97 existing worktrees retain identical BSP settings and unchanged tracked/customized files; a fresh 98th experiment bootstrapped automatically with clean status. 47 unit tests and an unrelated real Xcode app build/run plus BSP target discovery passed. Previous harness/hook/config are retained for rollback, and `.vscode-local/worktrees.py` forwards legacy commands.
 
-The standalone harness is initialized on `main` with no commits, staged changes or remote; it has not been published. Generated files remain locally excluded. The earlier `exp/buildServer.json` migration remains the existing intentional uncommitted change because that file was already tracked. No app-repository commits, upstream PRs or issues were created. The DuckDuckGo-owned fork and team/repository rollout described below remain proposed.
+The standalone harness is now public at [mallexxx/xcode-editor-tools](https://github.com/mallexxx/xcode-editor-tools), pushed to `main` at `b4a839b92f60ec09cd33982014f4b593161d2673` on 2026-10-16 at the user's request. All 35 source files were audited for local/private details before publication; the initial commit uses GitHub's noreply identity. GitHub's exact SHA and public visibility were verified, and the local checkout is clean and tracks `origin/main`. Generated files remain locally excluded. The earlier `exp/buildServer.json` migration remains the existing intentional uncommitted change because that file was already tracked. No app-repository commits, upstream PRs or issues were created. The DuckDuckGo-owned fork and team/repository rollout described below remain proposed.
 
 Deployment paths, maintenance commands, verification evidence, publishing limitations and cache research: [[projects/vscode-migration/xcode-build-server]].