yj?dZddlmZddlZddlmZmZmZeddhZ dZ dd Z ddZ ddZ dde ddddZgdZdS)uTurn-end guard for kanban workers. Kanban workers must end with ``kanban_complete`` or ``kanban_block``. Models (especially GLM / Qwen families) sometimes narrate the next step ("Let me write the report now") and stop with ``finish_reason=stop`` and no tool calls. Hermes treats that as a clean exit → ``rc=0`` → dispatcher ``protocol_violation``. This module is policy-only: when a kanban worker tries to finish without a terminal board tool, return a bounded synthetic nudge so the conversation loop continues instead of exiting. ) annotationsN)AnyIterableOptionalkanban_complete kanban_blockreturnboolctjd}|*|dvrdStjdpd}t |S)zReturn whether the kanban stop-guard is active for this process. On when ``HERMES_KANBAN_TASK`` is set (dispatcher-spawned worker), unless ``HERMES_KANBAN_STOP_NUDGE`` explicitly disables it. HERMES_KANBAN_STOP_NUDGEN>0noofffalseFHERMES_KANBAN_TASK)osenvirongetstriplowerr )envtasks 7/home/ragecks/.hermes/hermes-agent/agent/kanban_stop.pykanban_stop_nudge_enabledrsr *..3 4 4C 399;;,,..2MMMu JNN/ 0 0 6B = = ? ?D ::tcrstrct|trr|d}t|tr$t|dpdSt|dpdSt |dd}| tt |ddpdStt |ddpdS)Nfunctionnamer) isinstancedictrrgetattr)rfns r_tool_call_namer'&s"d) VVJ   b$   -rvvf~~+,, ,266&>>'R((( Z & &B ~72vr**0b111 wr62&&," - --rmessagesIterable[dict] | NonecP|sdS|D]}t|ts|d}|dkr5|dpgD]}t|tvrdSh|dkr0t |dpd}|tvrdSdS) zATrue if this conversation already invoked a terminal kanban tool.Frole assistant tool_callsTtoolr"r)r#r$rr'_TERMINAL_KANBAN_TOOLSr)r(msgr+rr"s rsession_called_kanban_terminalr12s u  #t$$  wwv ;  ggl++1r  "2&&*@@@444A V^^swwv,"--D---tt 5r)r(attempts max_attemptstask_idr2intr3r4 Optional[str]ctsdS||krdSt|rdS|p tjdpdpd}d|dS)zReturn a synthetic follow-up when a kanban worker exits without a terminal tool. Returns ``None`` when the guard should not fire (not a kanban worker, already completed/blocked, or nudge budget exhausted). Nrrz this taskzj[System: You are a Hermes kanban worker. A plain-text reply is NOT a terminal state for the board. Task `u!` is still `running`. Ending now without a board tool causes a protocol violation (clean exit with no `kanban_complete` / `kanban_block`). Do this immediately in your next response — do not narrate intent: 1. Finish any remaining deliverable (write the required file(s) now). 2. Call `kanban_complete(summary=..., artifacts=[...])` if the work is done, OR `kanban_block(reason=...)` if you are blocked. Never end a turn with only a promise of future action. Repeated protocol violations will block this task and require manual intervention.])rr1rrrr)r(r2r3r4tids rbuild_kanban_stop_nudger9Es % & &t<t%h//t  @bjnn%9:: @b G G I I X[C U U U U r)r9rr1)r r )rrr r)r(r)r r ) r(r)r2r5r3r5r4r6r r6)__doc__ __future__rrtypingrrr frozensetr/_DEFAULT_MAX_ATTEMPTSrr'r1r9__all__rrrAs  #""""" **********#$5~#FGG     . . . .*'+-!      F   r