Cloud project session can start without a repository checkout

## Problem

A coordinated cloud project session can report successful creation even though it has no repository checkout, workspace path, or runnable terminal. The session then cannot perform the implementation or validation work it was created for, and the creator receives no provisioning error.

## Reproduction

1. Create a coordinated cloud session for a configured repository project and an explicit base branch.
2. Allow the session to start automatically with a kickoff prompt that requires repository commands.
3. Inspect the session metadata and terminal.

Observed in session `8079b444-7187-470c-854f-ffa1f5ad74f2`:

- Session type was `cloud`, but its path was empty.
- The process working directory was `/`.
- No Git checkout was available.
- The native terminal surface twice returned `Terminal not found or not running`.
- The session exhausted its attempt budget without reaching the requested work.

## Expected behavior

- A cloud session created for a repository project starts with that repository and requested ref checked out in a runnable development environment.
- If repository/ref resolution or environment provisioning fails, session creation fails visibly with an actionable error.
- A repository-targeted cloud session never silently falls back to repository-less task state.

## Acceptance criteria

- Cloud-task creation validates that a repository-targeted request has a complete owner and repository name before creating the task.
- A partial repository object, including branch without owner/name, is rejected rather than converted to the empty-repository sentinel.
- Provisioning failure is surfaced through project-session status and the kickoff turn.
- Tests cover repository-targeted cloud creation, explicit repository-less creation, partial repository metadata, and terminal/environment startup failure.
- Programmatic project-session creation receives the same Codespaces-scope and provisioning errors as interactive CLI flows.

Investigation notes

- Runtime triage found that cloud-task metadata creation can omit the repository when either owner or name is missing, then serialize an empty owner/name sentinel while preserving the branch.
- The empty-repository sentinel is intended for explicitly repository-less tasks, not degraded repository-targeted sessions.
- A separate Codespaces OAuth-scope gap may affect the managed-environment path, but server telemetry is needed to determine which path this session used.
- Useful telemetry: the task-creation repository payload, whether an environment ID was assigned, and the provisioning failure/status transition for the session ID above.

Related issues:

- https://github.com/github/copilot-cli/issues/4054
- https://github.com/github/copilot-cli/issues/2655
- https://github.com/github/copilot-cli/issues/4144

Commencez par les points d’entrée de la création de cloud-task et du provisionnement de project-session, puis suivez la gestion des métadonnées du dépôt lors du démarrage de l’environnement et du terminal. Exécutez des tests ou ajoutez de la couverture pour les cas ciblant un dépôt, explicitement sans dépôt, avec des métadonnées partielles et avec un échec du provisionnement, la complétion devant être démontrée par des erreurs de création visibles ou par une session extraite et exécutable.

Rédigé par le modèle d'indexation à partir du texte de l'issue.