Adapter shims around from __future__ import annotations modules must resolve type hints, not read Parameter.annotation

When wrapping callables defined in a module that uses from __future__ import annotations (PEP 563), inspect.signature(fn).parameters[name].annotation returns the annotation as a string (the type's name), not the resolved class. An adapter that does params_class = sig.parameters['params'].annotation; params = params_class(**kwargs) constructs fine but raises TypeError: 'str' object is not callable on the first call. Use inspect.get_annotations(fn, eval_str=True) to resolve at adapter-construction time once. This is hard to spot when the registry is built without invoking the wrapped function, the adapter "loads" cleanly, looks correct in dispatcher tests, and only fails when something actually calls it. Verified 2026-05 in Python 3.13; reproducible against any module using PEP 563.

When wrapping functions from a module that uses from __future__ import annotations (or anywhere PEP 563 / future-annotations are in effect), do not read parameter annotations off inspect.signature(...).parameters. Use inspect.get_annotations(fn, eval_str=True) (Python ≥3.10), or typing.get_type_hints(fn) for older versions, so string forward references are resolved to real classes before you instantiate them. Add a unit test that invokes the adapter through the registry, not just one that constructs it.