jdZddlmZddlZddlmZmZddlmZeGddZ eGdd Z eGd d Z ddZ ddZ dS)uShared types for normalized provider responses. These dataclasses define the canonical shape that all provider adapters normalize responses to. The shared surface is intentionally minimal — only fields that every downstream consumer reads are top-level. Protocol-specific state goes in ``provider_data`` dicts (response-level and per-tool-call) so that protocol-aware code paths can access it without polluting the shared type. ) annotationsN) dataclassfield)AnyceZdZUdZded<ded<ded<edd Zd ed <edd ZeddZ eddZ eddZ eddZ dS)ToolCallu_A normalized tool call from any provider. ``id`` is the protocol's canonical identifier — what gets used in ``tool_call_id`` / ``tool_use_id`` when constructing tool result messages. May be ``None`` when the provider omits it; the agent fills it via ``_deterministic_call_id()`` before storing in history. ``provider_data`` carries per-tool-call protocol metadata that only protocol-aware code reads: * Codex: ``{"call_id": "call_XXX", "response_item_id": "fc_XXX"}`` * Gemini: ``{"extra_content": {"google": {"thought_signature": "..."}}}`` * Others: ``None`` str | Noneidstrname argumentsNFdefaultreprdict[str, Any] | None provider_datareturncdS)Nfunctionselfs 5/usr/local/lib/hermes-agent/agent/transports/types.pytypez ToolCall.type-szc|S)z=Return self so tc.function.name / tc.function.arguments work.rrs rrzToolCall.function1s  rc:|jpidS)zSCodex call_id from provider_data, accessed via getattr by _build_assistant_message.call_idrgetrs rrzToolCall.call_id6s "(b--i888rc:|jpidS)z*Codex response_item_id from provider_data.response_item_idrrs rr"zToolCall.response_item_id;s!"(b--.@AAArc:|jpidS)uGemini extra_content (thought_signature) from provider_data. Gemini 3 thinking models attach ``extra_content`` with a ``thought_signature`` to each tool call. This signature must be replayed on subsequent API calls — without it the API rejects the request with HTTP 400. The chat_completions transport stores this in ``provider_data["extra_content"]``; this property exposes it so ``_build_assistant_message`` can ``getattr(tc, "extra_content")`` uniformly. extra_contentrrs rr$zToolCall.extra_content@s "(b--o>>>r)rr )rrrr )rr) __name__ __module__ __qualname____doc____annotations__rrpropertyrrrr"r$rrrrrs  NNN IIINNN+05E+J+J+JMJJJJXX999X9BBBXB ? ? ?X ? ? ?rrcLeZdZUdZdZded<dZded<dZded<dZded<dS) Usagez!Token usage from an API response.rint prompt_tokenscompletion_tokens total_tokens cached_tokensN) r&r'r(r)r/r*r0r1r2rrrr-r-Os]++MLMrr-ceZdZUdZded<ded<ded<dZded <dZd ed <edd Zded<e ddZ e dZ e dZ e dZ dS)NormalizedResponseuNormalized API response from any provider. Shared fields are truly cross-provider — every caller can rely on them without branching on api_mode. Protocol-specific state goes in ``provider_data`` so that only protocol-aware code paths read it. Response-level ``provider_data`` examples: * Anthropic: ``{"reasoning_details": [...]}`` * Codex: ``{"codex_reasoning_items": [...], "codex_message_items": [...]}`` * Others: ``None`` r contentzlist[ToolCall] | None tool_callsr finish_reasonN reasoningz Usage | NoneusageFrrrrc>|jpi}|dS)Nreasoning_contentrrpds rr;z$NormalizedResponse.reasoning_contentr"   %2vv)***rc>|jpi}|dS)Nreasoning_detailsrr<s rr@z$NormalizedResponse.reasoning_detailswr>rc>|jpi}|dS)Ncodex_reasoning_itemsrr<s rrBz(NormalizedResponse.codex_reasoning_items|s"   %2vv-...rc>|jpi}|dS)Ncodex_message_itemsrr<s rrDz&NormalizedResponse.codex_message_itemss"   %2vv+,,,rr%)r&r'r(r)r*r8r9rrr+r;r@rBrDrrrr4r4Ys  %%%% I    E+05E+J+J+JMJJJJ +++X+++X+//X/--X---rr4r r r r r rprovider_fieldsrc t|trtj|nt |}|rt|nd}t ||||S)zBuild a ``ToolCall``, auto-serialising *arguments* if it's a dict. Any extra keyword arguments are collected into ``provider_data``. N)r r r r) isinstancedictjsondumpsr r)r r r rEargs_strr=s rbuild_tool_callrLs[)39d(C(CWtz)$$$YH"1 ;o   tB r K K KKrreasonmappingdict[str, str]c6|dS||dS)zTranslate a provider-specific stop reason to the normalised set. Falls back to ``"stop"`` for unknown or ``None`` reasons. Nstop)r )rMrNs rmap_finish_reasonrRs" ~v ;;vv & &&r) r r r r r rrErrr)rMr rNrOrr )r) __future__rrI dataclassesrrtypingrrr-r4rLrRrrrrVs*#""""" (((((((( 9?9?9?9?9?9?9? 9?x   *-*-*-*-*-*-*- *-d L L L L''''''r