Usage page: review launcher
Dummy data from docs/handoff/fixtures. Never deployed.
For review
See the usage page as a customer would
Two steps. First choose who is looking at the page. Then open one of the five districts below. Each one starts where a customer starts: the link in their monthly email. Click View report to open their page.
Pick a district to view
Anything in red on the page is a note for testers, not part of the design. While testing, links into SLP and the admin portal open a red box that says where they would go, instead of leaving the page.
For context: the logic behind the page
For the team building it. The rules each screen follows, checks that the page matches the server, and every single state and account on its own. Links here also open as the person chosen in step 1.
Tier rules
What each tier changes on an account's page. Built from the same code and copy the page uses (CUView.bannerFor, js/cu-copy.js), so it can't drift. The tier itself is never shown to the admin. Rules: docs/handoff/FRONTEND-SPEC.md §4.5; open questions: docs/handoff/OPEN-QUESTIONS.md.
Self-test: the page against the server's rollup
The page does no rollup math (increment 2b). These checks render the overview from the server's answer and compare what's on screen with what was sent, and with hand-worked answers. The fixture answers are built by the server's own lib/payload.js (node scripts/build-fixtures.mjs). Runs on every load.
Against the running server
With CU_FIXTURES=1 node scripts/dev-proxy.js running, open this launcher at http://localhost:8080/index.html and check the live endpoint's rollup for three-accounts (the numbers in docs/handoff/2b-ADAPTER.md, "The self-test"). This signs this browser in as three-accounts.