Fixly 0.3.0-dev - Windows build kit

This archive contains source code and build scripts, not a ready-to-run desktop app.

1. Extract the entire ZIP to a local directory, for example C:\FixlySourceKit.
2. Open scripts\build-windows-release.cmd.
3. The script downloads the official .NET SDK 10.0.100 if it is missing and restores NuGet packages.
   An Internet connection is required. Run this only on a development/test Windows x64 machine.
   Windows/WinUI native build prerequisites may be needed on a clean machine.
4. Wait for a successful build and tests. Logs are in installer\artifacts.
5. The resulting package is installer\artifacts\Fixly-0.3.0-dev-win-x64.zip.
6. Extract that package separately. Start START-SERVICE-TEST.cmd, then START-DESKTOP-TEST.cmd.
7. Click Check the system: Windows, architecture, logical processor count, uptime and
   system drive space should appear. Try cancellation and a repeated check.
8. Continue with WINDOWS-TEST-CHECKLIST.txt for enrollment, remote jobs, restart and offline
   recovery. Create the one-time code immediately before START-ENROLLMENT.cmd.

The build uses C:\FixlyBuild and C:\FixlyTools. C:\FixlyBuild\source and
C:\FixlyBuild\release are disposable build directories and are recreated by the script.
Do not put personal files in those directories. Do not run simultaneous builds.

The desktop app and service are unsigned developer binaries. The service runs as a console
process for this test; the production installer is not included.
The source already contains Increment 3A Agent enrollment and two signed read-only commands,
but they stay disabled by default. Once enrolled, Agent:Enabled=true sends heartbeat metadata
(Agent version, OS, architecture and capabilities). Agent:AllowRemoteDiagnostics=true
additionally permits results from the two allowed remote diagnostic commands.
LLM integration, artifacts and repairs remain future steps.
See docs\AGENT_RELEASE_CHECKLIST.md for backend readiness and enrollment instructions.

The release package includes COLLECT-FIXLY-DIAGNOSTICS.cmd. It creates a support ZIP with
versions, status, Fixly-only logs and connectivity checks. It deliberately excludes DPAPI
identity/challenge contents, the SQLite jobs database and CNG private key material. Review
PRIVACY-READ-BEFORE-SHARING.txt and every collected file before sharing the ZIP.

If the build itself fails, share these logs (inspect them for personal paths before sharing):
- installer\artifacts\build-0.3.0-dev-result.txt
- installer\artifacts\build-0.3.0-dev-output.txt
- installer\artifacts\build-0.3.0-dev-error-output.txt
- installer\artifacts\test-0.3.0-dev-output.txt
- installer\artifacts\test-0.3.0-dev-error-output.txt
