"j|SSKJr SSKJr SSKJr SSKJr SSKJ r SSK J r J r J r \"S\ S9rS S jrg ) ) annotations)TypeVar) await_maybe) UserError)AbstractNativeTool) AgentDepsTNativeToolFunc RunContext _NativeToolT)boundc# Ub.[U[5(d[U"U55IShvN nUc&[SURSURS35e[X5(d[SURSU<35eU$N[7f)aResolve a native tool instance or factory, raising if it doesn't yield a `tool_cls`. A factory returning `None` means "omit this tool" on the native path ([`NativeToolFunc`][pydantic_ai.tools.NativeToolFunc]). The fallback subagent cannot omit once it has already been invoked, so it raises [`UserError`][pydantic_ai.exceptions.UserError] rather than enabling the default tool. `tool_cls` comes first so the return type is solved from it rather than from `native_tool`, which is what lets callers use the result as a `tool_cls` without re-asserting. KEEP IN SYNC with the graph's resolution in `_prepare_request_parameters`, with two deliberate differences: `None`, which the native path omits for that step while the already-invoked fallback subagent cannot, so it raises; and the result type, which the graph accepts as any `AbstractNativeTool` while the fallback subagent needs the `tool_cls` its subagent is built around, so a sibling native tool raises here too. N`z` native tool factory returned `None`, but the already-invoked `fallback_subagent_model` subagent cannot omit the tool. Return a `zL` instance, or drop `fallback_subagent_model` so that `None` omits the tool.z,Native tool must resolve to an instance of `z`, got ) isinstancerrr__name__)tool_cls native_toolctxs h/home/mande/repo/quber/.venv/lib/python3.13/site-packages/pydantic_ai/capabilities/_native_resolution.pyresolve_native_toolr s*z+?Q'R'R' C(899 !!"#!**++w y  k , ,FxGXGXFYY`al`opqq :s-B B AB N)rztype[_NativeToolT]rz6AbstractNativeTool | NativeToolFunc[AgentDepsT] | NonerzRunContext[AgentDepsT]returnr ) __future__rtypingrpydantic_ai._utilsrpydantic_ai.exceptionsrpydantic_ai.native_toolsrpydantic_ai.toolsrr r r rrrsP"*,7DD~-?@  G  r