fix(deploy): support project-scoped Vercel tokens

[RSO]

Summary

• upgrade the Vercel CLI from 53.3.1 to 59.5.0 across production staging and promotion workflows
• pick up upstream support for deployments authenticated with project-scoped tokens

Root cause

Vercel CLI 53.3.1 fetched both the project and its owning team before deploying. The new project-scoped tokens can read their project but intentionally cannot read the team, so the CLI aborted with the misleading Could not retrieve Project Settings error before starting a build. Vercel added project-scoped deploy support in 56.3.1; 59.5.0 is the current stable release.

Upstream fix: vercel/vercel#16999

Validation

• actionlint .github/workflows/deploy-production.yml .github/workflows/promote-vercel-deployment.yml .github/workflows/stage-vercel-deployment.yml
• git diff --check
• npm exec --yes --package=vercel@59.5.0 -- vercel --version

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• .github/workflows/deploy-production.yml
• .github/workflows/promote-vercel-deployment.yml
• .github/workflows/stage-vercel-deployment.yml

---

_{Reviewed by grok-4.6 · Input: 129.2K · Output: 5.2K · Cached: 162.2K}

_{Review guidance: REVIEW.md from base branch main}