Clarify active Windows client architecture

This commit is contained in:
2026-07-07 21:19:41 +03:00
parent a0f41baa36
commit 59f2264a2e
55 changed files with 19554 additions and 8 deletions

View File

@@ -0,0 +1,16 @@
# Goal: Windows Tauri Proxy Client
Use Krypton Execution to execute `docs/goals/windows-modular-client/PLAN.md`.
Core rules:
- Treat `PLAN.md` as the source plan.
- Preserve intent, ownership, contract, cutover, evidence, and kill criteria.
- Build a separate Tauri 2 Windows desktop app under `apps/windows-client`.
- Do not implement Windows by extending the current Node gateway/client server.
- Keep Control App, Proxyfier Layer, and Local sing-box separately installable and operable.
- Make external proxy target + ProxiFyre profile apply the MVP.
- Keep Local sing-box optional; it must not be required for external target profiles.
- Keep generated ProxiFyre and sing-box configs derived from source models.
- Capture acceptance evidence from the target user's perspective and record it in `EVIDENCE.md`.
- Say "implemented but unproven" if Windows-only privileged evidence cannot be captured.