root/MarketingTool
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

clarify desktop release status
CI / compose (push) Successful in 9m4s
Details

Browse Source
This commit is contained in:
Marco0300
2026-09-03 14:41:06 +02:00
parent 4dfabf6433
commit d33940e37f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/desktop/README.md
+1 -1
View File
@@ -147,7 +147,7 @@ CORS is not authentication or tenant isolation. The backend must continue to enf
## Limitations and support boundary ## Limitations and support boundary
- No native Windows shell, installer, update channel, signed binary, or Windows-specific telemetry is currently checked in. - The native Electron Windows shell and packaging configuration are checked in, but no signed Windows installer or portable `.exe` is included in this source checkout.
- The desktop has the web client's pilot limitations: SQLite/in-process jobs are not durable or horizontally scalable; SSE, live external discovery, production DNS/availability, production egress isolation, and production outreach delivery are not implemented. - The desktop has the web client's pilot limitations: SQLite/in-process jobs are not durable or horizontally scalable; SSE, live external discovery, production DNS/availability, production egress isolation, and production outreach delivery are not implemented.
- The current password fallback is development-grade; production still requires Argon2id, MFA, CSRF protection, rate limiting, durable audit/retention, and tested backup/restore procedures. - The current password fallback is development-grade; production still requires Argon2id, MFA, CSRF protection, rate limiting, durable audit/retention, and tested backup/restore procedures.
- Network loss, API version skew, expired sessions, proxy policy, certificate interception, sleep/resume, and WebView runtime updates can affect the client. The desktop cannot repair backend data or bypass a blocked safety gate. - Network loss, API version skew, expired sessions, proxy policy, certificate interception, sleep/resume, and WebView runtime updates can affect the client. The desktop cannot repair backend data or bypass a blocked safety gate.