feature/Failed-run-reason · L-260925-3c79e2

[lchoquel]

A durable run that ended without a result used to print its status three times and never its reason. The failed-run presentation in widget/errors.py, used by widget attended, widget detached wait and widget detached result, now reads out the stored error report the SDK carries (the reason from its title and message, the next step and the retry advice), widget detached status prints the same lines under the status, and a run with no stored report says that no reason was recorded and what is left to do. It depends on the published pipelex-sdk 0.13.0, which carries that typed report, and raises the mthds floor to the 0.16.0 that release pins.

Closes L-260925-3c79e2

🤖 Generated with Claude Code

---

Summary by cubic

A failed durable run used to print its status three times and never why it failed. The failed-run presentation now reads out the stored error report—the reason, next step, and retry advice—across widget attended, widget detached wait, and widget detached result; widget detached status prints the same lines under the status, and a run with no stored report says no reason was recorded and what is left to do. Closes L-260925-3c79e2.

Bug Fixes

• The reason is the report's title and message (its error type when it carries neither), the next step its advice, and the retry line its retryable flag, left unsaid when unknown.
• Server error text is escaped before Rich renders it, so bracketed spans in provider messages no longer disappear or crash the print.

Dependencies

• Raises the floors to pipelex-sdk 0.13.0 and mthds 0.16.0, the versions carrying the typed error report.

^{Written for commit 911ac6c. Summary will update on new commits.}