main=4b758f49ec52ab58a0bd9647e28c9e2911945c88 pr_head=900742ddd8e3c4f63af1cbcda9b28ae3cbdccd41 fix=6b47939e606b17fc6fab278eec3fcbde65995514 fix_parent=2d689687f57acafe1b85cbc9d82583ea66d2d0fc PASS issue #36424 (the bug this PR fixes) is closed as completed by merged PR #36433 PASS #36433 is on main as 6b47939e60 (fix(mobile): thread list project filter lists recently active projects first (#36433)); the PR branch predates it PASS #36433 touched exactly the three filter surfaces this PR changes: apps/mobile/src/features/home/HomeRouteScreen.tsx apps/mobile/src/features/home/HomeScreen.tsx apps/mobile/src/features/threads/ThreadNavigationSidebar.tsx PASS HomeRouteScreen.tsx: filter options are pickableProjectGroups(sortHomeProjectScopes(..., "updated_at")) at 6b47939e60; unsorted pickableProjectGroups(projectScopes) at its parent PASS HomeScreen.tsx: filter options are pickableProjectGroups(sortHomeProjectScopes(..., "updated_at")) at 6b47939e60; unsorted pickableProjectGroups(projectScopes) at its parent PASS ThreadNavigationSidebar.tsx: filter options are pickableProjectGroups(sortHomeProjectScopes(..., "updated_at")) at 6b47939e60; unsorted pickableProjectGroups(projectScopes) at its parent PASS at 6b47939e60 the filter passes the same sortHomeProjectScopes arguments as the new-task project picker the issue asks it to match ✓ |@t3tools/mobile (unit)| src/features/home/prove-pr-36432.test.ts > PR 36432 claim > fix call sites: filter options are ordered by most recent thread activity, pinned first 1ms ✓ |@t3tools/mobile (unit)| src/features/home/prove-pr-36432.test.ts > PR 36432 claim > parent call sites: filter options ignore recent activity 0ms Tests 2 passed (2) PASS at 6b47939e60, the PR's fixture through the call-site expression lists gamma, alpha, beta (beta first when pinned), the PR's own expected orders; the parent's expression does not VERDICT: already-fixed by #36433 (6b47939e60); PR #36432 can be closed