PR Preview incorrectly created as Production despite branch tracking settings

Hello Vercel team,

I am seeing a reproducible Git Integration classification issue on a new isolated project.

Project: francais-college-preview (team: fabrice-projects) Repository: FabriceProjects/conjugaison-pwa PR: https://github.com/FabriceProjects/conjugaison-pwa/pull/19 Head branch: preview/francais-college Head SHA: ef551c7dfc33c9c760994380f55568658f7df7a6

Verified project settings:

Production environment branch tracking: main
Preview environment branch tracking: All unassigned Git branches
The PR targets main; the head branch is not main.

Expected: the PR deployment should be a Preview. Observed: Vercel created the deployment as Environment = Production. To avoid touching Production, I removed that deployment immediately. The project now has no deployments.

This was reproduced after creating a fresh isolated Vercel project, linking it to the repository, and opening the draft PR. A previous isolated project showed the same behavior.

Could you advise why a non-production PR branch is classified as Production and how to restore a safe Preview-only workflow? I will not trigger another deployment until the classification is understood.

No credentials, access codes, or user data are involved.