client_jaminator

<!-- GSD:project-start source:PROJECT.md -->
## Project

**Jaminator**

Jaminator is a single-EXE Windows maintenance tool that Jam Coding deploys onto every laptop in its fleet of school-classroom laptops. Configuration lives in a GitHub-hosted JSON manifest (`manifest/manifest.json`), so program installs, cleanup rules, wallpaper, folder layout, and arbitrary PowerShell tasks can be updated for the entire fleet without redeploying the EXE. Two run modes coexist in one binary: a silent login-mode scheduled task that enforces folders + wallpaper at every logon, and an interactive WinForms UI a technician opens to trigger disruptive work (cleanup, program installs, ad-hoc commands).

**Core Value:** A technician can change behaviour on every school laptop by editing one JSON file in GitHub — no MSI redeploy, no per-machine login, no manual rollout.

### Constraints

- **Tech stack**: .NET Framework 4.8 / C# / WinForms / WiX Toolset v4 — locked by existing codebase; this milestone touches only WiX (`installer/installer.wxs`, `installer/UpdateCheck/`) and possibly the build script (`installer/build.ps1`).
- **Target platform**: Windows 7 SP1+ baseline via `net48`, with the actual fleet on Windows 10 / 11 64-bit; install must work via double-click on Win10 and Win11 (the canonical technician deployment path).
- **Deployment**: GitHub Releases — the hotfix ships as a tagged GitHub release with the rebuilt MSI as an asset; downstream `SelfUpdater` will pick it up on first launch of v0.7.4 instances.
- **Build environment**: .NET SDK 8+ + WiX 4 CLI installed locally; build is `ins…

## Entry Points
- Location: `src/Jaminator/Program.cs`, method `Main(string[] args)`
- Triggers: User double-click (no args), scheduled task (`--login-mode`), scripts (`--run-all`, `--install`), etc.
- Responsibilities:
- Location: `bootstrap/Program.cs`, method `Main()`
- Triggers: End user runs `Jaminator-Setup.exe` for the first time
- Responsibilities:
- Location: `installer/installer.wxs`
- Triggers: Windows Installer during install/upgrade/uninstall
- Responsibilities:
- Trigger: Every user logon
- Action: Run `C:\Program Files\Jaminator\Jaminator.exe --login-mode`
- Result: Headless execution of folders + wallpaper only
- Trigger: Daily at time specified in `manifest.schedule.dailyRunAll`
- Action: Run `C:\Program Files\Jaminator\Jaminator.exe --run-all`
- Result: Headless execution of all sections (if internet available)
## Architectural Constraints
- **Threading:** Single-threaded event loop (WinForms on UI thread); services use `async/await` with `Task.Run()` to avoid blocking UI during long operations (downloads, installs, PowerShell). No thread pool or concurrent section execution.
- **Global state:** Logger instance created per-run; Manifest fetched once per app start and passed to services. No module-level singletons beyond Logger. State.json is the only persistent key/value store.
- **Circular imports:** None detected. Dependency graph is acyclic: UI → Services → Models → System APIs.
- **Process elevation:** Entire EXE runs elevated (via UAC prompt or scheduled task as SYSTEM). No privilege boundaries within the process. No subprocess elevation calls needed.…