[Bug] -i initial prompt can remain pending until a second user message on Windows

Describe the bug

Starting Copilot CLI with -i/--interactive <prompt> can open the interactive session without executing the supplied initial prompt. The terminal remains responsive. After the user submits another message, the original initial prompt is then executed automatically.

Debug logging shows the pending request is emitted before the foreground session host is registered:

[WARNING] pending-request event was not delivered to the session host
GenericFailure, no session host is registered for session <redacted>
...
[INFO] Starting Copilot CLI: 1.0.84-3
...
[INFO] Registering foreground session: <redacted>

This appears to be a startup ordering/race issue rather than command-line quoting or CR/LF handling.

Affected version

GitHub Copilot CLI 1.0.84-3

Steps to reproduce the behavior

1. On Windows, open PowerShell.
2. Run copilot -i "Test of prompt.".
3. Observe that the interactive UI launches but the supplied prompt may remain unexecuted.
4. Submit any second message in the session.
5. Observe that the original Test of prompt. request is then executed automatically.

The same diagnostic ordering occurs when invoking the WinGet executable directly:

& "$env:LOCALAPPDATA\Microsoft\WinGet\Links\copilot.exe" -i "Test of prompt."

Expected behavior

The prompt supplied through -i should execute automatically as soon as the interactive session is ready, without requiring another user message.

Additional context

• Date reproduced: September 9, 2026
• OS: Windows, x64
• Shell: PowerShell 7.6.5
• Terminal hosts tested: Windows Console Host and Windows Terminal
• Copilot CLI: 1.0.84-3 (reported as latest)
• Both the WindowsApps launch alias and direct WinGet executable were tested.
• The WindowsApps package was repaired from 1.0.83.0 / NeedsRemediation to 1.0.84.0 / Ok; the pending-request warning still occurred afterward with both launch paths.
• Fresh traces consistently recorded the warning about no registered session host roughly 1.2 seconds before Registering foreground session.
• Full debug logs are not attached because they may contain environment/account metadata, but can be provided privately if requested.

Start by reproducing copilot -i "Test of prompt." in PowerShell on Windows and inspect the debug log around the pending-request event and Registering foreground session entry. Done means the initial prompt executes as soon as the interactive session is ready, without requiring a second message.