Admin developer tools: evals and Atlas in the shared page wrapper
Board row p11-page-admin-dev, screen-rule gaps G16 and G19. The evals page now sits in the app's standard page width and gutter, and the Atlas loading frame is the page's own wrapper.
28 Sept 2026 · branch p11-admin-1 · captured against propflow-stage · at 779e12f792+local
Details
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · Evals at a wide screen: the standard width, not edge to edge
Before this change the evals page body was a bare p-6 box with no width cap, so on a 1600 px screen its heading and tab row ran to the far edge while every other admin page stopped at the standard width. It now sits in PageBody: the heading's left edge lines up with the other admin pages, and the loading shell uses the same frame so nothing jumps when data lands.
Asserted in the captured DOM — Agent evals · Overview. The real page heading and its first section tab are on screen.
2 · Atlas: the page's wide wrapper (loading frame now matches it)
The Atlas page already used PageBody variant="wide"; only its loading frame kept an older 1600 px cap, so on wider screens the loading frame was narrower than the page. The loading frame now renders the same wrapper. The loading moment itself lasts a fraction of a second, so the pinning test in the PR (which renders the loading component and reads its classes) is the proof for that frame; this capture shows the page it must match.
Asserted in the captured DOM — Atlas. The Atlas page heading is on screen.
