Module tool_inventory 

What tools an agent on this machine can actually use, and where each one came from.

One answer, two callers. The lint asks “is this name a tool” when it checks a blueprint’s available_tools, and GET /api/tools asks “what may I pick” on behalf of an editor. Those were the same four discovery rules - built-ins, sub-agent tools, the agent’s own tools/, and the global drop-in directory - and a second copy of them would have drifted from the first the moment either side gained a source.

The compile failures come out with the tools rather than being dropped. A script missing because its file has a syntax error looks exactly like a script that was never written, and only one of those is worth telling somebody about.

Structs

SkippedScript

A .rhai file that was found but did not become a usable tool.

ToolEntry

One tool an agent may name in available_tools.

ToolInventory

The full tool inventory for one scope: an agent plus the global directory, or the global directory alone.

Enums

ToolSource

Where a tool comes from, which is the part that answers “will this work if I pick it”.