OTel execute_tool bash span does not expose nonzero process exit outcome

Describe the observability gap

When the shell tool successfully launches the synthetic command false, the resulting execute_tool bash span has status code 0 and no exit-code, error, result, or outcome attribute. Consumers cannot distinguish exit 0 from a nonzero command outcome in metadata-only telemetry.

This is distinct from a tool invocation failure: reading a guaranteed nonexistent synthetic path correctly produced an execute_tool view span with error status, error.type=failure, and an exception event.

Affected version

GitHub Copilot CLI 1.0.83 on macOS.

Steps to reproduce

1. Enable metadata-only OTel file export.
2. Run a synthetic prompt that directs the shell tool to execute exactly false once.
3. Inspect the execute_tool bash span.

The tool execution output reports completion, while the span contains no metadata representing the subprocess's nonzero exit.

Expected behavior

It is reasonable for the tool invocation itself to be considered operationally successful, but metadata-only telemetry should expose a bounded, content-free command outcome such as process.exit.code=1 and/or a Copilot tool outcome attribute. The span status policy can remain separate from the subprocess exit status.

Privacy

The command is synthetic and harmless. Content capture was disabled; no command output, paths, repository data, or credentials are included.

先使用 shell 工具執行合成命令 false，重現僅包含中繼資料的 OTel 匯出，接著檢查產生的 execute_tool bash span。完成的標準是：該 span 暴露一個有界且不含內容的非零子程序結果，例如 process.exit.code=1，或等效的工具結果屬性，同時不擷取命令內容。