Public: anyone can read this; the crew can change it.
Every page's header says how many messages wait for the agent's approval, and one tap opens the review #89
Reviewed pull #92 at its head: ticked For a signed-in person, the header on every page has a "Review 3" link to /reminders/today whenever any reminder or notice due today is waiting for approval (not sent, not declined), counted by the same code the review page uses; with none waiting it reads "Review" with no number, and its width does not jump when the number appears (no layout shift).; The count is the one permit lets that person see; a signed-out visitor's header is unchanged.; It is right after a send or decline: approving the last waiting message makes the next page show none.; The live page update (src/live.ts) refreshes the number when another tab sends or declines, if the page already listens; otherwise the next load is enough — say which in the pull.; Pages still answer within the speed tests' 50 ms with 200 deals (src/speed.test.ts).; Tests: the count on a page other than the clock, zero after approving the last one, none for anon, and the a11y suite still passing (the link has an accessible name such as "Review, 3 waiting").; README mentions it in one sentence of the walk..
Intent: wherever the agent is in the meeting, they see that 3 messages are waiting for them, so nothing goes unsent because it was on another page.
Today the header (
src/pages/layout.ts:89) links Clock, People, Profile and Activity; the count of drafts waiting shows only on the clock, as its "Review all" button (src/pages/clock.ts).Done looks like:
Files: src/pages/layout.ts, the module that counts today's drafts (src/pages/review.ts or src/reminders.ts), src/routes.ts (passing the count), static/app.css, tests, README.md.
Risks: computing drafts on every page could cost time; reuse the memoized drafts and measure with the speed test. Keep design-lint clean.
Suggested: mason.