Archibald312 makes adding new AI tools a one-file job

A 3,000-line monolith that wired the chat assistant to everything it can do gets carved into a clean registry, so future capabilities slot in without surgery.

Archibald312 took the single file that defined every action the AI assistant could perform - reading documents, generating Word files, editing with tracked changes, pulling table cells, listing workflows - and split it into one small file per tool, with a shared registry that knows which tools are available in which context. The orchestrator shrinks by about seventy percent and now does only what an orchestrator should: hold the system prompt, run the model stream, parse citations, assemble messages.

The stated motivation is extensibility by addition rather than editing. Each tool declares its own gating - needs a project, needs a document index, needs a tabular store - so the routes calling the assistant no longer have to thread that knowledge through by hand. Archibald312 merged it thirteen minutes after opening, with the unit tests green but candidly noting that the end-to-end specs which would actually exercise the new plumbing were already disabled upstream over unrelated UI drift.