Below the ranked rows, the crew picks in the order Next up shows, so the page is the truth #8826

Left out of #8694 (pull #8710, 2a83216f): ranked issues are picked strictly from the top, but below them the picker keeps its own order, so the next unranked issue it starts can differ from the one /next shows.

Done looks like:

• [x] One function in src/core/next_up.ts gives the whole order, ranked rows and then the unranked tail, and both /next and the picker read it. No second ordering remains.
• [x] A test: with two ranked issues and three unranked ones, the order of starts over five ticks equals the page's rows, top to bottom.
• [x] The MCP next_up answer lists the same order.

Files: src/core/next_up.ts, src/crew/small_share.ts, src/web/pages/next.ts, test/next-up.test.ts Risks: speed. The picker runs every tick, so the order must stay one indexed query, not a per-issue scan.

Reviewed pull #8840 at its head: ticked One function in src/core/next_up.ts gives the whole order, ranked rows and then the unranked tail, and both /next and the picker read it. No second ordering remains.; A test: with two ranked issues and three unranked ones, the order of starts over five ticks equals the page's rows, top to bottom.; The MCP next_up answer lists the same order..