On this page
1. The Watchtower web landing page2. The Watchtower API health check3. The Watchtower API landing routeWhat's not here yetWalkthrough
Everything below was captured from the live sandbox for this branch (feat-watchtower-foundation). There is no login flow to show yet — the scaffold has no authentication — so this is a tour of the two routes that exist today: the web landing page and the API's two routes.
1. The Watchtower web landing page
Visiting the Watchtower web URL renders a single static page — no JavaScript, no data fetching, nothing clickable.

The page's own copy is the most accurate description of its purpose: it tells the reader outright that this is a placeholder and names the real epic (WT-1 / XLZ-556) that replaces it.
2. The Watchtower API health check
The backend's /health route returns a plain-text ok. This is the route the sandbox container healthcheck polls to decide the service is up.

3. The Watchtower API landing route
Every other path on the API returns the same small JSON payload — there's no routing table, just a health check and a catch-all.

What's not here yet
There is no sign-in screen, no dashboard, no data of any kind — the "same shared credentials + 2FA as the Dashboard/Admin" line on the landing page describes a plan for WT-1, not something wired up in this branch. If you're looking for the actual product screens, they don't exist yet; check back once the WT-1 epic branches land.