Hello Vercel team,

Please clarify Preview > Branch Tracking for an existing Hobby project. This is informational only; project identifiers and private evidence are omitted. Tracking is currently enabled for all unassigned branches. An authenticated GET /v9/projects/{idOrName} omitted previewDeploymentsDisabled.

1. Does disabling Preview Branch Tracking prevent automatic Preview deployment creation from BOTH branch pushes and pull-request events for unassigned branches, without changing Production or existing READY deployments?

2. Does re-enabling Branch Tracking restore the original effective configuration exactly? Is the native control related to previewDeploymentsDisabled? How is the original ABSENT API-field state restored exactly, rather than simply writing false?

3. Can Git events received while Branch Tracking is disabled be queued, retried, replayed, or cause deployments after tracking is re-enabled without another explicit Git event? Please include delayed webhook processing and automatic reconciliation.

4. Which other Preview environments, branches, active workflows, or project-wide dependencies are affected? Please clarify CLI/API deployments, existing deployments, and Git status/event behavior.

Please provide current official documentation or attributable Vercel staff confirmation, distinguishing guarantees from assumptions. No configuration changes, deployments, repository actions, upgrades, or purchases are requested. Thank you.