Skip to content
Vulpine
Esc
↑↓navigate↵open⌘Jpreview

Tool manifests

Tool manifests (tool.v1 S3): one folder per catalog tool holding its tool.toml, an optional guide.md and golden calls; bun catalog.ts lints them by named rules and compiles the passing ones into catalog/pi/tool-manifests.json, the file the runtime reads; lint-corpus/ is the lint's fixture corpus shared with the conformance kit.

Living doc, checked against the code 2026-11-14

One folder per catalog tool, named for the tool. It holds the tool’s tool.toml (tool.v1, “The manifest”), an optional guide.md and golden/*.json.

  • bun catalog.ts in catalog/pi/extensions/vulpine-tools lints every manifest and compiles the ones that pass into ../tool-manifests.json. The runtime reads that compiled file, because Pi loads extensions under Node, which has no TOML parser. A manifest that fails the lint is refused, and its row keeps what the registration says.

Was this page helpful?