[github-actions]

Closes #847

Summary

Failed durable-operation exception events now use a nonblank stored ErrorObject.errorType in both Invocation and Execution trace views. This preserves remote-language types such as RejectedError instead of reporting the SDK's DurableOperationException wrapper. Missing, empty, or whitespace-only types retain the existing throwable-type fallback.

Both event paths previously derived the type from the wrapper instead of its stored error. The shared helper supplies only the type override to native recordException and the existing timestamped event builder. A stored type must be nonblank to replace the fallback. Blank values still count as supplied error details, so the exception event remains present. Nonblank values are used verbatim, and checkpoint payloads are not normalized.

Message/stack diagnostics, timestamps, attempt events, caller-visible exceptions, and Workflow/Invocation reporting remain unchanged. Replacing the throwable would change its diagnostic details, so the change reuses the existing event paths.

Regression coverage and corrected expectations

• OperationExceptionEventTest.storedTypeChangesOnlyTheOperationExceptionType covers missing/null/empty/whitespace types, remote types, and current-clock/epoch/backend timestamps. It compares complete attribute maps because native OpenTelemetry events and AttributesBuilder.build() use different container implementations. The earlier empty-type expectation was incorrect: supplied error details do not imply a usable exception type. Empty, ASCII whitespace, and Unicode whitespace now assert the throwable fallback; nonblank padded values remain verbatim.
• CallbackErrorMetadataTest checks type-only empty and whitespace callback errors through both trace views, retaining the event and the original checkpoint/caller payload. Replay still skips completed user code.
• OperationExceptionTypeIntegrationTest exercises child contexts, conditions, callbacks, and invokes. Replay requires exactly the documented DurableExecutionRoot, Invocation, and Workflow spans, rejecting repeated operation/attempt spans.
• Existing backend-timing coverage checks stored exception types without changing timestamps. README documents the nonblank-type selection rule.

Validation

• New blank-type regressions before the guard: 12 event-timestamp cases and 4 callback cases failed. All 76 focused event, callback, replay, and timing cases pass with the guard.
• Java 17 mvn -o -B -ntp -pl otel-plugin -am clean verify spotless:check: passed; 2,630 tests, 0 failures/errors, 5 configured skips. All 979 OTel plugin tests passed.
• GitHub CI on 58927ff2: Java 17/21/25 builds, Spotless, all CodeQL analyses, and all four OTel cloud conformance jobs passed. The automated review of this commit reported no actionable findings.

[github-actions]

Codex AI review

No actionable findings in the full diff against the SDK invariants and applicable contribution rules. Tests were not executed during this read-only review, so reported test results remain independently unverified.

Reviewed commit 58927ff27e9032fc0f31a3d1260b87831d93ac1f. Workflow run