refactor(tools): first-wave simplification of tools/ (file ops split, lazy_deps, code_exec, approval, browser, delegate, mcp, skills, terminal, voice, media)
Behavior-neutral structural pass over tools/*: god-file extractions into sibling modules (file_operations_common/lint/search, file_tools_paths/ read_tracking/write, code_execution_env/rpc, tool_search_catalog/names/ validation, tts_command_provider, ...), duplicate helper unification, if/elif -> dispatch tables, dead-code removal, docstring compaction. Tool schemas (get_tool_definitions) verified byte-identical to base.
This commit is contained in:
+3
-14
@@ -1,18 +1,7 @@
|
||||
#!/usr/bin/env python3
|
||||
"""Tools package namespace.
|
||||
|
||||
Keep package import side effects minimal. Importing ``tools`` should not
|
||||
eagerly import the full tool stack, because several subsystems load tools while
|
||||
``hermes_cli.config`` is still initializing.
|
||||
|
||||
Callers should import concrete submodules directly, for example:
|
||||
|
||||
import tools.web_tools
|
||||
from tools import browser_tool
|
||||
|
||||
Python will resolve those submodules via the package path without needing them
|
||||
to be re-exported here.
|
||||
"""
|
||||
"""Tools package namespace. Kept side-effect free: importing ``tools`` must not
|
||||
load the tool stack, since some subsystems import tools while
|
||||
``hermes_cli.config`` is still initializing. Import concrete submodules directly."""
|
||||
|
||||
|
||||
def check_file_requirements():
|
||||
|
||||
Reference in New Issue
Block a user