߲jWndZddlmZddlmZmZdZdZdZdZ ddeeee d  d d Z y) aSend-path image eviction policy shared by both stateless outbound passes. Two passes retire old tool-result images from the per-request copy of the conversation: ``agent.context_compressor.evict_stale_outbound_tool_images`` on the OpenAI-shaped list and ``agent.anthropic_message_convert._evict_old_screenshots`` on the Anthropic wire list. Both run from scratch on a fresh clone every request, so they must agree on one policy or the second pass re-evicts on a different frontier than the first (#113517). This module is stdlib-only so the wire converter, a leaf, can import it without dragging in the compaction stack. Why the trigger is a provider limit, not a keep-newest count: retiring an image edits a message the provider has already cached, and Anthropic matches its prompt cache on an exact byte prefix. A keep-newest-N window retires one more message on every new image, so every turn is a full-prefix miss. Holding images until the request would cross a real API limit and then retiring a batch costs one slower turn per batch and nothing below the limit. 20 is the documented threshold at which Anthropic applies a stricter per-image dimension cap (2000 px) to EVERY image in the request, counting images nested in tool_result content. The hard ceilings are higher (100 images per request on 200K-context models, 600 otherwise) but the 32 MB request-size limit usually binds first, which the byte budget guards with headroom for text. ) annotations)OptionalSequencei6nN)carrier_bytes_newest_firstreserved_byteslimitbudgetbatchfloorc8t|}|dg|dzzdg|dzzt|D](} | || z| dz<| | ndz| dz<*dfd dfd |rytt|d|}ds |r||z n|} | dkrydr tfdt|dzDnd} tdt|| |z } d} | | kr#t| | z| } || z r | S| | kr#| S)uHow many of the OLDEST image-bearing tool results to retire. ``carrier_blocks_newest_first`` is the image-block count per image-bearing tool result, newest first; ``reserved_blocks`` counts images the pass must never rewrite (user uploads). The byte dimension is active only when ``carrier_bytes_newest_first`` is given (the wire pass has no sizes). The retire count must be a STEP FUNCTION of the overshoot, because the pass is recomputed on every request: an exact ``count - limit`` target moves the frontier on every new image, and a fixed one-batch retire stops enforcing the limit after the first batch. So the count advances in quanta until the request fits. The quantum is ``batch`` capped at ``window - floor``, where ``window`` is how many newest carriers fit under the ceiling. A quantum wider than that would step past the newest frames on every advance; cutting each step back to exactly ``total - floor`` instead makes the retire count track ``total`` again — the per-image frontier this policy exists to avoid, visible whenever a tool result carries several images or uploads fill most of the ceiling. Holding for ``window - floor`` turns per advance is the most the floor allows. The floor is a SATISFIABILITY floor: it shelters the newest frames only when reserved uploads alone breach the block ceiling (no retirement can fix that), and never under byte pressure — the request-size limit is hard and the provider answers 413. rc&duxs |zkSN)keptr bytes_keptr sizess @/home/ubuntu/.hermes/hermes-agent/agent/image_eviction_policy.py _bytes_fitz/outbound_image_retire_count.._bytes_fitKs!}KD1A AV KKc.|zkxr|Srr)rr blocks_keptr reserved_blockss r_fitsz*outbound_image_retire_count.._fitsNs"T!22e;P 4@PPrc34K|]}|s |ywrr).0krs r z.outbound_image_retire_count..Xs9qa9s )rintreturnbool)lenrangeminmax)carrier_blocks_newest_firstrr r r r r rtotali max_retirewindowquantumretirerrrrrs ` ``` @@@@@routbound_image_retire_countr0!s_D + ,E &E##K "J 5\S(^.I!.LL AE&qM9JU1XPQR 1q5SLLQQ U| E1 u %E&+Ah:e3D%JQ=B1XS9E%!),9 91F!S/0G F : Vg%z2   M :  Mr)r)z Sequence[int]rr"r zOptional[Sequence[int]]r r"r r"r r"r r"rr"r#r") __doc__ __future__rtypingrrOUTBOUND_IMAGE_LIMITOUTBOUND_IMAGE_BUDGET_BYTESIMAGE_EVICTION_BATCHOUTBOUND_IMAGE_FLOORr0rrrr8s*#%(;?%-%%?!.??!8 ?  ?  ? ? ? ? ?r