## Summary

I cannot create any Vercel deployment for a GitHub-connected project. The branch and commit resolve correctly in the deployment dialog, but submitting the deployment remains on **Loading** and Vercel never creates a deployment record, build log, activity event, or production URL.

Reproduction

• The project is on a Hobby team and connected to a private GitHub repository.
• In the deployment dialog, `main` resolves to the latest commit.
• Selecting **Deploy to Production** remains loading indefinitely.
• A deploy hook is accepted and returns a pending job, but it never creates a deployment.
• The same result occurs in a separate clean Git-linked recovery project created in the same team.

Checks already completed

• Reconnected the Git repository and retried from `main`.
• Confirmed the expected Vite/root/output settings and required environment-variable names without exposing values.
• Tried both Git-triggered and manual deployment paths.
• Source checks pass locally: TypeScript, production build, and 20 tests.
• The browser dashboard can see the projects, but the authorized project API integration reports no projects/linked Git projects and returns 404 for browser-visible project IDs.

Request

Is there a known deployment-queue, team-account, or project-visibility condition that can prevent a deployment from being instantiated at all? What is the recommended way to reset or reconcile this state so a Git/manual deployment produces a deployment record and build log?

No credentials, private configuration values, or deployment-hook URLs are included here.