mirror of
https://github.com/NanmiCoder/cc-haha
synced 2026-07-16 13:03:31 +08:00
8b5de63ae9
The desktop docs now explain the intended H5 setup path for personal and team use: enable H5 in Settings, generate a one-time token, configure allowed origins, and use LAN or a reverse proxy to open the mobile browser chat surface. Constraint: H5 is opt-in browser access, not a public multi-tenant auth system. Rejected: Hide the setup details in the implementation spec only | users need operational guidance for token handling, CORS, and reverse proxy routing. Confidence: high Scope-risk: narrow Directive: Keep this page aligned with Settings labels and the token/CORS behavior before documenting broader public hosting. Tested: bun run check:docs Tested: Live local smoke with temporary HOME: /health 200, H5 verify without token 401, H5 verify with token 200, configured Origin echoed by CORS.