Live Console
Run the battle route.
Keep the launch surface light.
`/play/console` now owns the heavy interactive surface: training, live rooms, PvP, custody tooling, and deck iteration. The launch page stays lean so the entry path is fast and the console pays its cost only when you actually open it.
Route split
`/play` is now the launch and route-selection surface.
`/play/console` is the live interactive surface for rooms, deck work, and PvP state.
`/playbook` keeps deterministic replay notes, fixtures, and engine planning off the critical path.
Deferred live workspace
Keep the console shell light
until you need live state.
The heavy training board, battle renderer, PvP rail, and room state now stay dormant until you explicitly open the workspace. That keeps the console landing path from paying the bootstrap and runtime cost before you actually need it.
Startup
No workspace mount and no `/api/play/bootstrap` fetch until you open the console.
Live board
Training, PvP, authored actions, and replay controls stay behind the workspace boundary.
Metrics
Deep links and explicit open actions still go straight into the live workspace when they include launch intent.
Launch surfaces
Keep launch, console,
and playbook separate.
This split keeps the fast entry path from paying the cost of the heavy console, while the console itself still keeps the operational and PvP branches folded until they are needed.