}-je(dZdZdZdddefdZdS)a1 Shared helpers for session compression anchor metadata. Manual compression anchoring versus automatic compression paths =============================================================== When ``auto_compression=True`` is passed to ``visible_messages_for_anchor()``, the function accepts a broader set of message content types (including provider-style ``input_text`` / ``output_text`` parts) and metadata markers (``reasoning``, ``thinking``, etc.) from any non-tool role. This enables the streaming auto-compression path to determine which messages should anchor compression UI metadata without being limited to the legacy manual-compression rules. When ``auto_compression=False`` (the default), the function applies the historical manual-compression rules: only plain ``text`` content parts from non-assistant roles are counted. Why this module exists ====================== Compression anchoring needs to identify which messages in a session transcript are semantically significant enough to seed the compression UI metadata (e.g., message count, token budget display). The original implementation hard-coded these rules in multiple places. This module consolidates the logic so that: 1. Manual compression anchoring (CLI/legacy path) uses the stricter ruleset. 2. Automatic compression (streaming/agent path) can leverage the relaxed ruleset when it knows it is handling provider-style messages. Callers specify ``auto_compression=True`` when the messages may originate from an automatic/compression-aware pipeline, and ``False`` (default) for manual compression contexts. ct|tr3dfd|DSt |pdS)N c3K|]i}t|trR|dv.t|dp|dpdVjdS)typetextcontentN) isinstancedictgetstr.0part part_typess ,/root/hermes-webui/api/compression_anchor.py z _content_text..'s  $%% +/((6*:*:j*H*H   =DHHY$7$7=2 > >*H*H*H*H  r)r listjoinstripr rrs `r _content_textr%s|'4  yy          %''   w}"   # # % %%rcht|tsdStfd|DS)NFc3pK|]0}t|to|dvV1dS)rN)r r r r s rrz)_content_has_part_type..2sW  4A488F#3#3z#Ar)r ranyrs `r_content_has_part_typer/sR gt $ $u   rF)auto_compressionrc2g}|rhdndh}|pgD]}t|ts|d}|r|dkr7|dd}t|d}t ||}|rtt|d t o|d } t |d h} t|d } |s| pt |d d h} |s|s| s| s| r||6|d krtt|d t o|d } t |d h} t|d pt |d d h} |s|s| s| s| r|||s|r|||S)aReturn transcript messages that can anchor compression UI metadata. Manual compression historically only counted plain ``text`` content parts for non-assistant messages, while the streaming auto-compression path also accepted provider-style ``input_text`` / ``output_text`` parts and metadata markers on any non-tool role. Keep that difference explicit at the call site instead of carrying two near-identical helper implementations. >r input_text output_textrroletoolrr attachments)r tool_callstool_use reasoningthinking assistant)r r r boolrrrappend) messagesrouttext_part_typesmessager!rhas_attachmentsrhas_tool_calls has_tool_use has_reasonings rvisible_messages_for_anchorr38sn C?O];;;;V\U]O>r( ( '4((  {{6"" tv~~ ++i,,w{{=99::WAAA  !7;;|44d;;Y L@Y@YN2'J<HHL [!9!9::M  -!1G-22  $ $. $L $M $ 7###  ;  !7;;|44d;;Y L@Y@YN2'J<HHL [!9!9::>T[)??M $ $. $L $M $ 7###   ? JJw    JrN)__doc__rrr)r3rrr6sd!!H&&&GL444t444444r