Legacy Tool Gateway Deprecation Timeline

Scope

backend/src/services/llmToolGateway.service.ts

Boundary

• Supported: parser compatibility (parseLlmToolOutput) for debug/legacy payload parsing.
• Deprecated: direct execution path (executeLlmToolCall) for primary runtime behavior.
• Current behavior: executeLlmToolCall is a thin compatibility adapter that delegates to canonical executeTool (no independent policy branching).
• Canonical execution path: backend/src/services/toolExecutor.service.ts through LangChain tool runtime.

Timeline

1. Now

   • Keep parser compatibility.
   • Keep legacy execute helper only as thin adapter.
   • Emit deprecation warning when legacy execute path is used.

2. Next major cycle

   • Remove runtime callsites to executeLlmToolCall (if any are introduced).
   • Keep parser-only utilities for migrations and prompt-debug tools.

3. Final removal window

   • Remove executeLlmToolCall from service exports after no production usage is observed for one full release cycle.