[codex] Group project scopes in mobile thread lists

[juliusmarminge]

Why

Mobile thread lists treat copies of the same repository in different environments as unrelated projects. Selecting one project can therefore hide threads from the other copy.

Root cause

Mobile list filtering accepts one physical project reference, while project presentation is expected to operate on logical repository groups.

Fix

• derive logical project scopes for the mobile home screen
• filter threads and pending tasks by every member project reference
• allow Thread List v2 to accept multiple project references
• preserve grouped sorting and stale duplicate references

Settings placement and startup preference behavior are intentionally excluded from this PR.

Verification

• targeted formatting and lint
• vp run --filter @t3tools/mobile typecheck
• focused mobile grouping and Thread List v2 tests — 22 tests passed

Note

Group project scopes by repository identity in mobile thread lists

• Introduces buildHomeProjectScopes and sortHomeProjectScopes in homeThreadList.ts to consolidate duplicate projects across environments into logical groups, sorted by recent thread/task activity.
• Updates buildThreadListV2Items in threadListV2.ts to accept an array of projectRefs instead of a single ref, enabling multi-environment project filtering.
• Updates the home screen and thread navigation sidebar to select and filter by logical project scopes rather than individual projects, with empty states reflecting the selected scope title.
• Behavioral Change: thread and pending-task filtering now matches any projectRef within the selected logical scope, so selecting a project may include threads from multiple environments.

^{Macroscope summarized c71bc86.}

---

Note

Medium Risk
Changes core list filtering and grouping logic for home/sidebar/v2 paths; behavior is well covered by new tests but wrong scope resolution could hide or mis-attribute threads.

Overview
Mobile home and sidebar thread lists now treat logical project groups (same repo across environments, including stale duplicate project IDs) as one filter scope instead of a single physical project ref.

buildHomeProjectScopes and sortHomeProjectScopes in homeThreadList.ts derive grouped scopes with merged projectRefs, reuse them in buildHomeThreadGroups, and improve new-thread target resolution when threads still point at stale project IDs.

HomeScreen and ThreadNavigationSidebar build project filter options from scopes, match selection by scope key or any member ref, and scope v1/v2 threads and pending tasks across all refs. Empty states use the group title.

Thread List v2 takes projectRefs (array) instead of one projectRef, so filtering includes every environment copy in the group.

^{Reviewed by Cursor Bugbot for commit c71bc86. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 0d2b0e7e-4d19-4920-a5c3-3910df1de4dc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/mobile-grouped-project-scopes

---

_{Comment @coderabbitai help to get the list of available commands.}

[macroscopeapp]

Approvability

Verdict: Needs human review

This PR introduces new project grouping functionality that merges projects across environments by repository identity, changing how thread lists are filtered and displayed. The scope of new logic and runtime behavior changes warrants human review.

^{You can customize Macroscope's approvability policy. Learn more.}

[cursor]

Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.

^{Bugbot Autofix is ON, but a cloud agent failed to start.}

^{Reviewed by Cursor Bugbot for commit 7e09d54. Configure here.}