docs(vana-sdk): surface VanaStorage as the default storage provider

[volod-vana]

Tiny README clarification — VanaStorage is the default Vana storage provider (talks to storage.vana.org). The big endpoint switch already landed in #145; this is the doc follow-up.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
vana-console	Ignored		May 14, 2026 4:20pm
vana-rbac-auditor	Ignored		May 14, 2026 4:20pm
vana-vibes-demo	Ignored		May 14, 2026 4:20pm

[github-actions]

Findings

• Medium: Upgrading the default endpoint can break reads/deletes of URLs created by older SDK versions. VanaStorage now defaults to https://storage.vana.org at vana-storage.ts:14, but pathFromUrl() still rejects any URL whose host does not exactly match the configured endpoint at vana-storage.ts:296. So a consumer upgrading from the old default may have stored https://storage.vana.com/v1/blobs/... URLs, and download() / delete() will fail client-side before the Worker’s dual-audience migration support can help. Consider allowing storage.vana.com as a legacy host during the migration window, or normalizing legacy URLs to the new endpoint before signing.

Verification

• Tried running the focused test: npm test --workspace packages/vana-sdk -- packages/vana-sdk/src/storage/tests/vanaStorage.test.ts
• Could not run because dependencies are not installed here: vitest: not found.

[github-actions]

🎉 This PR is included in version 3.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀