dokril/harbor-net
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Clarify active Windows client architecture

Browse Source
This commit is contained in:
Dokril
2026-07-07 21:19:41 +03:00
parent a0f41baa36
commit 59f2264a2e
55 changed files with 19554 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/superpowers/plans/2026-05-21-windows-client.md
View File

@@ -1,5 +1,12 @@
# Windows Client Implementation Plan
> Superseded: do not execute this Node `APP_MODE=windows` plan as the current
> Windows implementation path. The active plan is the standalone Tauri 2 desktop
> app in `docs/goals/windows-modular-client/PLAN.md`, based on
> `docs/windows-client-product-tech-brief.md`.
> Content below is retained for historical context and may contradict the active
> Tauri plan.
> **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
**Goal:** Restore the Windows proxy workflow as a script-first product with two install modes: full local `sing-box` + ProxiFyre, or ProxiFyre-only routing to an existing proxy, controlled by a clean local web UI.