b80c0692dc
* fix: improve Vercel domain 'forbidden' error message The 'forbidden' error code from Vercel is a generic permission denial, not specifically 'domain owned by another team'. It can occur for various reasons: wrong teamId, token lacking project access, account-level restrictions, or domain ownership by another team. Updated the error message to be more accurate and changed the HTTP status code from 400 to 403 to better reflect the permission error nature. Co-Authored-By: hariom@cal.com <hariombalhara@gmail.com> * fix: add message and invalidToken fields to Vercel error response schema This allows better logging of Vercel API error responses, especially when tokens become invalid. The new fields help with debugging permission issues. Co-Authored-By: hariom@cal.com <hariombalhara@gmail.com> * fix: revert status code to 400 for Vercel forbidden errors Keep the status code at 400 to avoid potential downstream side effects while still using the improved error message and schema fields. Co-Authored-By: hariom@cal.com <hariombalhara@gmail.com> * fix: use .nullish() instead of .optional() for message and invalidToken fields .nullish() handles both null and undefined, which is safer for API responses. Co-Authored-By: hariom@cal.com <hariombalhara@gmail.com> --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>