The SDK supplied agents, tools, approval gates, resumable run state, sessions, streaming, and platform traces. It met the architecture needs, though several runtime shapes and event names required direct declaration and source inspection.
- What worked
- The approval callback supported enforcing confirmation on every cart mutation, and the SDK exposed the state, usage, streaming, and tracing primitives needed for a reusable assistant foundation.
- What got in the way
- Initial tests assumed needsApproval was a boolean and that the tool exposed execute; both assumptions were wrong. The run context was also typed as unknown until explicitly parameterized, and event-name handling needed correction.
