+ lHjRt^RIHt^RIt^RIHtHt^RIHtH t ^RI H t ]P!R4t ]!.RO4t.ROtRRltR R ltR R ltR RltRRltR#)zOChild toolset resolution for delegate_task: what a child may and may never use.) annotationsN)ListOptional)TOOLSETSresolve_toolset)_get_inherit_mcp_toolsetsztools.delegate_toolc V^8dQhRRRR/#)namestrreturnbool)formats"A/home/ubuntu/.hermes/hermes-agent/tools/delegate_tool_toolsets.py __annotate__rs ; ;s ;t ;cV'gR#\V4PR4'dR#^RIHpVP \V44p\ T;'d\V4PR44# \ dRpL ``web``/``file``, ``safe``) are tools the parent genuinely holds, and the child never gains a tool the parent lacks.Finclude_registryc3<"TFIpVS9gK \VRR7;o'gK#\S4PS4'gKEVxKK R#5i)FrN)rrissubset).0ts_nameexpandedparent_tool_namesresolveds& r *_expand_parent_toolsets..0sR #+h& ,WuMMM H &&'89 G8s AAA A)rrrupdate)rr$tr%r&r's& @@@r_expand_parent_toolsetsr,&sl )(gx,?Y`sxIyAIy?#H #+  Os A-A-c V^8dQhRRRR/#)r toolsets list[str]r r)rs"rrr8s C C9 C Crc .RR0\Uu0uFXp\VRR7;p'gK\;QJdRV4F 'dK RM RM !RV44'gKVVkKZ up,pVUu.uF qDV9gK VNK up#uupiuupi)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``). delegationkanbanFrc32"TF q\9xK R#5i)N)DELEGATE_BLOCKED_TOOLS)r#tools& rr('_strip_blocked_tools..?sJ>4..>sT)rrall)r.r resolved_toolsblocked_toolset_namesr+s& r_strip_blocked_toolsr:8s*848D-dUK KN K  CJ>JCCCJ>J J 8  Bx!,A#AAAx BB 8 Cs'B  B B B $B 7BBc V^8dQhRRRR/#)r roler r r/r)rs"rrrCsSYrca\\4oVR8XdSPR4\V3Rl\P !444#)zOne-tool deny toolsets for the role; passed as ``disabled_toolsets`` so blocked names inside mixed bundles are subtracted AFTER composite expansion. orchestrator delegate_taskc3<"TFTwrVPR4'gK\VPRR44PS4'gKPVxKV R#5i)toolsNr)getrr")r#r defn blocked_namess& rr(-_blocked_toolsets_for_role..IsF/488G3DTXXV]_aMbIcIlIlmzI{/sA-A A)rr4discardsortedritems)r<rDs&@r_blocked_toolsets_for_rolerICsG./M ~o. '~~/ rc$V^8dQhRRRRRR/#)r r.zOptional[list[str]]effective_roler r ztuple[list[str], list[str]]r)rs"rrrMs$.3.3/.3AD.3 .3rc\VRR4pVe \V4pM_V'dI\VR4'd7^RIpVPUu0uFqeP V4;pfKVkK ppM\\ 4pV'ds\V4pVU u.uF qV9gK V NK p p \4'd>T \V4Uu.uF p\V4'gKWj9gKVNK" up, p M(V'dVeTp M\V4;'g\ p \V 4p \VRR4p \V \\\34'dV Uu.uFp\V4NK upM.p VR8Xd2V Uu.uF qfR8wgK VNK p pRV 9dV P!R4\\"P%V \'V4,R.,44p W3#uupiuup iuupiuupiuupi)u2``(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_namesdisabled_toolsetsr>r1r2)getattrrhasattr model_toolsrNget_toolset_for_toolDEFAULT_TOOLSETSr,rrGrr: isinstancelisttupler appenddictfromkeysrI) parent_agentr.rKparent_enabledrrRr tsexpanded_parentr+child_toolsetsraw_parent_disabledinherited_disabledchild_disabled_toolsetss&&& r_resolve_child_toolsetsrcMs\+=tDN!n- ',0BCC'88 84CcCcdhCi=iRBB8  ./1/B%-FXo1E!!XF $ & & !'!8!8rss\U"!.@   0 1#/ ;$ C.3r