feat(storage): add storage.errors.error_codes capability

[mandarini]

Summary

• Adds a new errors group and storage.errors.error_codes feature to capabilities/storage.yaml
• Covers exposing the machine-readable service-specific error code (e.g. NoSuchKey, AccessDenied) returned by the Storage server on a thrown client error

Why

supabase-js PR supabase/supabase-js#2537 adds a code property to StorageApiError (inherited by StorageVectorsApiError), which the SDK compliance check flags as new public API with nowhere to register. There was no existing capability anywhere in the matrix for exposing service error codes, so this adds one. It's area-level (group: errors, no file_buckets/vector_buckets split) since the field lives on the shared error base class and applies to both.

Once this merges, supabase-js's sdk-compliance.yaml will reference storage.errors.error_codes with symbols StorageApiError.code and StorageVectorsApiError.code.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5d61b018-7022-46ae-bef4-54f069085faf

📥 Commits

Reviewing files that changed from the base of the PR and between 825ab0c and 382d9cd.

📒 Files selected for processing (1)

• capabilities/storage.yaml

---

📝 Walkthrough

Summary by CodeRabbit

• New Features
  • Added support for machine-readable error codes across Storage file and vector bucket operations.

Walkthrough

The Storage capability manifest adds an errors capability group titled “Errors.” It also adds the storage.errors.error_codes feature. The feature documents access to service-specific error codes returned by Storage errors for file and vector bucket operations.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}