Autopilot background-task timeout exits active parent after subagent completes

Describe the bug

In autopilot mode, the 600-second background-task wait timeout terminates the
entire Copilot CLI process even after the background subagent has completed and
the parent agent has resumed work.

The timeout appears to start from when the parent first becomes idle.
It is not cancelled or reset when the background task completes.

The process exits with code 0, causing automation to treat the interrupted run
as successful.

Affected version

1.0.80

Steps to reproduce the behavior

1. Start Copilot CLI in autopilot mode.
2. Launch a background subagent that remains active for several minutes.
3. Allow the parent agent to become idle while awaiting that subagent.
4. Let the subagent complete before the configured COPILOT_TASK_WAIT_TIMEOUT_SECONDS deadline.
5. Allow the parent to resume work.
6. Original timer still fires and exits the entire process, even though the parent is active and the subagent has finished.

Observed timeline from one run:

06:07:40 - background subagent started
06:10:52 - parent became idle while waiting
06:19:12 - subagent completed; parent resumed
06:20:48 - parent was actively streaming an edit tool call
06:20:52 - exactly 600 seconds after the parent became idle, Copilot emitted:
"Timed out after 600s waiting for background tasks to finish; exiting.
Set COPILOT_TASK_WAIT_TIMEOUT_SECONDS to change the limit."

The process then returned exitCode: 0.
The in-progress edit was never executed.

Expected behavior

When a background-task timeout is reached, Copilot CLI should:

1. Cancel only background tasks that are still running.
2. Return control to the parent with a timeout notification.
3. Cancel the wait timer when all background tasks complete.
4. Not terminate an active parent because of a stale background-task timer.

If a session-level deadline intentionally terminates the process, it should be reported as a timeout with a nonzero exit status rather than successful completion.

Additional context

copilot-cli-timeout-redacted-logs.zip

Commencez par suivre le traitement de COPILOT_TASK_WAIT_TIMEOUT_SECONDS et le cycle de vie de l’achèvement des tâches en arrière-plan en autopilot mode. Reproduisez le scénario en six étapes, vérifiez si le minuteur d’attente est annulé lorsque le sous-agent se termine et que le parent reprend, et vérifiez que tout délai d’expiration de session intentionnel signale un état de sortie différent de zéro.