Add right-click Remove from sidebar for projects

[jonathanKingston]

Summary

• Right-clicking a project row in the sidebar opens a context menu with Remove from sidebar
• Removal only updates the app's project list / activeProjectId in config — it does not delete workspace files or thread-store data on disk
• Removing the active project switches to another open project (or clears the workspace UI if it was the last one)

Visual eval

Context menu on Project B
After remove — only Project A remains

CI fix

e2e (3) failed with Electron Killed / invalid session id (OOM). Root cause: adding project-remove-sidebar.e2e.ts shifted WDIO --shard 3/3 boundaries so heavy project-switch-panels.e2e.ts moved onto shard 3. The new visual eval itself had already passed on shard 2. Renamed the spec to projects-remove-sidebar.e2e.ts so it sorts after project-switch-panels and restores the prior shard load.

Test plan

• Unit tests for removeProject (inactive, active→switch, last project)
• Component test: contextmenu opens menu; clicking remove drops the row
• E2E: tests/e2e/projects-remove-sidebar.e2e.ts (menu + after screenshots)
• npm test / focused e2e passed locally
• CI e2e shards green after rename

_{To show artifacts inline, enable in settings.}

  

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[github-actions]

Merge conflict needs a human

main advanced and screenshot conflicts were resolved automatically, but these non-screenshot files conflict and can't be auto-merged. Resolve them by hand (merge or rebase main):

• docs/ui-taste.md
• src/renderer/views/projects-pane.ts

[jonathanKingston]

Heads-up: this branch has merge conflicts with current main (post #991/#992/#999 CI fixes + roadmap changes). The e2e instability that was failing CI here is addressed on main — after resolving conflicts and updating, CI should be meaningfully greener. Conflicting areas: source files (not just screenshots), so resolving needs feature context.

[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_7300e902-3a35-4370-87dd-b5ad97c9a2dd)

[cursor]

Not approving: Cursor Bugbot completed as skipped (usage limit), so automated review did not run. Human review is needed before merge; requested AutomatedTester.

  

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