Nit: per AGENTS.md ("When a public API raises exceptions a caller would reasonably catch, document them in a `Raises:` section"), `get_resource()`'s docstring should mention `ResourceNotFoundError` (and that `ResourceError` may propagate from template creation). The PR updated the sibling `create_resource()` `Raises:` section and added a migration.md entry telling callers to catch these, but left this docstring as a one-liner.

Nit: this branch maps template-handler crashes to `INTERNAL_ERROR` without calling `logger.exception()`, and the lowlevel server's `except MCPError` handler doesn't log either — so the operator gets no server-side traceback for the failure. The parallel `resource.read()` path a few lines below in `read_resource()` does `logger.exception(...)` before wrapping, and AGENTS.md asks for `logger.exception()` when catching exceptions; consider adding the same in templates.py:135 before the `ResourceErr

Nit: per AGENTS.md ("Do not use `Test` prefixed classes — write plain top-level `test_*` functions… do NOT follow that pattern for new tests even when adding to such a file"), the two new tests `test_read_resource_template_error` and `test_read_resource_template_not_found` should be top-level `async def test_…` functions rather than methods on the legacy `TestServerResources` class. They don't use `self` or any class fixtures, so they can be moved out as-is (just add the `@pytest.mark.anyio` dec