Task registration, a background driver, placeholder results and a progress poller all exist, but the check that requests a task always returns false.
What
The MCP tool-call path gained a full implementation of long-running server tasks: registering or adopting a task, a background driver, a placeholder result while work continues, and a poller that reports progress as Task <id> .... None of it runs, because the check that decides whether to ask a server for a task is compiled to always return false and the request is sent with no task option set.
Details
- The task pathway also threads a "tasks not allowed" parameter through the call and its retry-after-auth path.
- The error map for listing tools learned a new case for pagination limits being exceeded,
list_pagination_exceeded. - Treat this as landed but inert; nothing in this build asks a server for a task.
Evidence
buildSep2663PlaceholderResult
Strings lifted out of the shipped bundle, so the claim above can be checked against them.