Deploy hooks return PENDING but no deployment is created after Git reconnect

## Summary

Vercel is accepting deployment requests for a connected GitHub project but never creates a deployment record.

## Project context

- Project: `anatrova1/trainer`

- Repository: `anatrova/trainer`

- Production branch: `main`

- Current main head: `bf834bcb6172b55b6ea9d6310c8cea57ddd2b4f1`

## What happens

1. A deploy hook for `main` returns HTTP `201` and a `PENDING` job (`Gba2SJakSqUXYuvuC0Tt`).

2. No deployment appears afterward—not queued, building, blocked, error, or ready.

3. Pushing a fresh source change also does not create a deployment.

4. Disconnecting and reconnecting the GitHub integration succeeded, but did not change the behavior.

## What we ruled out

Earlier Git-triggered deployments were blocked due to a malformed historical author email. New commits are authored by `Anatrova Software <REDACTED>`, the account identity, so this is no longer the cause. The Vercel dashboard status filter includes active states, so the deployment is not simply hidden.

## Impact

A production fix for scheduled notification processing is committed but cannot reach production. Automated session reminders and related notifications remain at risk.

Has anyone seen deploy-hook jobs remain `PENDING` without a deployment being created after reconnecting a Git repository? Is there a project-level queue reset, integration repair, or other workaround available on Hobby?