Sign in with Telegram
Use the same Telegram account you use with the FastVPN bot. This slice now creates pre-auth continuity, exposes session status, and tells the truth when Telegram verification is not configured yet.
This screen is scaffolded for layout, navigation, and product tone. Real data contracts still need a backend/BFF layer.
Pre-auth continuity
Promo, invite, referral, hidden-tariff, and return-path state can now be parked in a short-lived pre-auth session instead of being left dangling in the URL.
Telegram-first start
The backend issues one-time login attempts for Telegram-first auth and keeps the auth surface disabled, not fake, until secrets exist.
Logout and session status
The login screen can read the current authenticated session summary and revoke the web session cookie cleanly.
Telegram verification is configured. The remaining work is wiring the real widget/browser handoff for production UX.
No authenticated cookie exists yet.
This starts the honest auth flow shape: create or refresh pre-auth context, mint a one-time attempt, and expose whether Telegram verification is actually available.