Organize browser journeys by product area

[nicksan222]

Summary

• Group browser specs under apps/web/e2e/{auth,chat,group,ideas,issues,trips,workspace}.
• Split the larger ideas suite into activities, planning, and review.
• Pure file moves: no test assertions, runner settings, or coverage changes.

Validation

• just check and bun run format:check pass.
• Playwright lists 15 + 10 + 12 + 12 = 49 tests across four shards (unchanged total).
• git diff --cached --check passed before commit.
• CI will verify the new shard distribution on isolated backends.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_ac089304-1945-4dec-a9ff-b014fee2921f)

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-28T09:07:59.795404Z	edc6c15	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[cursor]

Approved: Cursor Bugbot was skipped (usage limit), so that signal was ignored, and no approval policy required human review. These are rename-only e2e spec moves with no assertion or runner changes. No reviewers were assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}