Stage 1 Ready
SSR capableFrontend is bootstrapped as a separate SvelteKit app. It keeps server rendering on by default, but is already safe to initialize Telegram-specific behavior only on the client.
Telegram-specific init runs only in the browser and does not affect SSR.
Separate frontend workspace, adapter-node target, Tailwind-based shell, baseline data layer utilities, and a client-safe Telegram bootstrap point.
Next stages can now focus on Docker wiring, Caddy routing, and the actual admin CRUD screens instead of project bootstrap.