WSL session creation fails: project has no linked GitHub account

Short summary

Creating a new session for a project hosted in WSL fails during kickoff with project <redacted> has no linked GitHub account, even though the app health check reports that GitHub authorization is valid.

Affected version or release

• GitHub Copilot app v1.1.19 (commit ae7ad64)
• Bundled Copilot CLI 1.0.84-4
• copilotd 0.7.3

Installation context

• GitHub Copilot app installed on Windows
• WSL hosts (Preview) enabled
• Project repositories stored inside an Ubuntu WSL distribution
• App authenticated to github.com

What happened?

The WSL environment registers successfully, copilotd starts with the expected version, and WSL rehydration completes. When the app sends the session kickoff request to the WSL-hosted project, it immediately rejects the request because the project allegedly has no linked GitHub account:

Failed to create session: project <redacted> has no linked GitHub account

The diagnostics contain the same failure for more than one project record. This occurs even though the health check reports:

auth.host = github.com
auth.status = ok
auth.message = GitHub authorization is valid.

Steps to reproduce

1. Sign in to the GitHub Copilot app with a github.com account.
2. Enable WSL hosts (Preview) and restart the app.
3. Register an Ubuntu WSL environment.
4. Configure or select a project whose repository is stored in that WSL environment.
5. Start a new session for the project.
6. Observe that WSL initialization succeeds but session kickoff fails with project <redacted> has no linked GitHub account.

Expected behavior

The WSL session should inherit or resolve the active GitHub account associated with the app/project and complete session creation.

If account linkage is genuinely missing, the app should provide a visible way to link the project to the active account rather than failing during kickoff.

Additional context

Sanitized sequence from the application log:

INFO  spawning wsl copilotd distro="<distro>" executable=<redacted>
INFO  adopted the daemon's endpoint record from its own stdout distro="<distro>" listen=<redacted> daemon_pid=<redacted> version=0.7.3 keys=4
INFO  wsl rehydrate complete env_id=wsl:<distro> new_url=<redacted>
INFO  Received create_session request cwd=<WSL-repository> workspace_id=<redacted> session_type=Project
ERROR failed to create session error=project <redacted> has no linked GitHub account
ERROR kickoff: session creation failed workspace_id=<redacted>
ERROR frontend: Failed to create session: project <redacted> has no linked GitHub account

Later retries in the same diagnostic archive also contain the key-mismatch signature tracked separately in #3667. The error reported here is the earlier, immediate no linked GitHub account rejection and does not require waiting for a run_git timeout.