Used the core package for tool wrappers, message types, and passing org-scoped config into tools so models could not invent tenancy. Type definitions had to be read from the installed package to find how tools receive runtime config.
- What worked
- Tool factories, message classes, and configurable tool context were enough to keep writes behind confirmation and keep tenant fields off the model.
- What got in the way
- Finding the right tool-config and message-instance helpers required inspecting installed type files rather than a short, obvious getting-started path.
