NQjb*UdZddlmZddlZddlmZmZmZeje Z dd Z dd Z dd Z ddZdZdZded<dZddZedddZdS)uxReplay-history sanitization shared across resume code paths. When a session's last turn dies mid-tool-loop — the process is killed by a restart/shutdown command, a stale-timeout fires, or an interrupt lands before the tool result is written — the persisted transcript can end with a dangling ``assistant(tool_calls)`` (no matching ``tool`` answer) or an interrupted ``assistant→tool`` block. On resume the model sees that broken tail and re-issues the unanswered call, producing an endless "thinking"/reboot loop (#49201, #29086). These pure helpers strip those tails before the history is replayed to the model. They were originally local to ``gateway/run.py`` (which fixed the messaging-gateway path) and are extracted here so every resume surface — the messaging gateway AND the TUI/WebUI gateway — shares the same cleanup instead of the WebUI path silently skipping it. ) annotationsN)AnyDictListcontentrreturnboolct|tsdS|}d|vrdSd|vr d|vsd|vrd|vSdS)z@Return True if a tool result indicates the tool was interrupted.Fz[command interrupted]T exit_code130z-1 interrupt) isinstancestrlower)rlowereds 8/home/alina/.hermes/hermes-agent/agent/replay_cleanup.pyis_interrupted_tool_resultrsc gs # #ummooG'))tg5G#3#3twg%% 5 agent_historyList[Dict[str, Any]]c|s|Sg}d}t|}||kr_||}|ddkrd|vr|dz}g}||krd||ddkrE||||dz }||kr||ddkE|rItd|Dr0td||dz t||}|ddkrDt |d d r!td |dz }E|||dz }||k_|S) uStrip interrupted assistant→tool sequences from replay history. Older interrupted gateway turns can be followed by a queued real user message, so the interrupted assistant/tool block is not necessarily the final tail by the time we rebuild replay history. Remove any contiguous assistant(tool_calls) + tool-result block that contains an interrupted tool result, while preserving successful tool-call sequences intact. rrole assistant tool_callstoolc3\K|]'}t|ddV(dS)rN)rget).0ms r z/strip_interrupted_tool_tails..?sL$$+155B+?+?@@$$$$$$ruVStripping interrupted assistant→tool replay block (indices %d–%d, tool_results=%d)rrz.s'OO7w$OOOOOOr)rrstriprr%r7)rr<s @ris_dangerous_confirmationr>sY gs # #u ==?? " "D OOOO.NOOO O OOr)expiry_secondsnowfloatr?c 8|s|Sg}|D]}t|tr|ddkrt|ddr|d}||t |z |kryt d|t |z ||dpdddt|}t|d<|||||S) u Expire stale dangerous-confirmation text in user messages (#59607). When a high-risk side effect (e.g. host restart via ``shutdown.exe``) runs, the user's plain-text confirmation phrase is persisted in the conversation transcript. If the host restart killed the gateway process before the assistant's tool result was written, the transcript tail ends on the assistant's text response — and the dangerous confirmation text remains in the user role. On the next inbound message — possibly a casual "are you there?" from the user minutes later — the LLM sees the stale confirmation and may interpret the new turn as a fresh re-confirmation, re-executing the destructive action. This is the failure mode reported in #59607. Expired confirmations are REDACTED IN PLACE, not removed: deleting a user message from the incident tail (``user(confirm) → assistant("OK, restarting")``) would leave two consecutive assistant messages, violating the strict role-alternation invariant providers enforce. The message survives with its role intact; only the trigger text is replaced by a sentinel that tells the model the confirmation has expired. Messages without a timestamp are left untouched (backward compatibility: legacy transcripts and in-memory test scaffolding have no timestamps). User messages that contain dangerous confirmation text but are within the expiry window are also left untouched — they represent a fresh confirmation that has not yet been acted on. Complements 75ed07ace (which strips the *assistant* side of the broken tail) by handling the *user* side: a stale plain-text confirmation that the assistant has not yet responded to in a way the resume logic recognises. ruserrr timestampNzYRedacting stale dangerous-confirmation text in user message (age=%.1fs, expiry=%.1fs): %rP) rr1rr>rAr&r'_EXPIRED_CONFIRMATION_SENTINELr$)rr@r?r(r+tsredacteds r#strip_stale_dangerous_confirmationsrIs&N $&G sD ! ! 6)))#'')R*@*@AA*%%B~3r?n"D"D <%))O"WWY''-2ss3  99&D#x(((s Nr)rrrr )rrrr)rrr@rAr?rArr)__doc__ __future__rloggingtypingrrr getLogger__name__r&rr.r3r5&_DANGEROUS_CONFIRMATION_EXPIRY_SECONDSr7__annotations__rFr>rIr:rrrRs+"#"""""""""""""""  8 $ $    ++++\))))X V V V V,*.& +    &* P P P P"C ????????r