Tony Pan

[MKT-3999] Add custom environment routing to connect attach (#17219) ## Summary - add `--trigger-environment` to `vercel connect attach` - accept a project custom-environment slug or stable ID and send only the stable `customEnvironmentId` - reject unknown or wrong-project environments and branch/custom-environment combinations - preserve trigger-required custom-environment IDs when an attachment is repeated or updated - add help, telemetry, tests, and a CLI changeset The API trigger-routing foundation is merged in [vercel/api#81501](https://github.com/vercel/api/pull/81501). Part of [MKT-3999](https://linear.app/vercel/issue/MKT-3999/support-custom-environments-in-vercel-connect). ## Evidence [Datadog trace](https://app.datadoghq.com/apm/trace/6a63c0900000000045d79b78608d23fb?graphType=flamegraph) - a locally built CLI resolved the custom-environment slug to its stable ID; repeating with that ID returned `unchanged: true` and reported the full preserved attachment - signed event `EvMKT3999-CLI-1784922256` reached the explicit custom-environment domain with environment-scoped OIDC and HTTP 200; the trace records signature verification, domain resolution, forwarding, and the 200 response ## Validation - `pnpm vitest run test/unit/commands/connex/attach.test.ts test/unit/commands/help.test.ts` — 181 tests passed - `pnpm turbo build --filter=vercel` — 39 tasks passed - affected-file Biome lint and formatting checks — passed - live built-CLI slug registration and stable-ID repeat against the deployed API — passed - signed post-repeat trigger event — receiver and Datadog trace returned 200 - disposable connector, project, custom environment, domain, and deployment cleanup — verified 404 ## Scope This PR adds the explicit CLI trigger option and preserves trigger-implied attachment environments. Deletion cleanup, SDK generation, Dashboard UI, and API delivery behavior remain outside this PR.

[connex] Resolve custom environments when attaching projects (#17181) ## Summary - let `vercel connect attach --environment` accept a project custom-environment slug or stable ID - resolve custom inputs against the selected project and send stable `env_*` IDs to Connex - reject unknown or wrong-project custom IDs and deduplicate aliases and repeated values - preserve the existing Production, Preview, and Development default when the option is omitted - document stable-ID input in command help and keep the required CLI changeset - add coverage for alias deduplication and explicit `--project` resolution Depends on the merged Connex API custom-environment stack: 1. https://github.com/vercel/api/pull/81164 2. https://github.com/vercel/api/pull/81165 3. https://github.com/vercel/api/pull/81166 ## Test plan - `pnpm turbo build --filter=vercel` — PASS (`39/39` tasks) - `cd packages/cli && pnpm vitest run test/unit/commands/connex/attach.test.ts test/unit/commands/help.test.ts` — PASS (`2/2` files, `171/171` tests) - Built `connect attach --help` — PASS (exit `0`; custom slug/ID documentation, defaults, and examples rendered) - Explicit `--project vercel-ai-gateway-demo` matrix — PASS (omitted defaults, custom slug, stable ID, and repeatable/comma-separated deduplication) - Linked `cli-test` matrix — PASS (`tonytest` slug and stable ID produced the same stable `env_*` receipt with no `--project`) - Unknown project-scoped `env_*` — PASS (exit `1`; capture count unchanged, so no attachment POST) - API safety boundary — PASS (deployed reads; `6/6` attachment POSTs captured locally, `0` unexpected routes, no deployed mutation) - No `--triggers`, deletion, detach, or connector-removal scenarios were run Related: [MKT-3999](https://linear.app/vercel/issue/MKT-3999)

Preserve Custom Environment SDK coverage (#376)