Security updates
The WebFlux host uses Spring Framework 7.0.10, and the Spring Boot modules use Boot 4.1.2, which manages the same Framework version. These updates address the critical Spring WebFlux advisories GHSA-9qf2-26p9-2q2q and GHSA-j9f9-w8pj-32f8. If your application overrides Spring dependency versions, align it with these versions when upgrading.What changes for clients
Use an absolute working directory when the agent runs on the same machine:
additionalDirectories still requires the agent’s corresponding session capability.
The capability API adds requireMcpHttp(), requireMcpSse(), and requireEmbeddedContext() to NegotiatedCapabilities.
The client send paths now enforce these checks for you.
What changes for agents
Boolean session config options are omitted, with a warning, when the client has not advertised boolean option support. This applies to session responses, config option responses, and config option updates. Other option kinds remain available. Your application still chooses URL elicitation ids and must keep outstanding ids unique. The SDK does not yet track their lifetime.The audit and its limits
The audit covers a frozen roster of 240 requirements from stable ACP v1. Run 001 reported six failures; each was reproduced with a failing test and fixed. Run 002 judged all six fixes PASS and raised two session-path findings that are also fixed in this release. It also raised elicitation id uniqueness, which remains an application responsibility. The audit is model-assisted evidence, not official ACP certification or a claim that every requirement passes. Run 002 contains abstentions and one unanswered item. The general requirement for absolute file paths remains open beyond sessioncwd and additionalDirectories, including file-system requests, terminal working directories, and tool-call locations.
See the report for the complete results and dispositions.