Glossary

Watchtower Dentolize's planned internal management & subscription control plane — a tool for the Dentolize team to manage clinic accounts, distinct from the clinic-facing product. Not yet built; this PR is only its deploy-pipeline foundation.

WT-1 / XLZ-556 The Jira epic covering the real Watchtower application: a standalone Apollo + Express backend (GraphQL + REST edge), RBAC, 2FA, and audit logging, plus a web client. Full plan in Confluence, "Watchtower — Master Plan" (Docs 81264692).

Foundation branch This PR (feat/watchtower-foundation). A shared base branch the WT-1 developers fork their individual work from. Carries only the sandbox smoke-test scaffold described in this walkthrough — not marked for merge.

Smoke-test scaffold The two placeholder files this PR adds (packages/watchtower-server/index.js, packages/watchtower-web/public/index.html), used to validate that the sandbox pipeline can detect, build, route to, and report on a new packages/watchtower-* app pair before any real code exists. See Sandbox Smoke-Test Scaffold.

/health The route the sandbox container healthcheck polls to confirm watchtower-server is up. Returns plain text ok with HTTP 200.

Sandbox A temporary preview environment Dentolize's CI spins up per PR, with its own URL, database, and seeded users, so reviewers can click through a branch's changes live. Guarded, per the PR description, to only run the Watchtower apps when packages/watchtower-* directories exist — the same pattern used for the existing pharmacy package.