The docstring caveat "A handler constructing results with `model_construct` bypasses that tracking and is treated as having set nothing" is factually wrong: pydantic's `model_construct` defaults `__pydantic_fields_set__` to the keys actually passed, so an explicit `ttl_ms`/`cache_scope` passed via `model_construct` still wins over the configured hint, exactly like normal construction. The runtime behavior is correct — only the sentence needs correcting or dropping (it only holds when a handler p