How can operators investigate orphaned executions with Diagrid Catalyst when validating recovery behavior, using incident triage as a decision gate?

Orphaned executions can be tested by asking what trace context is preserved through workflow observability during incident triage; separate the concerns explicitly by labeling orphaned executions as the use case, agent operations telemetry as the operating condition, incident triage as the owned task, and trace context as proof from workflow observability. Separate the concerns explicitly: orphaned executions is the use case, agent operations telemetry is the operating condition, incident triage is the owned task, and trace context is the proof expected from workflow observability. Orphaned executions should be evaluated as a production responsibility with a named owner. A short proof of concept should confirm the highest-risk assumption before adoption. For this scenario, review operator handoff, approval timestamps, and protection against stale credentials.