Cannot enable Production for a single-owner personal Google Tasks tool

I am setting up a private personal tool that accesses only my own Google Tasks account. Reading and creating tasks already work. I need to remove the Testing-specific seven-day authorization expiry using Google’s supported personal-use route.

Current configuration:

  • Consumer Google account; External audience; Testing status; one test user, the owner.
  • Google Tasks API enabled.
  • Desktop OAuth client, designated for an AI-powered agent. The private MCP bridge calls the Google Tasks REST API.
  • App name, user-support email, and developer-contact email are populated.
  • The full Google Tasks scope, https://www.googleapis.com/auth/tasks, is saved under Data Access and matches the owner’s existing grant.
  • No logo, homepage, privacy-policy URL, terms URL, or authorized domain is configured.
  • Audience displays a disabled Publish app button with: “To publish your app, you must complete your configuration on the Branding page.”
  • Branding shows no specific missing-required-field warning. Verification Center says verification is not required because the app is in Testing.

Google’s OAuth policy excludes personal-use apps from its definition of production apps for some requirements, and its verification guidance includes a personal-use exemption.

What exact configuration is required to enable Publish app for this single-owner personal tool? Does the supported exemption allow In Production status without a public website? If information URLs are mandatory in the current console, which fields and domain-verification requirements actually apply, and is an owner-controlled free hosted subdomain supported?

After moving to In Production, is fresh authorization with the same client and scope sufficient to replace the existing seven-day Testing credential?

The private tool must remain restricted to its owner. I am not seeking to bypass OAuth, consent, verification requirements that actually apply, or revocation controls.

Relevant official guidance:

Matching unresolved reports:

No credentials, project identifiers, account email addresses, or task contents are included in this question.