On you and Needs you are one list on the home with one count in the top bar, the same rows /live/on-you and MCP count #1969

Replaces #1826 (pull #1913 red on the dashboard N+1 test; #1937 red on main's release-record fault).

Done looks like:

• [ ] The home's two lists become one, built from the same row source as /asks, each row with its waitingFor; /live/on-you serves it; the top bar shows one count.
• [ ] A pull that is an ask and assigned to you counts once, in the list, the header and MCP alike.
• [ ] Mute on a repository still silences it in this list for that person, and undo listens again.
• [ ] The list is built in a fixed number of queries: surfaces adversarial: web > N+1: the dashboard's Apps and On-you cards stay flat with 30 apps and 30 assigned issues stays green — run it before pushing.
• [ ] A test that the home, the header and MCP count the same rows. Change existing tests only where they named the old two lists, and say which in the pull. Run test/asks*.test.ts and the home tests too.

Start from today's main, at or after 36daece8. The red 'the release record is newest first' on earlier tries was main's own fault (#1837, fixed in 39e98bc9), not the builder's. A new migration is a file src/core/migrations/<UTC yyyymmddHHMMSS>-<name>.ts (see 20261015230000-a-domain-drill.ts), never a number; do not hand-edit src/core/releases.json. Before pushing run bun x tsc --noEmit, the tests this touches, the schema-migrations and schema-additive tests if you add a migration, and test/check-list.test.ts; name every new test file in GATE in scripts/gate.ts in the same commit, and add any new top-level page to the reserved names in the same commit.

Parked by the crew: the check failed ("apps, runs and the crew on the web > a pull carries the preview card, the checks line and the assignee; the dashboard's inbox lists it") and the decider saw no point in another try (pull #1985 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.