fix: handling of supabase error responses when creating a signed url

[DonKoko]

• add a retry-and-log guard in createSignedUrl for Supabase HTML/StorageUnknownError responses, with inline docs and helpers at file end
• normalize signed URL error metadata to safe strings to satisfy TS
• covers all callers (asset/kit refresh) via the shared helper

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[vercel]

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

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
shelf-docs	Ignored	Preview		Nov 27, 2025 10:29am

[Copilot]

Pull request overview

This PR improves the robustness of signed URL creation by adding retry logic to handle transient Supabase errors. When Supabase occasionally returns HTML error pages (e.g., CDN/edge 50x errors) that get surfaced as StorageUnknownError, the code now retries once before failing, preventing transient issues from bubbling up as user-facing errors.

Key changes:

• Added retry-and-log guard with up to 2 attempts for handling Supabase HTML/StorageUnknownError responses
• Normalized error metadata (errorName, errorMessage) to safe strings for TypeScript compatibility
• Added helper functions isSupabaseHtmlError and wait at the file end

---

You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

---

You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.