Issue 092: Implement retrieval of Vercel deployment status

[temma02]

Description
Fetch and normalize the status of a deployment from Vercel.

Requirements and context

• Must be secure, tested, and documented where applicable
• Should stay reviewable and fit the current monorepo structure

Suggested execution

• Create branch: issue-092-implement-retrieval-of-vercel-deployment-status
• Keep changes scoped to the issue and reference the task IDs in the PR

Implement changes

• Map provider statuses into internal deployment states
• Preserve relevant timestamps and URLs
• Handle missing deployments and transient provider failures

Test and commit

• Run the most relevant tests for the touched service or UI surface
• Include screenshots or request/response examples when the change is user-facing
• Call out edge cases, assumptions, and any follow-up work

Example commit message
feat: add vercel deployment status lookup

Guidelines

• Prefer small, reviewable PRs
• Keep naming and data contracts consistent with the spec docs
• Preserve responsive and accessible behavior for frontend work

[ACodehunter]

@knightsdev001 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I'm a full-stack developer and I'd like to take this issue.
I understand the requirements and will follow the existing project structure, keep the implementation clean, and include proper tests where applicable.

ETA: 1–3 days (depending on scope)
Portfolio: https://knightsdev-portfolio.vercel.app/

ℹ️ Repo Maintainers: To accept this application, review their application or assign @knightsdev001 to this issue.

[onlydotsevn1]

@onlydotsevn1 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I would like to work on this issue. My plan:

Implement a Vercel deployment status fetch that maps Vercel provider statuses into internal deployment states consistently with the existing state model
Preserve relevant timestamps and URLs from the Vercel response in the normalized output
Handle missing deployments with a clear not found response and transient provider failures with appropriate error handling and retry or fallback behaviour

Tests will cover successful status retrieval and normalization, each provider status mapping to the correct internal state, missing deployment handling, transient failure handling, and correct timestamp and URL preservation.
Branch: issue-092-implement-retrieval-of-vercel-deployment-status
Commit: feat add vercel deployment status lookup
PR will include: Closes 92, request and response examples showing normalized status output, and notes on any edge cases or assumptions around provider status values.
Please assign, happy to clarify the internal state model or provider integration approach before starting.
Thanks!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @onlydotsevn1 to this issue.

[Folex1275]

@Folex1275 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I'd like to work on this please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Folex1275 to this issue.

[drips-wave]

Congratulations, @Folex1275! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Folex1275: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Folex1275 as part of the Stellar Wave Program's 3rd Wave 🥳

😎 @Folex1275: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.