SIGINT exits prompt process but model work continues and OTel later reports success

SIGINT の処理から子プロセス/ネイティブ推論処理、OTel ファイル exporter まで、非対話型の --prompt パスを追跡します。最初の delta より前にシグナルが発生するシナリオを再現し、その後、キャンセルによって子孫の処理が停止すること、アクティブな span がキャンセルまたはエラーの結果で終了すること、exporter が上限時間内に flush すること、終了後に出力 writer が残らないことを検証します。

Describe the bug

Interrupting an active non-interactive model call with SIGINT exits the foreground Copilot process, but a descendant/native worker continues producing output and completing the model call. The OTel file appears much later and records the interrupted operation as a successful completion rather than cancelled.

This means cancellation is not promptly propagated to the underlying work and can continue consuming model resources after the foreground process has exited.

Affected version

GitHub Copilot CLI 1.0.83 on macOS.

Steps to reproduce

1. Enable the OTel file exporter and force content capture off.
2. Run copilot --prompt ... --stream on --model <available-model> --output-format json with a synthetic prompt that produces a long response; redirect output to a file.
3. Wait for model.call_start and send SIGINT before the first assistant.message_delta.
4. Record foreground process exit, then continue observing the output and telemetry paths.

Observed result

• SIGINT was sent with zero response deltas observed.
• The foreground process returned as terminated by SIGINT.
• Approximately 55 seconds after the foreground process had exited, inherited output continued to grow and the telemetry file appeared.
• Output contained partial response deltas but no model.call_finished or assistant.turn_end record.
• OTel nevertheless contained a completed chat span and root invoke_agent span with status code 0, finish reason stop, response model, and full token usage. No cancellation/error attribute was present.

A prior late-stream attempt showed the same delayed-file behavior but was not suitable for proving when cancellation was sent. The reproduction above signals immediately after model.call_start.

Expected behavior

On the first termination signal, Copilot should propagate cancellation to child/native inference work, end active spans with a cancelled/error outcome, force-flush and shut down exporters with a bounded timeout, and then preserve the conventional signal exit result. No model work or output writer should remain active after the foreground command reports termination.

A downstream Collector cannot correct a successful producer span or cancel orphaned producer work.

Privacy

The reproduction used only synthetic content and OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT=false. No credentials or user data are included.