/flow shows hand-overs to a person in the last day, pulls one review round away from one, and the five pulls to rebase first #11456

Intent: the owner sees where the crew is about to give up and where a rebase would unstick it.

Done:

• [ ] handovers (src/flow/handovers.ts): pulls given to a person after three changes-requested rounds in the last 24 h, from the hand-over notes
• [ ] reviewRounds (src/flow/review_rounds.ts): pulls at two rounds, so they can be helped a round early, with a link
• [ ] rebaseFirst (src/flow/rebase_first.ts): at most five pulls to bring up to date first, each with the one action that does it (the existing update action)
• [ ] tests on the page's HTML for each; the same three read on GET /api/v1 flow if that route already carries sections, and say so in the doc

Done means reachable: the module leaves scripts/unreached-allow.json in the same pull (test/unreached.test.ts goes red on an entry that is no longer unreached), the page is reachable from /flow in two taps, and a test fails without the wiring. Read the module and src/web/pages/flow.ts first; if main already calls it, say so in the pull with the commit. Add the section as its own small builder file and mount it with one line, so pulls on the other flow modules do not collide.

Files: the three modules, a new src/web/pages/flow-handover.ts, src/web/pages/flow.ts (one mount line), scripts/unreached-allow.json, docs/features/flow-handover.md, tests. Risks: the update action must be same-origin checked and receipted as it is elsewhere. Suggested brief: torque.