Summary
The decision route announces an approval's lifecycle by publishing straight to the approval broker, the last producer still reaching a broker on its own. Move those sites onto the agent event schema so approvals travel the same way as tool lifecycle, MCP progress, and usage.
Goals
- Approval lifecycle carried in the same vocabulary as the rest of an agent's events, rather than on a private channel.
- The publish sites going through the same entry point every other broker-backed producer uses.
- Attended and unattended routes reaching the same outcomes they do today, including timeout and cancellation.
- Emitted events unchanged, demonstrably: the existing approval tests subscribe to the broker and assert on what arrives, so a lost or reshaped field fails them.
Searched Issues
Code of Conduct
Summary
The decision route announces an approval's lifecycle by publishing straight to the approval broker, the last producer still reaching a broker on its own. Move those sites onto the agent event schema so approvals travel the same way as tool lifecycle, MCP progress, and usage.
Goals
Searched Issues
Code of Conduct