$ the-wire · showcase
Agent-governance-toolkit moves its snapshot wire keys, breaking
By RepoJournal · Filed · About Agent Security · Composed from the cited sources · methodology
Microsoft's agent-governance-toolkit now emits model_request, model_response and output on the wire like every other SDK, so manifests written against the old HostSession shape and the agent_os adapter runtime stop lining up until you re-key them.
fix!: send the snapshot contract's keys from HostSession and the AGT adapter runtime microsoft/agent-governance-toolkit
HostSession used to spread the request over top-level model, messages and tools, send the model response as response, and the final content as response.content; the policy engine now sends model_request, model_response and output to match the snapshot contract, wire schema and Rust, Node, .NET and Python adapters. This is a breaking change: a manifest written from the contract failed closed aga...
fix(agent-sre): report a failed runbook rollback instead of rolled_back (#4478) microsoft/agent-governance-toolkit
RunbookExecutor used to mark an execution ROLLED_BACK whenever any completed step had a rollback action, even when that action raised, and the rolled-back steps kept SUCCESS. It now marks each step whose rollback succeeds ROLLED_BACK and marks the execution ROLLED_BACK only when every rollback succeeded, so a failed rollback no longer reads as a clean recovery in agent-sre run histories.
fix(docs): correct streaming marker SDK reference rendering NVIDIA-NeMo/Guardrails
Fern was emitting quoted streaming handoff marker defaults as unescaped attributes, leaving raw ParamField markup in the generated Python SDK reference; the constants now sit at module scope so they render as Python code blocks. The marker strings and handoff behavior are unchanged, so this is docs rendering only.
Action items
- → Migrate agent-governance-toolkit policies and adapters to model_request, model_response and output before upgrading p... microsoft/agent-governance-toolkit [plan]
