matevip 5b24a599ca fix(agent): resolve agent tool bindings by class/bean/function name aliases (#24) ... Issue #24: tools selected in the agent binding UI had no effect at runtime. mate_tool.name stores the Java class name (e.g. "BrowserUseTool") and was written into mate_agent_tool.tool_name, but AgentToolSet.withAllowedToolsOnly matched by the @Tool function name (e.g. "browser_use") — so every binding was silently filtered out. Fix: AgentToolSet builds an alias index per ToolCallback indexed by every equivalent identifier — function name, Spring bean name, and Java class simple name. withAllowedToolsOnly / withDeniedToolsFiltered / excluding all accept any of these aliases, mirroring how Spring's BeanFactory accepts bean names + aliases. ToolRegistry.getEnabledToolSet now threads a bean→beanName resolver into the new AgentToolSet.fromCallbacks(...) overload. Existing two-arg callers keep working; tests pass without changes. Zero data migration: stale mate_agent_tool rows that previously had no effect now resolve correctly via the class-name alias.		2026-04-27 23:51:48 +08:00
..
src	fix(agent): resolve agent tool bindings by class/bean/function name aliases (#24)	2026-04-27 23:51:48 +08:00
Dockerfile	build(docker): install poppler + tesseract for PDF extraction parity with Mac	2026-04-25 11:05:29 +08:00
pom.xml	refactor(approval): unify state machine across DB/metadata/memory	2026-04-27 19:30:52 +08:00
settings.xml	build(maven): declare US + CN repositories in pom.xml, drop opaque mirror	2026-04-25 09:56:17 +08:00