+ lHja0t$Rt^RIHt^RIt^RIHtRtRtRt Rt Rt R t R t R tR tR tRtRtRtRt]!]]] ] ] ] ] ]]]]]]]04tRt]!]] ]]04tRRltRtRtRtRRltRt];QJd9.RR]3R] R2] 3] R2] 3] R 2]3] R!2]3R"]3R#]3R$]334FNK 5M2!RR]3R] R2] 3] R2] 3] R 2]3] R!2]3R"]3R#]3R$]3344t R%]!R&&R'R(lt"R)R*lt#R+R,lt$R-R.lt%R#)/uTyped failure-reason codes for bot turns and relay replies. A closed vocabulary of machine-readable reason codes carried ALONGSIDE the free-text ``error`` fields (additive — old consumers keep working). Platform-side codes are assigned by the transport/relay layer; agent-side codes are derived from raw agent/provider error text via ``classify_agent_error``. Classifier precedence is the order of ``_RULES``: auth outranks quota by design — real provider 401 bodies (e.g. Anthropic) say "invalid, blocked or out of funds". ) annotationsN)Anyruntime_offlinequeued_expireddelivery_timeout agent_blocked cancelledprovider_auth_or_accessprovider_quota_limitprovider_rate_limitprovider_server_errorcontext_overflowmissing_configmodel_unavailabletarget_scope_unresolvedunknownruntime_coordination_requiredc V^8dQhRRRR/#)reasonstrreturnbool)formats">/home/ubuntu/.hermes/hermes-agent/tools/bot_failure_reasons.py __annotate__r3s$$c$d$cV\9#N)AUTO_RETRYABLErs&ris_auto_retryabler"3s ^ ##rresumecompress_then_resumenonec V^8dQhRRRR/#)rrrrr)rs"rrrBsrcRV\9d\#V\8Xd\#\#)zEMap a failure reason to the bot-turn retry action (see policy above).)r RETRY_RESUMECONTEXT_OVERFLOWRETRY_COMPRESS_THEN_RESUME RETRY_NONEr!s&r retry_actionr,Bs%  !!)) rz3(?:error code:?\s*|status(?:\s*code)?:?\s*|http\s*)c#t"TF.wr\P!V\P4V3xK0 R#5ir)recompile IGNORECASE).0patcodes& r r4Ns18 ZZR]]#T*s68zycould not read this profile's [^(]+\(an internal profile-scoping bug|served_profile_child_env\(inherit_credentials=true\)z%authentication_error|invalid api key|z (?:401|403)\bz 402\b|out of funds|quota|balancez429\b|rate.?limitz$5\d{2}\b|server[ _]?error|overloadedz/context length|context_overflow|maximum contextz9no llm provider configured|missing config|no access tokenz2model .*(not found|does not exist)|model_not_foundz'tuple[tuple[re.Pattern[str], str], ...]_RULESc$V^8dQhRRRRRR/#)rstdoutz str | Nonestderrrrr)rs"rrrds& Y Yj Y* Y Yrc4RPRW344#)u5The error text of a failed ``hermes … -Q`` delivery turn: both streams, in the order the CLI writes them. The provider prose is the turn's final_response and lands on STDOUT; stderr carries session bookkeeping (``session_id: …``) on every run, so ``stderr or stdout`` only ever saw the banner and every transient failure classified as ``unknown``. The in-process lanes hand over the same two pieces of prose as an agent result dict (``error`` + ``failure_reason``); ``result_retry_action`` joins them here too, so one classifier sees every lane's failure text. c3"TF6q'gK VP4'gK$VP4xK8 R#5ir)strip)r1texts& rr4$turn_failure_text..ms(X.>d$\4::<\TZZ\\.>s AAA)join)r7r8s&&rturn_failure_textr@ds 99Xv.>X XXrc V^8dQhRRRR/#)rresultrrrr)rs"rrrps O O O Orc \V\4'dVPR4'g\#\ \ \ VPR4VPR4444#)u~The retry action for a finished IN-PROCESS turn (an ``_run_agent`` result dict). The transport-agnostic twin of the child-process lanes' ``retry_action(classify_agent_error( turn_failure_text(stdout, stderr)))``: same policy, the failure text just arrives as result fields instead of two streams — ``error`` carries the raw provider summary (status codes included) and ``failure_reason`` the turn loop's own typed verdict, which is what names an overflow the copy only describes in prose. ``RETRY_NONE`` for anything that did not fail (and for a non-dict result), so a successful turn whose text happens to mention 429 is never re-run.failederrorfailure_reason) isinstancedictgetr+r,classify_agent_errorr@)rBs&rresult_retry_actionrKpsZ fd # #6::h+?+? ,&**W-vzz:J/KLN OOrc V^8dQhRRRR/#)rr=rrr)rs"rrrsssrc\T;'gR4pVP4'd+\F wr#VPV4'gKVu# \#)z]Map raw agent/provider error text to a closed reason code (``unknown`` when unmatched/empty).)rr<r5searchUNKNOWN)r=rawpatternr3s& rrJrJsC djjb/C yy{{#MG~~c"" $ Nrc V^8dQhRRRR/#)rrE BaseExceptionrrr)rs"rrrs , ,= ,S ,rc\\VRR4;'gR4P4pVR8Xg V\9dV#\ \V44#)aThe typed reason for a delivery refusal, kept inside the documented vocabulary. An exception's own ``reason`` is trusted only when it names a real code: ``TurnBusyError`` carries ``target_busy``, but ``reason`` is also a stdlib attribute on ``ssl.SSLError`` and ``urllib.error.URLError``, and forwarding one of those would put free text where consumers expect a closed set. Anything else is classified like every other failure. Shared by the relay lane (``bot_relay.deliver``) and the local runner (``bot_mode_dm --run-delivery``). rrN target_busy)rgetattrr< ALL_REASONSrJ)rEsupplieds& rdelivery_failure_reasonrZsK75(B/5526<<>H= H $; E ++r)&__conditional_annotations____doc__ __future__rr.typingrRUNTIME_OFFLINEQUEUED_EXPIREDDELIVERY_TIMEOUT AGENT_BLOCKED CANCELLEDPROVIDER_AUTH_OR_ACCESSPROVIDER_QUOTA_LIMITPROVIDER_RATE_LIMITPROVIDER_SERVER_ERRORr)MISSING_CONFIGMODEL_UNAVAILABLETARGET_SCOPE_UNRESOLVEDrP frozensetrX HELD_NOT_SENTr r"r(r*r+r,_STATUStupler5__annotations__r@rKrJrZ)r[s@rrps # $!%  4-+/%!'3 ^%5}i13F+^=NW  0 O-=?RTijk$ 3   A38%8  BCZ \ 1'- HJab I5 68LM I& ')<=I; <>ST ;=MN E~V >@QR8%%8  BCZ \ 1'- HJab I5 68LM I& ')<=I; <>ST ;=MN E~V >@QR83/, Y O ,r