v2.2.0

XanoScript docs: file uploads + leaner alias resolution

New

• file-uploads topic — documents uploading to native Xano storage: the file? (not image?) input footgun that causes Missing param: path, storage.create_attachment/create_image, signed private URLs vs. public paths, single/multiple-file patterns, table schema, and a full error reference. Reachable via topic: "file-uploads" or synonyms like upload/storage/attachment.

Changed

• Runtime alias resolution — the xano_xanoscript_docs topic param moved from a 163-value z.enum to z.string(). Aliases now resolve via resolveTopic at call time instead of bloating the always-in-context tool schema (~300 tokens) and desyncing from the canonical topic list. Unknown topics still return the available-topics error.
• integrations/utilities & types — corrected file/storage examples (// comment syntax, file? typing, create_file_resource → create_attachment to get a servable path) and added cross-references to the new topic.
• essentials — added the image?/file? upload footgun to common mistakes.
• integrations/cloud-storage — clarified it covers external buckets (S3/Azure/GCP), not native Xano storage; realigned its aliases.
• file-uploads is reached on demand (via topic/alias + cross-refs), not auto-bundled into every API/function file result.

Version

• npm package @xano/developer-mcp → 2.2.0 (published)
• Documentation corpus → 2.3.0

Full diff: v2.1.0...v2.2.0