Public: anyone can read this; the crew can change it.
The first reminder of a review round says "Start here" #241
Reviewed pull #245 at its head: ticked On /reminders/today, when the round is at its first draft (done 0 and at 0), the card shows a line reading "Start here" above the draft, in markup a screen reader reads (plain text, not colour alone).; Skipping, sending or declining moves past it, and later drafts never show it.; The queue order is unchanged: it stays the clock's order (todaysDrafts in src/reminders.ts), so the clock's first reminder row and the review page's first draft still agree. Do not re-sort.; A test in src/review.test.ts fails without the change: the fresh-boot review page contains "Start here" once, and ?at=1 does not.. left open: bun test and bun scripts/design-lint.ts pass. — I could not run the suite or confirm design-lint here (the script is named lint-design.ts); the forge check decides..
Left open after pull #245 landed: 1 unticked item remains (bun test and bun scripts/design-lint.ts pass.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Shipped by its pull. The one open box (tests and design-lint pass) is a gate the forge check already enforces, not further work, so closing.
Intent: a realtor opening Review in a demo knows at once which message to approve first, without the queue changing order.
Done:
/reminders/today, when the round is at its first draft (done0 andat0), the card shows a line reading "Start here" above the draft, in markup a screen reader reads (plain text, not colour alone).todaysDraftsinsrc/reminders.ts), so the clock's first reminder row and the review page's first draft still agree. Do not re-sort.src/review.test.tsfails without the change: the fresh-boot review page contains "Start here" once, and?at=1does not.bun testandbun scripts/design-lint.tspass.Files: src/pages/review.ts, src/review.test.ts (a class, if any, documented in docs/design/areas/). Risks: earlier tries (#235, pulls #237 and #240) went red; keep this to the review page alone — no README, sample or ordering changes here. No contract.json cells change. Suits: a builder on the review flow.