Remove Docker and container references from FieldWorks build system

This commit removes all Docker and container-related artifacts and references from the FieldWorks codebase. The changes include:

- Deleted Docker-specific files: Dockerfile.windows, .dockerignore, and Docker build workflow
- Removed Docker-related scripts and documentation including Build/Agent/Docker/ folder
- Eliminated container-specific build logic and environment variables
- Removed references to DOTNET_RUNNING_IN_CONTAINER, FW_CONTAINER, and related conditional code
- Cleaned up Vagrant references while preserving the vagrant/ directory structure
- Updated build scripts and configuration files to remove container-specific paths and logic
- Removed agent-container related references from documentation and specs
- Updated project documentation to reflect the removal of container builds

This cleanup ensures that the build system only uses native Windows build processes and removes all container-specific dependencies and configurations that were never fully implemented or used in production.

Author: johnml1135

.GitHub/agents/speckit.implement.agent.md

@@ -63,7 +63,6 @@ You **MUST** consider the user input before proceeding (if not empty).
      git rev-parse --git-dir 2>/dev/null
      ```
 
-   - Check if Dockerfile* exists or Docker in plan.md → create/verify .dockerignore
    - Check if .eslintrc* exists → create/verify .eslintignore
    - Check if eslint.config.* exists → ensure the config's `ignores` entries cover required patterns
    - Check if .prettierrc* exists → create/verify .prettierignore
@@ -91,7 +90,6 @@ You **MUST** consider the user input before proceeding (if not empty).
    - **Universal**: `.DS_Store`, `Thumbs.db`, `*.tmp`, `*.swp`, `.vscode/`, `.idea/`
 
    **Tool-Specific Patterns**:
-   - **Docker**: `node_modules/`, `.git/`, `Dockerfile*`, `.dockerignore`, `*.log*`, `.env*`, `coverage/`
    - **ESLint**: `node_modules/`, `dist/`, `build/`, `coverage/`, `*.min.js`
    - **Prettier**: `node_modules/`, `dist/`, `build/`, `coverage/`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`
    - **Terraform**: `.terraform/`, `*.tfstate*`, `*.tfvars`, `.terraform.lock.hcl`

.dockerignore

@@ -125,7 +125,6 @@ def index_repo_files(root: Path):
             "Obj",
             "Output",
             "Downloads",
-            "vagrant",
         }:
             continue
         for f in filenames:

.github/check_copilot_docs.py

@@ -22,7 +22,6 @@ See `.github/AI_GOVERNANCE.md` for the documentation taxonomy and “source of t
 
 ## Build & Test Essentials
 - Prerequisites: install VS 2022 Desktop workloads, WiX 3.14.x (pre-installed on windows-latest), Git, LLVM/clangd + standalone OmniSharp (for Serena C++/C# support), and optional Crowdin CLI only when needed.
-- Docker is available for clean-slate reproduction if needed (see `DOCKER.md`), but standard development uses VS Code worktrees on the host.
 - Verify your environment: `.\Build\Agent\Verify-FwDependencies.ps1 -IncludeOptional`
 - Common commands:
   ```powershell

.github/copilot-instructions.md

@@ -13,7 +13,7 @@ description: "PowerShell best practices for scripts used in FieldWorks (dev scri
 - Use `pwsh`/PowerShell Core syntax where possible and `Set-StrictMode -Version Latest`.
 - Use `Write-Host` sparingly; prefer `Write-Output` and `Write-Error` for correct streams.
 - Use `-ErrorAction Stop` in helper functions when errors should abort execution.
-- **No Unicode icons or emojis** in output messages (e.g., `✓`, `✗`, `⚠`, `🔧`). Use plain ASCII text like `[OK]`, `[FAIL]`, `[WARN]`, `ERROR:` instead. Unicode causes encoding issues in Docker containers and CI logs.
+- **No Unicode icons or emojis** in output messages (e.g., `✓`, `✗`, `⚠`, `🔧`). Use plain ASCII text like `[OK]`, `[FAIL]`, `[WARN]`, `ERROR:` instead. Unicode causes encoding issues in CI logs.
 
 ## Security
 - Avoid embedding secrets in scripts; read from env vars and prefer platform secret stores.
@@ -29,7 +29,6 @@ description: "PowerShell best practices for scripts used in FieldWorks (dev scri
 - Pipes (`|`)
 - Semicolons (`;`) or `&&`
 - Redirection (`2>&1`)
-- Nested quotes in `docker exec`
 
 **ALWAYS use `scripts/Agent/` wrapper scripts for these operations.** Do not attempt raw commands.
 

.github/instructions/powershell.instructions.md

@@ -11,7 +11,6 @@ Provide clear, concise, and enforceable rules that help Copilot code review and
 
 ## Rules (high-impact, short)
 - Prefer the repository top-level build (`.\build.ps1`) and solution (`FieldWorks.sln`) for full builds.
-- Do not change COM/registry behavior without explicit tests and a plan for containerized runs (see `scripts/spin-up-agents.ps1`).
 - Keep localization consistent: use `.resx` and follow `crowdin.json` for crowdin integration.
 
 ## Examples (Quick)

.github/instructions/repo.instructions.md

@@ -7,12 +7,11 @@ description: "FieldWorks testing guidelines (unit/integration)"
 
 ## Purpose & Scope
 Guidance for writing and running deterministic unit and integration tests for FieldWorks.
-**CRITICAL**: Always use the provided PowerShell scripts (`test.ps1`, `build.ps1`) to run tests. These scripts handle containerization, environment setup, and dependency management automatically.
+**CRITICAL**: Always use the provided PowerShell scripts (`test.ps1`, `build.ps1`) to run tests. These scripts environment setup, and dependency management automatically.
 
 ## Core Rules
 1.  **Always use scripts**: Never run `vstest.console.exe`, `nmake`, or `msbuild` directly for testing unless debugging the build system itself.
-2.  **Containerization**: The scripts automatically detect if you are in a worktree and respawn inside the Docker container. This is required for COM/Registry isolation.
-3.  **Build First**: Ensure tests are built before running. `test.ps1` builds by default unless `-NoBuild` is passed.
+2.  **Build First**: Ensure tests are built before running. `test.ps1` builds by default unless `-NoBuild` is passed.
 
 ## Running Tests (Managed)
 
@@ -64,7 +63,7 @@ Tests are built automatically by `test.ps1`. To build explicitly without running
 The testing infrastructure relies on shared PowerShell modules for consistency:
 -   **`test.ps1`**: Main entry point. Dispatches to VSTest (managed) or `Invoke-CppTest.ps1` (native).
 -   **`scripts/Agent/Invoke-CppTest.ps1`**: Backend for native C++ tests (MSBuild/NMake).
--   **`Build/Agent/FwBuildHelpers.psm1`**: Shared logic for container detection, VS environment, and process cleanup.
+-   **`Build/Agent/FwBuildHelpers.psm1`**: Shared logic for VS environment, and process cleanup.
 
 ## Debugging & Logs
 -   **Logs**: Build logs are written to `Output/Build.log` (if configured) or standard output.
@@ -77,7 +76,6 @@ The testing infrastructure relies on shared PowerShell modules for consistency:
 -   **Determinism**: Tests must be hermetic. Avoid external state.
 
 ## Troubleshooting
--   **"Class not registered"**: You are likely running outside the container. Use `.\test.ps1`.
 -   **"File not found"**: Ensure you built with `-BuildTests` (or let `test.ps1` do it).
 -   **Native Crash**: Native tests are fragile. Use `printf` debugging if the debugger is unavailable.
 

.github/instructions/testing.instructions.md

@@ -24,21 +24,6 @@ msbuild Build\Src\NativeBuild\NativeBuild.csproj /p:Configuration=Debug /p:Platf
 **Cause**: Build order not respected
 **Solution**: Use traversal build (`.\build.ps1`) which respects `FieldWorks.proj` phases
 
-## Container/Worktree Issues
-
-### Agent Worktree Build Fails on Host
-**Symptom**: COM/registry errors when building `worktrees\agent-N` paths
-**Cause**: Agent worktrees require containerized builds
-**Solution**:
-```powershell
-docker exec fw-agent-N powershell -NoProfile -c "msbuild FieldWorks.sln /m /p:Configuration=Debug"
-```
-
-### Container Can't Access NuGet Packages
-**Symptom**: Package restore fails inside container
-**Cause**: Volume mounts or network issues
-**Solution**: Check `scripts/spin-up-agents.ps1` for proper mount configuration
-
 ## Test Issues
 
 ### Tests Fail with "SIL.FieldWorks" Assembly Errors

.github/workflows/docker-build-publish.yml

@@ -4,4 +4,4 @@
 - Tech stack: predominantly C#/.NET Framework 4.8 managed code, plus native C++/C++-CLI components, WiX installer assets, PowerShell/bash build scripts, and auxiliary Python tooling. Builds rely on MSBuild traversal (`FieldWorks.proj`).
 - Structure highlights: Src/ contains applications and libraries (with per-folder COPILOT.md docs). Build/ houses shared targets/scripts, FLExInstaller/ contains WiX artifacts, Include/ + Lib/ host native headers/libs, and Build/Agent scripts support worktree automation. Specs/ and Docs/ provide planning/reference material.
 - Key guidelines: Follow `.github/instructions/*.instructions.md` (build, managed, native, installer, testing). Respect `.editorconfig`, update COPILOT metadata when touching folders, and keep documentation in sync with code.
-- Tooling environment: development happens on Windows with Visual Studio 2022 workloads (Desktop .NET + C++), WiX 3.14.x, and optional Dockerized worktrees (fw-agent-* containers).
+- Tooling environment: development happens on Windows with Visual Studio 2022 workloads (Desktop .NET + C++), WiX 3.14.x.