Use consistent reasons for typed failures

This commit is contained in:
2026-11-17 03:55:29 +00:00
parent c6be2ec20d
commit a88141ef4a
4 changed files with 38 additions and 5 deletions

View File

@@ -110,6 +110,10 @@ report, and that the peer's available phase, reason, and origin remain present.
### R3 — Use the Same Missing-Reason Fallback in Run Reports (P3)
**Complete.** The operation and run report use the same typed reason fallback.
The regression covers a missing reason with a wrapped deadline, retained
operation origin and cause, and distinct parent cancellation.
**Affected plan:** Stage 12, item 2, and Stage 17, item 1.
**Evidence:** [Operation projection](../../internal/framework/structuredoutput/failure.go#L42)