v0.35.17

Fix

• A failed Agent Zero turn shows its exception and stack trace in the trace, like every other harness. Agent Zero handles its own exceptions, so its failure never reached the output the trace's diagnostic is read from, and the stack frames were dropped. A failed turn's trace now carries the error with its frames: the message first, then the innermost frames, capped at 4,000 characters and with secrets redacted. The turn's one-line error is unchanged. (#546, #571)

Checked on the test VM against a copy of a real instance, A/B against 0.35.16 on the same day, with an Agent Zero turn whose model endpoint did not answer: the trace's diagnostic was empty on 0.35.16; on this release it holds the error and its stack frames, ending at the innermost frame. Agent Zero's own turns pass the support matrix's five scenarios.

Thanks to @aswathas for finding it (#546) and pointing at the exact line.

What's Changed

• agentzero: a failed turn hands the trace its exception with the stack frames, as every other base does by @github-actions[bot] in #571

Full Changelog: v0.35.16...v0.35.17