Issue 090: Implement retrieval of Vercel deployment logs

[temma02]

Description
Fetch build and runtime logs from Vercel for failed or in-progress deployments.

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-090-implement-retrieval-of-vercel-deployment-logs
• Keep changes scoped to the issue and reference the task IDs in the PR

Implement changes

• Normalize Vercel log data into platform log types
• Support pagination or incremental retrieval if needed
• Preserve timestamps and severity where available

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 log retrieval

Guidelines

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

[Aesdecodes]

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

I’d like to work on this issue because retrieving deployment logs is critical for debugging and observability. It gives users clear insight into what’s happening during deployments and helps identify failures quickly. I’m comfortable integrating external APIs and handling structured log data, and I can implement a reliable retrieval flow that fits cleanly into the existing system.

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

[Tsammie]

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

I reviewed the current monorepo structure and the existing deployment route/service patterns. My plan is to add a deployment logs endpoint under the existing /api/deployments/[id] surface, backed by a dedicated service that fetches Vercel build logs and runtime logs separately, then normalizes them into the platform log type.

I'd like to take this on.
I’ll keep the implementation scoped and reviewable by reusing the current deployment auth/ownership wrapper, preserving timestamps and severity where Vercel provides them, and adding pagination or incremental retrieval support rather than returning an unbounded log dump. I’ll also cover missing-ID, empty-log, and Vercel-error cases in tests so the behavior is predictable for failed and in-progress deployments.

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

[popsman01]

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

hello dev , assign me to this issue.

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

[drips-wave]

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

🧑‍💻 @popsman01: 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 🌊