Ë âß²j'ãó@—dZddlmZdZdZdZd d„Zd d„Zd d„Zd d „Z y )ucShared wording for the exec-approval prompt every messaging surface renders. The button card (``BasePlatformAdapter._format_exec_approval``) and the plain-text ``/approve`` fallback (``gateway.run._format_exec_approval_fallback``) must tell the user the same three things: what Hermes wants to run, why it was flagged, and that silence means the command does NOT run once ``approvals.timeout`` elapses. Keeping the text here means one edit changes every platform; adapters only wrap these strings in their own markup. No imports from ``gateway.platforms.base`` or ``gateway.run`` — both import this module. é)Ú annotationsz0Hermes wants to run a command that needs your OKzWhy it was flaggedu—⌛ Approval timed out after {window} — the command was NOT run. Ask me to try again if you still want it, or raise approvals.timeout in config.yaml.có—ddlm}|«S)zZThe configured ``approvals.timeout`` (default 300s); module attribute so tests can pin it.r©Ú_get_approval_timeout)Útools.approval_contextrrs úI/home/ubuntu/.hermes/hermes-agent/gateway/platforms/base_exec_approval.pyÚapproval_timeout_secondsr s€å<Ù Ó "Ð"ócó—ddlm}||«S)uÁHuman wording for a timeout (300 → "5 minutes"); one formatter shared with the CLI notice and the tool result's ``user_summary`` — see ``tools.approval_context.format_approval_window``.r©Úformat_approval_window)rr )ÚsecondsÚ_shareds rr r s€õIÙ 7Ó Ðr có —dt|«›dS)zCThe last line of every approval prompt: doing nothing is a safe no.zIf you don't answer within z it will NOT run.r ©Ú timeout_ss rÚformat_approval_deadline_liner%s€à (Ô)?À Ó)JÐ(KÐK\Ð ]Ð]r có@—tjt|«¬«S)N)Úwindow)ÚAPPROVAL_TIMED_OUT_NOTICEÚformatr rs rÚ format_approval_timed_out_noticer*s€Ü $× +Ñ +Ô3IÈ)Ó3TÐ +Ó UÐUr N)ÚreturnÚint)rrrÚstr)rrrr) Ú__doc__Ú __future__rÚEA_HEADER_TEXTÚEA_REASON_LABEL_TEXTrr r rr©r rúr!s>ðñ õ#ðD€Ø+Ðð[ðó #ó ó^ô Vr