v0 "Create Repository" error: "You don't have permission to create projects on this team"

In v0, project Settings → GitHub → Create Repository fails with:

"You don't have permission to create projects on this team. Please check your team role or contact your team admin."

Verified facts:

Team: bennec2's projects (Hobby/Free). Settings → Members shows one member — me — with role Owner. There is no team admin above me.
Default Team in Account Settings is bennec2s-projects, selected and saved.
Git Scope is my personal GitHub account (Bennec2), not an organization.
The v0 scope selector lists only "bennec2's projects" — no Personal scope is offered, so the suggested scope toggle is not possible on my account.
Signing out and back in changes nothing. The error occurs on multiple projects.

The support AI agent described this as a conflict/desynchronization between the v0 workspace scope and Vercel project provisioning permissions, but the case form for Technical (v0) → Settings requires a paid account, so I am posting here instead.

The agent also suggested a workaround — create the repository manually on GitHub, then link it via the + menu's "Import from GitHub." I verified this is not possible in the product:

The + menu's "Import from…" offers only Figma (Premium) and Paper. There is no GitHub import.
Project Settings → GitHub → Connect opens only the Create Repository flow. There is no way to select or link an existing repository. I created the repo manually (Bennec2/preschool-pundit) but cannot link it to the project.

Related symptom on the same team: OAuth connections (Vercel's official MCP server) get 403 "Not authorized: Trying to access resource under scope bennec2s-projects" on any call that names the team, and list_teams returns empty — even after a complete disconnect and fresh re-authorization. list_projects without a teamId works, and get_auth_user shows the team as my default. This points to the team-scope authorization state on my account being broken underneath both issues.

Can someone check the provisioning/permission state for my team? v0's GitHub creation flow should work for a team owner.