n@j_ \dZddlmZddlmZddlmZddlmZdd Z d d d d d d d d ddZ dS)unMap agent activity → a :class:`PetState`. This is the one place the "what is the agent doing right now?" → "which animation row?" decision lives. Each surface feeds it the signals it already tracks: - CLI — ``KawaiiSpinner`` waiting/thinking state + tool outcomes. - TUI — gateway ``tool.start/complete`` + ``message.delta/complete`` events. - Desktop — the ``$busy``/``$awaitingResponse``/tool-event nanostores (re-implemented in TS, but mirroring this priority order). Keeping the priority order here (and documenting it) lets the TypeScript mirror stay faithful without a second design. ) annotations)Iterable)Any)PetStatetodosIterable[Any] | Nonereturnboolclt|pg}|sdSddtfd|DS)u+True iff there's ≥1 todo and every one is completed/cancelled. The "celebrate" beat (``JUMP``) fires when a plan finishes; this mirrors the TUI's ``isTodoDone`` so the trigger is defined once across surfaces. Accepts dicts (``{"status": ...}``) or objects with a ``status`` attr. Ftrr cxt|tr|dnt|ddS)Nstatus) isinstancedictgetgetattr)r s 5/home/thesage/.hermes/hermes-agent/agent/pet/state.py_statusztodos_all_done.._status#s2",Q"5"5UquuX71hPT;U;UUc32K|]}|dvVdS)) completed cancelledN).0r rs r z!todos_all_done..&s1GGAwwqzz77GGGGGGr)r rr r)listall)ritemsrs @rtodos_all_doners` "  E uVVVV GGGGGGG G GGrFbusyawaiting_inputerror celebratejust_completed tool_running reasoningr!r"r#r$r%r&r'rc|r tjS|r tjS|r tjS|r tjS|r tjS|r tjS|r tjStjS)uvResolve the animation state from coarse activity signals. Priority (highest first) — only one row can show at a time, so the most salient signal wins: 1. ``error`` → ``FAILED`` (a tool/turn just failed) 2. ``celebrate`` → ``JUMP`` (explicit success beat, e.g. todos done) 3. ``just_completed`` → ``WAVE`` (turn finished cleanly / greeting) 4. ``awaiting_input`` → ``WAITING`` (blocked on the user — a clarify/approval prompt is open; this outranks the in-flight signals below because the turn is paused on *you*, even though a tool is technically mid-call) 5. ``tool_running`` → ``RUN`` (a tool is executing) 6. ``reasoning`` → ``REVIEW`` (model is thinking / reading) 7. ``busy`` → ``RUN`` (turn in flight, unspecified work) 8. otherwise → ``IDLE`` )rFAILEDJUMPWAVEWAITINGRUNREVIEWIDLEr s rderive_pet_stater0)s}4 }} | | =rN)rrr r )r!r r"r r#r r$r r%r r&r r'r r r) __doc__ __future__rcollections.abcrtypingragent.pet.constantsrrr0rrrr6s  #"""""$$$$$$((((((HHHH&  ((((((((r