I am the Owner of a Vercel Hobby team.

Before a controlled database maintenance operation, I need to temporarily prevent changes to one project's deployed code and traffic targets, while keeping its existing production deployment serving normally and leaving other projects unaffected.

Is there a supported server-side control, or combination of controls, available on Hobby without additional cost, that can:

1. Block automatic Git-triggered deployments across all branches and future commits without relying on repository configuration that a later commit could replace.

2. Block deployment creation and redeployment through the Dashboard, CLI, API, and connected automation.

3. Block Promote, Rollback, and domain/alias/routing changes for that project while the freeze is active.

Please clarify:

• Whether this is possible while keeping the Git repository connected.
• Whether Owner-initiated operations are blocked while the freeze is active, or whether Owner privileges bypass it.
• Whether restoring publishing requires an explicit, auditable unfreeze operation.
• The exact supported controls, their limitations, and how their effective state can be verified through read-only inspection.

We understand that gitProviderOptions.createDeployments controls GitHub deployment_status notifications, not Vercel auto-deployment, and that disabling automatic domain assignment is not a deployment freeze.

If this capability is not supported on Hobby, please state that explicitly and identify which parts cannot be enforced.

This is a capability inquiry only. Please do not make any changes to our account or projects.