[Bug]: Sidebar repository grouping splits Conductor-created fork-only clones

[felixleopold]

Summary

Repository grouping in the sidebar splits checkouts of the same working repository when a checkout created by Claude Conductor does not include the upstream remote.

Observed

The sidebar shows a standalone felixleopold-t3code project for the Conductor-created Claude thread, while the existing T3 Code checkouts are grouped under pingdotgg/t3code.

On this host:

Checkout	Remotes	Sidebar identity
/srv/nas_share/conductor/t3-projects/felixleopold-t3code (created by Claude Conductor)	origin = git@github.com:felixleopold/t3code.git	felixleopold-t3code
/srv/nas_share/t3code-src	same origin plus upstream = git@github.com:pingdotgg/t3code.git	pingdotgg/t3code
/srv/nas_share/t3code-sync	same origin plus upstream	pingdotgg/t3code

The logical-project grouping therefore treats the Conductor clone as a different repository even though it is the same fork/repository being used by the other checkouts.

Expected

Projects that refer to the same repository/fork should be combined in the sidebar regardless of whether a particular clone has an upstream remote configured. This used to appear to work before the Conductor-created project path was introduced.

Suspected area

The canonical repository identity currently appears to be selected from the remotes available in each individual checkout. A clone with only origin resolves to the fork identity, while clones that also have upstream resolve to upstream. Please check both:

1. Whether Claude Conductor should preserve/add the upstream remote when creating a T3 project clone.
2. Whether sidebar grouping should normalize a fork-only clone and a clone with that fork plus upstream to the same logical project identity.

Reproduction

1. Have a checkout with origin=your-fork/repo and upstream=canonical/repo.
2. Create a second checkout of the same fork with only origin (as Claude Conductor currently does).
3. Open both in T3 Code with repository sidebar grouping enabled.
4. They appear as two project groups rather than one.

[lnieuwenhuis]

@felixleopold I opened #3935 with a fix for this. It carries all configured remote identities into sidebar grouping, so the Conductor fork-only clone joins checkouts that also expose upstream, with regression coverage for both discovery orders.

[felixleopold]

Closed as shipped in the Felix build via commit 732c9868c (early adoption of the #3935 fix). It resolves remote-set identity overlap so fork-only Conductor clones group with checkouts that also expose upstream.