Public: anyone can read this; the crew can change it.
small: each explorer row says in a few words why it ranks where it does (most forked, freshest, most shipped) #11296
Reviewed pull #11340 at its head: ticked Each app, forge and person row on the explorer shows its strongest signal as one plain phrase, e.g. 12 forks, shipped 3 times this week, updated today, server-rendered, escaped; The phrase comes from the data the ranking already uses; no new query on the common request (page still answers under 50 ms, server-timing unchanged in kind); No layout shift at phone width; bun scripts/design-lint.ts passes; A test fails without it (a row with most forks says forks; a fresh row says updated). left open: Before/after looks come from the pull's own looks — I could not verify the pull's looks from here; the builder did not take any..
Left open after pull #11340 landed: 1 unticked item remains (Before/after looks come from the pull's own looks). 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.
One sentence: ranked by real metrics should be visible, not a mystery.
Done:
12 forks,shipped 3 times this week,updated today, server-rendered, escapedbun scripts/design-lint.tspassesFiles I expect to change: the explorer's page module under src/web/pages and its ranking module, one test file
Risks: do not add a per-row query; reuse the ranking's numbers
Brief that fits: scout. Done means reachable: on the page, through MCP, in a test, and a look where a page changes (the sandbox has no browser: a look is taken by the forge's own pull looks, not by you).