v0.3.0
Highlights
Pass through the bridge's new cancellation metadata so agents know whether a task was gracefully cancelled or force-killed, and that the YADE __main__ namespace survives the interrupt.
What changed
yade_execute_code: distinguishesterminated(async abort succeeded) fromtimeout(abort failed, bridge may still be blocked). Docstring warns againstexcept BaseException:in user code — it defeats bridge-initiated cancellation.yade_interrupt_task: response now surfacesmethod(flag_only/flag_and_async_exc),async_exc_skipped_reason,namespace_preserved, andcontinuation_hintfrom the bridge. Agents can follow up withyade_execute_codeto resume work — task variables andOstate are preserved across the interrupt.
Pairs with
Requires yade-mcp-bridge 0.3.0 for the new termination metadata. See the bridge release notes for the architectural changes (dedicated script threads, SetAsyncExc cancellation, sim cleanup).
Full Changelog: v0.2.2...v0.3.0