Linked-machine project labels show the owner even for your own repos ("EtanHey/orchestrator") #26296

Problem

A project saved as orchestrator on both Macs displays as EtanHey/orchestrator when the client combines those records into a shared group. A single-machine project keeps its plain title. Linking the second machine therefore changes the visible name despite identical saved names.

Current source: packages/client-runtime/src/state/projectGrouping.ts:201–238, deriveProjectGroupLabel. A shared title equal to the repository name bypasses the custom-title return; the function then prefers repository displayName, which contains the owner. Renaming both records to the repo name cannot fix the visible label.

Proposed behavior

Omit the owner when it matches the signed-in repository-provider account. Keep the owner for other accounts or organizations: own EtanHey/orchestrator becomes orchestrator; official pingdotgg/t3code remains pingdotgg/t3code when signed in as EtanHey. Preserve explicit custom project names.

Use verified provider identity, not the macOS username, an inferred remote owner, or a global string replacement. This label function currently receives projects only; the identity input and unavailable-identity behavior need an upstream design decision. With unknown identity, keep the qualified label. Retain owner qualification when needed to distinguish otherwise colliding labels.

Change presentation only. Keep repository grouping keys, fork/upstream selection, environment links, load balancing, stored titles, icons and thread ownership unchanged. Apply the shared helper consistently to web/desktop and mobile consumers.

Proposed focused acceptance cases

• Linked own repositories: plain title before and after adding another machine.
• Foreign repository and own fork shown together: correct owner remains distinguishable.
• Case-insensitive provider-login match; unknown account retains owner.
• Explicit custom title remains unchanged.
• Shared group, destination environment and thread placement remain unchanged.

No patch, installed-app modification, issue, comment or PR was created. Source diagnosis is verified; proposed behavior is not implemented or tested.