ChatGPT Vercel connector lacks env/Marketplace actions required by documented workflows

Summary

The ChatGPT Vercel connector currently exposes deployment/project/log actions but no environment-variable mutation or Marketplace integration actions. This blocks documented workflows that require runtime secrets or storage provisioning.

Reproduction

1. Connect Vercel in ChatGPT and authorize a Hobby team.
2. Inspect the available connector actions: deploy/read/log/project actions are present, but no project env CRUD or Marketplace install/provision action is exposed.
3. The hidden deploy runtime contract currently validates only target, name, and files.
4. Provision a durable backend independently (our canary uses a Free Neon project).
5. There is no connector-native way to set DATABASE_URL for the Vercel runtime or install/link the Neon Marketplace integration.

Expected

Expose at least one safe connector-native route matching documented Vercel capabilities:

• project environment variable create/update for Preview/Production, and/or
• Marketplace integration install/provision/link actions.

The Vercel platform and this plugin documentation already treat env management and Marketplace provisioning as first-class workflows.

Public evidence

Focused canary/storage evidence:
https://github.com/TeaShaman-cyber/vercel-cookbook/issues/6

Separate create/read authority bug (not this issue):
https://github.com/vercel/vercel-plugin/issues/164

Current local classification: RUNTIME_WIRING_BLOCKED_BY_CONNECTOR_CAPABILITY.

Start by inspecting the connector action definitions and the hidden deploy runtime contract described in the reproduction, then compare them with the documented environment-variable and Marketplace workflows. Done means exposing a safe connector-native route for environment-variable management or Marketplace integration provisioning, with the corresponding workflow verified.