A successful SDK request is a low bar for an agent upgrade. Your backend can receive a valid response while the person using your app gets an empty result card, a file they cannot open, or a spinner that never ends.
The release gate should be a working user task. If you change the model route, tool-response handling, or conversation storage, follow the result all the way into the interface before calling the migration done.
This month's API maintenance topics include richer tool results and short-lived conversation state. Separately, FastMCP's 4.2 alpha updates cover skills-backend paging, schema expansion, and client timeout handling. A request that succeeds once won't exercise all those contracts.
Start with one task you can judge
Consider a spend-report assistant. Give it a small synthetic CSV and ask it to show spend by service, then offer a report download.…