߲jdZddlmZddlZddlmZmZddlmZm Z ddl m Z ejdZ egdZgd Zdd Zdd Zdd Zdd Z ddZy)zOChild toolset resolution for delegate_task: what a child may and may never use.) annotationsN)ListOptional)TOOLSETSresolve_toolset)_get_inherit_mcp_toolsetsztools.delegate_tool) delegate_taskclarifymemory send_messagecronjob_manage)terminalfilewebc|syt|jdry ddlm}|j t|}t |xrt|jdS#t $rd}Y4wxYw)zDReturn True for canonical MCP toolsets and their registered aliases.Fzmcp-Tr)registryN)str startswithtools.registryrget_toolset_alias_target Exceptionbool)namertargets A/home/ubuntu/.hermes/hermes-agent/tools/delegate_tool_toolsets.py_is_mcp_toolset_namersp  4yF#+223t9= 93v;11&9 :: s A'' A54A5c|Dchc]}|tvs t|dD]}|!c}}t|r jfdtDScc}}w)aAdd every toolset whose tools are a subset of the parent's tools: a parent on a composite like ``hermes-cli`` must still let a child request ``web``/``terminal``; bare name intersection would reject them. Both sides use the RESOLVED static surface: a composite's ``includes`` (``debugging`` -> ``web``/``file``, ``safe``) are tools the parent genuinely holds, and the child never gains a tool the parent lacks.Finclude_registryc3|K|]3}|vr-t|dxrtjr|5yw)FrN)rsetissubset).0ts_nameexpandedparent_tool_namesresolveds r z*_expand_parent_toolsets..0sF h&,WuMMMH &&'89  s9<)rrr!update)parent_toolsetsr$tr%r&r's @@@r_expand_parent_toolsetsr,&sq )Gx,?Y`sxIyDE ?#H #+  Os A A cddhtDchc]%}t|dx}rtd|Dr|'c}z}|Dcgc] }||vs| c}Scc}wcc}w)zRemove toolsets whose tools are ALL blocked (derived from DELEGATE_BLOCKED_TOOLS so the two can't drift) plus composite toolsets children must never get (``delegation``, ``kanban``). delegationkanbanFrc3,K|] }|tvyw)N)DELEGATE_BLOCKED_TOOLS)r#tools rr(z'_strip_blocked_tools..?sJ4..Js)rrall)toolsetsrresolved_toolsblocked_toolset_namesr+s r_strip_blocked_toolsr78sp*848 -dUK KN K J>J J 8  B!1,A#AA BB 8 Cs*A A Actt|dk(rjdtfdt j DS)zOne-tool deny toolsets for the role; passed as ``disabled_toolsets`` so blocked names inside mixed bundles are subtracted AFTER composite expansion. orchestratorr c3K|]F\}}|jdst|jddjsC|Hyw)toolsN)getr!r")r#rdefn blocked_namess rr(z-_blocked_toolsets_for_role..IsEt488G3DTXXV]_aMbIcIlIlmzI{sA*AA)r!r1discardsortedritems)roler?s @r_blocked_toolsets_for_rolerDCsG./M ~o. '~~/ cLt|dd}| t|}nO|r>t|dr2ddl}|jDchc]}|j |x}|}}ntt }|rWt|}|D cgc] } | |vs|  } } trH| t|Dcgc]}t|s|| vs|c}z } n|r||} nt|xst } t| } t|dd} t| tttfr| Dcgc] }t|c}ng} |dk(r*| Dcgc] }|dk7s | } }d| vr| j!dtt"j%| t'|zdgz} | | fScc}wcc} wcc}wcc}wcc}w) uF``(enabled_toolsets, disabled_toolsets)`` for a child. Children never gain tools the parent lacks: explicit ``toolsets`` are intersected with the parent's (composite-expanded) set, else the parent's enabled set is inherited. Blocked tools are stripped twice — whole blocked toolsets here, and exact one-tool deny toolsets via ``disabled_toolsets`` so blocked names inside mixed bundles (hermes-cli) are subtracted AFTER composite expansion and survive registry refreshes. Orchestrators get ``delegation`` re-added unconditionally (role-granted, not inherited).enabled_toolsetsNvalid_tool_namesrdisabled_toolsetsr9r.r/)getattrr!hasattr model_toolsrHget_toolset_for_toolDEFAULT_TOOLSETSr,rrArr7 isinstancelisttuplerappenddictfromkeysrD) parent_agentr4effective_roleparent_enabledr*rLrtsexpanded_parentr+child_toolsetsraw_parent_disabledinherited_disabledchild_disabled_toolsetss r_resolve_child_toolsetsr^Ms\+=tDN!n- ',0BC'88 ;CcCcdhCi=iRrisvU"!.@   0 1#/ ;$ C.3/.3AD.3 .3rE