## Description Adopt the upstream mcp/sdk 0.6.0 builder/handler API so the module continues to work against current SDK semantics. The SDK introduced an explicit `Builder::add(Tool|ResourceDefinition|ResourceTemplate|Prompt $definition, ElementHandlerInterface $handler)` registration path for elements whose schema is only known at runtime, and renamed `RuntimeToolHandlerInterface` to `ToolHandlerInterface`. The module's tool registration in `McpServerFactory` and the `ToolPluginInterface` contract must be updated accordingly, and the bundled CI patch in `.gitlab-ci/patches/mcp-sdk-runtime-handlers.patch` needs to be regenerated to reflect the 0.6.0 changes. ## Acceptance Criteria - [ ] `ToolPluginInterface` extends the new `Mcp\Server\Handler\ToolHandlerInterface` (not the old `RuntimeToolHandlerInterface`). - [ ] `McpServerFactory::registerTools()` constructs an `Mcp\Schema\Tool` and registers it via `Builder::add($tool, $plugin)` instead of the previous `Builder::addTool(handler: ..., name: ..., ...)` named-argument call. - [ ] `.gitlab-ci/patches/mcp-sdk-runtime-handlers.patch` is regenerated against the SDK version the module targets and applies cleanly in CI. - [ ] Existing tests pass and lint/static analysis stay clean. ## Additional Context The upstream 0.6.0 release contains several BC breaks beyond the handler rename (e.g. `Mcp\Schema\Resource` → `Mcp\Schema\ResourceDefinition`, `ArrayLoader` → `ReflectedElementLoader`, removal of `ElementReference::$isManual`, new `title` parameter on `addResource()`/`addResourceTemplate()`). This issue scopes to the tool-registration path that is already touched in the working tree; other surfaces (resources, prompts, loaders) can be tracked separately if needed.