[Desktop] Remote Control sessions are grouped under 'Other' instead of their project in the sidebar

Description

Sessions created through a Remote Control environment are filed under the "Other" group in the desktop app sidebar, instead of the project group that matches the environment's project.

Environment

• Host (machine A): macOS, Claude Code CLI 2.1.215, running claude remote-control from the project directory ~/Documents/jaronywork, spawn mode = same-dir
• Client (machine B): Claude Code desktop app, macOS, same account
• Desktop app on host: 2.1.209

Steps to reproduce

1. On machine A, run claude remote-control from a project directory (e.g. ~/Documents/jaronywork), choose spawn mode same-dir.
2. On machine B (same account), open the desktop app → environment picker → Remote Control → select the host environment (shown as "jaronywork · mac").
3. Create a new session and send a prompt.

Expected

The new remote session appears under the "jaronywork" project group in the sidebar — the environment itself is named after the project, and a "jaronywork" group already exists in the sidebar.

Actual

The session is grouped under "Other".

Inconsistency: another session of the same remote environment (mac-expressive-quail, apparently the host-side attached session) is grouped under "jaronywork". So two sessions of the same remote environment end up in different sidebar groups.

Impact

Cosmetic only — verified on the host that the remote session's cwd is the correct project path and edits land in the real working tree. But it is confusing: the user's first reaction was to doubt whether the remote session was actually operating on the intended project at all.

Suggested behavior

Group remote-control sessions by their environment's project (or give each remote environment its own sidebar group), instead of falling back to "Other" when no local folder mapping exists on the client machine.