Issue Summary

Bitbucket Pipelines' OpenTelemetry (OTLP) export for bbc.command spans does not correctly indicate whether an individual pipeline command succeeded or failed. The span status remains UNSET on failure, and no exit-code attribute is emitted, so command-level success/failure can't be determined from trace data alone.

Steps to Reproduce

1. Configure a Bitbucket Pipelines step with OpenTelemetry trace export enabled, including a command that is expected to fail (e.g. a command that exits with a non-zero status such as exit 1).
2. Run the pipeline, then inspect the exported OTLP trace for the resulting bbc.command span (e.g. via your OTEL collector/backend).

Expected Results

The bbc.command span for the failing command should report status.code: ERROR (or otherwise expose the command's exit code as a span attribute), and should have a non-zero recorded duration reflecting actual command runtime.

Actual Results

The data below is returned for the failing command instead of an ERROR status:

command.command: "exit 1"
status.code: 0        // UNSET, not ERROR
startTimeUnixNano == endTimeUnixNano   // zero recorded duration
// no exit-code attribute present on the span

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.