Fix new cloud session disappearing and misgrouping after commit

[osortega]

Problem

Sending a new cloud agent session from the Agents window (vs/sessions) failed in three ways:

1. The session disappeared ~5s after clicking Delegate, even though the task was created successfully on the backend.
2. Once it did appear, it landed in the "Unknown" group.
3. Its repo label flipped from microsoft/vscode (pre-commit) to vscode (post-commit).

Root causes & fixes

1. Session disappears — wait for the committed resource

A cloud session (RemoteNewSession) commits a new resource mid-request (untitled-… → /task/<id>), exactly like Copilot CLI. But _sendFirstChat grouped it with Claude (whose resource is stable), so it waited for the stale untitled resource in the cache, timed out, and removed the session.

• RemoteNewSession now routes through _waitForCommittedSession to learn the committed /task/<id> resource.
• That wait is deferred for cloud: it skips the responseCompletePromise race (which resolves early at the confirmation, not when the commit lands) and uses a longer timeout, because the cloud commit is delayed by a confirmation round-trip + network delegation + session load. Diagnosed from trace logs showing the commit event firing at ~T+6.5s while the old 5s safety timeout gave up at ~T+5.6s.

2. "Unknown" group — attach repo metadata to PR-less task cards

Grouping derives the repo from getRepositoryName(session) (metadata.owner/metadata.name). A brand-new PR-less task session item carried no metadata, so it grouped under "Unknown" (Agents window) / "Other" (core).

• Repo identity is hoisted from PullArtifactRef.repo up to CloudSessionData.repo — a task has a repo regardless of whether it has a pull artifact. resolvePullArtifact now takes repo as an explicit argument (its only consumer).
• The PR-less task card now attaches metadata: { owner, name } from CloudSessionData.repo.

3. Label flip — consolidate to owner/repo

The two label producers derived the repo label differently: the new-session workspace used owner/repo (stripping /HEAD), while the committed adapter used getRepositoryName (repo name only).

• Both now route through a single githubRemoteRepoLabel(uri) helper returning owner/repo, so the session stays in the same group across the commit swap.

Tests

• Adds a regression test for the cloud commit-swap (cloud session that commits a new resource resolves without timing out).
• Full CopilotChatSessionsProvider suite passes (77); client typecheck and copilot-extension typecheck are clean.

Notes

• Fixes 2 and 3 also improve grouping in workbench core's session list, which consumes the same provider metadata.

[Copilot]

Pull request overview

Fixes cloud-session persistence, repository grouping, and label consistency after commit.

Changes:

• Waits for cloud sessions to commit to their final resource.
• Adds repository metadata to PR-less task sessions.
• Standardizes GitHub repository labels as owner/repo.

Show a summary per file

File	Description
copilotChatSessionsProvider.test.ts	Adds cloud commit regression coverage.
copilotChatSessionsProvider.ts	Handles cloud resource commits and consistent labels.
cloudAgentBackend.ts	Hoists repository identity into session data.
taskApiBackend.ts	Populates repository data for task listings.
pullArtifactResolver.ts	Accepts repository identity explicitly.
copilotCloudSessionsProvider.ts	Adds task metadata and forwards repository identity.

Review details

• Files reviewed: 6/6 changed files
• Comments generated: 4
• Review effort level: Medium