Admin data reached non-editors
In a signed-in test, an account with no editor rights opened /admin. The screen said "Not an editor", but the page source still carried the admin board data.
Why it was hard, what I decided, how AI helped
- Why it was hard
- The page looked correct. The check lived in a shared layout, and the Next.js App Router can still stream a page's data to the browser while the layout shows a refusal.
- My approach
- Launch waited on a written readiness pass that ended in a go/no-go verdict for Tim. A signed-in admin test with two disposable accounts was part of it.
- How AI helped
- Claude Code ran the browser test, read the page source, found the leak, and moved the editor check into the request guard.
- The decision
- Check editor status at the request, before any rendering, and answer 403. Never rely on a layout check alone.
- Evidence
- commit 481e418 · docs/16 section 2 · web/src/proxy.ts



