@sponson/adapters 0.0.0-stage → 0.5.0

package/recipes/svix.yaml

@@ -0,0 +1,109 @@
+# yaml-language-server: $schema=../../../schema/recipe.schema.json
+# Svix API recipes (Svix as the webhook sender). Format and checklist: docs/adr/0020-recipes.md, CONTRIBUTING.md
+# "Adding a recipe".
+provider: svix
+title: Svix
+category: webhooks
+verified_on: "2026-10-11"
+docs:
+  - title: Svix API reference (OpenAPI document)
+    url: https://api.svix.com/api/v1/openapi.json
+  - title: Svix API reference
+    url: https://api.svix.com/docs
+  - title: Entities overview (ids and uids)
+    url: https://docs.svix.com/overview
+api:
+  base_url: https://api.us.svix.com
+  base_url_env: SVIX_API_URL
+  auth: { bearer_env: SVIX_AUTH_TOKEN }
+detect:
+  deps: [svix]
+  env: ["SVIX_*"]
+  starter:
+    - op: endpoint
+      values: { uid: "sponson-${ctx.env}-${ctx.scope}" }
+  where:
+    app_id: "Svix dashboard → Applications: the application (customer) the previews receive as"
+    url: "the preview's webhook handler: its URL plus the handler's path (a `{ from }` reference cannot carry a path)"
+assumptions:
+  - id: SV1
+    verified: true
+    text: "`POST /api/v1/app/{app_id}/endpoint` creates an endpoint from `url` (required), `uid`, `description`, `eventTypes`, `channels`, `disabled`, `metadata` and an optional `secret`, answering 201 with the endpoint (`id` `ep_…`, `uid`, `url`, …); requests carry `Authorization: Bearer <token>`."
+    source: https://api.svix.com/api/v1/openapi.json
+  - id: SV2
+    verified: true
+    text: "`GET`, `PATCH` (partial update) and `DELETE` (204) `/api/v1/app/{app_id}/endpoint/{endpoint_id}` take the endpoint's id or its uid, and `{app_id}` takes the application's id or uid."
+    source: https://api.svix.com/api/v1/openapi.json
+  - id: SV3
+    verified: true
+    text: "A uid is 1–256 characters of letters, digits, `-`, `_` and `.`, unique among the application's endpoints, so it names the endpoint for every later request and a create whose answer was lost is found by it."
+    source: https://api.svix.com/api/v1/openapi.json
+  - id: SV4
+    verified: true
+    text: "The endpoint's signing secret is generated when `secret` is null (recommended) and is readable at any time with `GET …/endpoint/{endpoint_id}/secret` (`{ key }`): it is not a once-only value, and this recipe does not output it (an endpoint answer does not carry it)."
+    source: https://api.svix.com/api/v1/openapi.json
+  - id: SV5
+    verified: true
+    text: "The API is served per region (`api.us.svix.com`, `api.eu.svix.com`, `api.ca.svix.com`, `api.au.svix.com`), and POST requests accept an `idempotency-key` header."
+    source: https://api.svix.com/api/v1/openapi.json
+  - id: SV6
+    verified: false
+    text: "A create with a uid that exists already answers 409 (the specification lists 409 for every operation without saying when), after which the endpoint is found by its uid and claimed only if an earlier intent of the same scope named it."
+  - id: SV7
+    verified: false
+    text: "`description` is answered as sent (default empty), `disabled` as a boolean and `eventTypes` as the list sent, so they compare without drift on every plan; accounts outside the US region set `base_url` in the provider block."
+ops:
+  endpoint:
+    kind: resource
+    title: Application endpoint
+    summary: An endpoint of a Svix application delivering to an environment's URL, named by a uid such as `preview-pr-42`. Its URL, description, event type filter and disabled flag are compared for drift; its signing secret stays readable in Svix (SV4).
+    covers: [svix-endpoint]
+    params:
+      app_id:
+        type: string
+        required: true
+        description: The application's id (`app_…`) or uid.
+        example: acme-customer
+      uid:
+        type: string
+        required: true
+        pattern: "^[a-zA-Z0-9\\-_.]{1,256}$"
+        description: The endpoint's uid, unique in the application; its identity.
+        example: "sponson-${ctx.env}-${ctx.scope}"
+      url:
+        type: string
+        required: true
+        pattern: "^https?://\\S+$"
+        description: The URL messages are delivered to.
+        example: "https://${ctx.scope}.preview.example.com/api/webhooks"
+      description:
+        type: string
+        default: ""
+        description: A note shown in the Svix dashboard and the application portal.
+      event_types:
+        type: list
+        description: Event type names to deliver (all when left out); at least one when set.
+      disabled:
+        type: boolean
+        default: false
+        description: Whether deliveries are paused.
+      secret:
+        type: string
+        description: "A signing secret to use instead of a generated one (`whsec_…`); sent on create only. Use `{ secret: … }`."
+    http:
+      read: { path: "/api/v1/app/{app_id}/endpoint/{uid}" }
+      create:
+        path: "/api/v1/app/{app_id}/endpoint"
+        body: { uid: { param: uid }, secret: { param: secret } }
+        idempotency_key: true
+      update: { method: PATCH, path: "/api/v1/app/{app_id}/endpoint/{id}" }
+      delete: { path: "/api/v1/app/{app_id}/endpoint/{id}" }
+      fields:
+        url: { param: url }
+        description: { param: description }
+        disabled: { param: disabled }
+        eventTypes: { param: event_types }
+    sim:
+      id_from: uid
+    live:
+      params: { app_id: SPONSON_LIVE_SVIX_APP_ID }

package/recipes/turso.yaml

@@ -0,0 +1,98 @@
+# yaml-language-server: $schema=../../../schema/recipe.schema.json
+# Turso Platform API recipes. Format and checklist: docs/adr/0020-recipes.md, CONTRIBUTING.md "Adding a recipe".
+provider: turso
+title: Turso
+category: databases
+verified_on: "2026-10-11"
+docs:
+  - title: Create database
+    url: https://docs.turso.tech/api-reference/databases/create
+  - title: Retrieve database
+    url: https://docs.turso.tech/api-reference/databases/retrieve
+  - title: Delete database
+    url: https://docs.turso.tech/api-reference/databases/delete
+  - title: Branching
+    url: https://docs.turso.tech/features/branching
+api:
+  base_url: https://api.turso.tech/v1
+  base_url_env: TURSO_API_URL
+  auth: { bearer_env: TURSO_API_TOKEN }
+detect:
+  deps: ["@libsql/client", "@tursodatabase/"]
+  env: ["TURSO_*"]
+  db_hosts: [.turso.io]
+  starter:
+    - op: database_branch
+      values: { name: "app-${ctx.scope}" }
+  where:
+    organization: "`turso org list`"
+    parent: "the database to branch from: `turso db list`"
+assumptions:
+  - id: TU1
+    verified: true
+    text: "`POST /v1/organizations/{organizationSlug}/databases` with `name`, `group` and `seed: { type: database, name: <parent> }` creates a database copied from the parent, authenticated with a Platform API token as `Authorization: Bearer`."
+    source: https://docs.turso.tech/api-reference/databases/create
+  - id: TU2
+    verified: true
+    text: "The create answers `{ database: { DbId, Hostname, Name } }` (capitalised), and 409 when a database with that name exists already."
+    source: https://docs.turso.tech/api-reference/databases/create
+  - id: TU3
+    verified: true
+    text: "`GET /v1/organizations/{organizationSlug}/databases/{databaseName}` answers `{ database: { Name, DbId, Hostname, group, … } }`, and 404 when there is none."
+    source: https://docs.turso.tech/api-reference/databases/retrieve
+  - id: TU4
+    verified: true
+    text: "`DELETE` on the same path removes the database; 404 when it is gone."
+    source: https://docs.turso.tech/api-reference/databases/delete
+  - id: TU5
+    verified: true
+    text: Database names are lower-case letters, numbers and dashes, at most 64 characters, unique in the organization; the group must exist already.
+    source: https://docs.turso.tech/api-reference/databases/create
+  - id: TU6
+    verified: false
+    text: The database is usable as soon as the create answers (no readiness to poll for a branch of a database in the same group).
+ops:
+  database_branch:
+    kind: resource
+    title: Database branch
+    summary: "A database copied from a parent database (a branch), named for the scope, such as `app-pr-42` from `app`. Its hostname is an output for the app's connection URL. Only its existence is compared for drift: changing `group` or `parent` later does not move or re-copy a database that exists."
+    covers: [turso-database]
+    params:
+      organization:
+        type: string
+        required: true
+        description: The organization (or user account) slug.
+        example: acme
+      name:
+        type: string
+        required: true
+        pattern: "^[a-z0-9-]{1,64}$"
+        description: The new database's name.
+        example: "app-${ctx.scope}"
+      parent:
+        type: string
+        required: true
+        description: The parent database to copy.
+        example: app
+      group:
+        type: string
+        default: default
+        description: The group the database is placed in; it must exist.
+      timestamp:
+        type: string
+        description: Copy the parent as it was at this ISO 8601 time (point-in-time recovery window only).
+    http:
+      read: { path: "/organizations/{organization}/databases/{name}" }
+      create:
+        path: "/organizations/{organization}/databases"
+        body:
+          name: { param: name }
+          group: { param: group }
+          seed: { type: database, name: { param: parent }, timestamp: { param: timestamp } }
+      item_path: /database
+      id_path: /Name
+      outputs: { hostname: /Hostname, db_id: /DbId }
+    sim:
+      id_from: name
+    live:
+      params: { organization: SPONSON_LIVE_TURSO_ORGANIZATION, parent: SPONSON_LIVE_TURSO_DATABASE }

package/recipes/unleash.yaml

@@ -0,0 +1,149 @@
+# yaml-language-server: $schema=../../../schema/recipe.schema.json
+# Unleash Admin API recipes. Format and checklist: docs/adr/0020-recipes.md, CONTRIBUTING.md "Adding a recipe".
+provider: unleash
+title: Unleash
+category: flags
+verified_on: "2026-10-11"
+docs:
+  - title: Admin API overview (authorization, base URL)
+    url: https://docs.getunleash.io/reference/api/unleash
+  - title: Add a strategy to a flag in an environment
+    url: https://docs.getunleash.io/reference/api/unleash/add-feature-strategy
+  - title: Get feature flag strategies
+    url: https://docs.getunleash.io/reference/api/unleash/get-feature-strategies
+  - title: Update a strategy (replace)
+    url: https://docs.getunleash.io/reference/api/unleash/update-feature-strategy
+  - title: Delete a strategy
+    url: https://docs.getunleash.io/reference/api/unleash/delete-feature-strategy
+  - title: API tokens and client keys
+    url: https://docs.getunleash.io/reference/api-tokens-and-client-keys
+# Every Unleash instance has its own URL (self-hosted, or https://<region>.app.unleash-hosted.com/<instance>):
+# everything before `/api`.
+base_url_example: https://unleash.example.com
+api:
+  base_url_env: UNLEASH_API_URL
+  auth: { header: Authorization, value_env: UNLEASH_AUTH_TOKEN }
+detect:
+  deps: [unleash-client, unleash-proxy-client, "@unleash/"]
+  env: ["UNLEASH_*"]
+  starter:
+    - op: flag_strategy
+      values: { title: "preview ${ctx.scope}", values: ["${ctx.scope}"] }
+  where:
+    base_url: "your Unleash instance's URL (`https://<instance>`)"
+assumptions:
+  - id: UN1
+    verified: true
+    text: "Every request carries the token as it is in `Authorization` (`Authorization: <token>`, no `Bearer`); a personal access token or service account token (admin tokens are deprecated) reaches the Admin API. The spec also lists a Bearer scheme, but the server does not strip a `Bearer ` prefix, so the bare form is used."
+    source: https://docs.getunleash.io/reference/api/unleash
+  - id: UN2
+    verified: true
+    text: "`POST /api/admin/projects/{projectId}/features/{featureName}/environments/{environment}/strategies` with `name`, `title`, `disabled`, `constraints` and `parameters` adds a strategy and answers it bare, with its server-assigned `id` (a UUID)."
+    source: https://docs.getunleash.io/reference/api/unleash/add-feature-strategy
+  - id: UN3
+    verified: true
+    text: "`GET` on the same path answers a bare array of the environment's strategies (the source returns `FeatureStrategySchema[]`; the docs page's schema shows a single strategy, which is wrong)."
+    source: https://github.com/Unleash/unleash/blob/main/src/lib/features/feature-toggle/feature-toggle-controller.ts
+  - id: UN4
+    verified: true
+    text: "`PUT .../strategies/{strategyId}` replaces a strategy's configuration (so it sends `name`, `title` and every compared field); `DELETE` on the same path removes it."
+    source: https://docs.getunleash.io/reference/api/unleash/update-feature-strategy
+  - id: UN5
+    verified: true
+    text: "A constraint is `{ contextName, operator, values, caseInsensitive, inverted }` (`caseInsensitive` and `inverted` default to false, and are written explicitly so the comparison does not depend on defaults); `parameters` is a map of strings (`rollout: \"100\"`)."
+    source: https://docs.getunleash.io/reference/api/unleash/add-feature-strategy
+  - id: UN6
+    verified: false
+    text: "`title` is optional and not unique on the server: the strategy is identified by its title in the environment, and two strategies with that title are PARAM_INVALID rather than a guess."
+    source: https://docs.getunleash.io/reference/api/unleash/add-feature-strategy
+  - id: UN7
+    verified: false
+    text: "A strategy is read back with `constraints` and `parameters` exactly as written (no extra keys such as `value: \"\"`); otherwise every plan shows it as changed."
+  - id: UN8
+    verified: true
+    text: "Deleting a strategy that is gone already answers 200 (nothing to do). Deleting the last strategy of an environment turns the flag off in that environment (the service calls `disableEnvironmentIfNoStrategies`). Adding a strategy does not turn the environment on."
+    source: https://github.com/Unleash/unleash/blob/main/src/lib/features/feature-toggle/feature-toggle-service.ts
+  - id: UN9
+    verified: true
+    text: "With change requests enabled for the environment, these writes are refused unless the caller may bypass them; the refusal fails the apply."
+    source: https://github.com/Unleash/unleash/blob/main/src/lib/features/feature-toggle/feature-toggle-service.ts
+ops:
+  flag_strategy:
+    kind: resource
+    title: Flag strategy with constraints
+    summary: "A `flexibleRollout` strategy on a flag in one environment, constrained to the preview (such as `preview IN [pr-42]`). Located by its title in the environment's strategies; a console edit of its constraints, rollout parameters or `disabled` is drift. Destroy deletes it; if it was the environment's last strategy, Unleash turns the flag off there (UN8). The environment itself must be enabled for the flag to be served."
+    covers: [unleash-strategy]
+    params:
+      project:
+        type: string
+        default: default
+        description: The project id.
+      feature:
+        type: string
+        required: true
+        description: The flag's name; also the rollout's `groupId`.
+        example: new-checkout
+      environment:
+        type: string
+        required: true
+        description: The environment the strategy is added in.
+        example: development
+      title:
+        type: string
+        required: true
+        description: The strategy's title, unique among the environment's strategies; it identifies the strategy.
+        example: "preview ${ctx.scope}"
+      context_name:
+        type: string
+        required: true
+        description: The context field the constraint tests (a custom context field such as `preview`, or `environment`, `userId`, …).
+        example: preview
+      operator:
+        type: string
+        default: IN
+        enum: [IN, NOT_IN, STR_ENDS_WITH, STR_STARTS_WITH, STR_CONTAINS]
+        description: The constraint's operator.
+      values:
+        type: list
+        required: true
+        description: The values the context field is compared with.
+        example: ["${ctx.scope}"]
+      rollout:
+        type: string
+        default: "100"
+        pattern: "^(100|[1-9]?[0-9])$"
+        description: The share of matching users the strategy enables, as a string (0–100).
+      stickiness:
+        type: string
+        default: default
+        description: The rollout's stickiness (`default`, `userId`, `sessionId`, `random`, or a context field).
+      disabled:
+        type: boolean
+        default: false
+        description: Keep the strategy but switch it off.
+    http:
+      find:
+        path: "/api/admin/projects/{project}/features/{feature}/environments/{environment}/strategies"
+        match: { title: { param: title } }
+      create:
+        path: "/api/admin/projects/{project}/features/{feature}/environments/{environment}/strategies"
+        body: { name: flexibleRollout }
+      update:
+        method: PUT
+        path: "/api/admin/projects/{project}/features/{feature}/environments/{environment}/strategies/{id}"
+        body: { name: flexibleRollout }
+      delete: { path: "/api/admin/projects/{project}/features/{feature}/environments/{environment}/strategies/{id}" }
+      fields:
+        disabled: { param: disabled }
+        constraints:
+          - contextName: { param: context_name }
+            operator: { param: operator }
+            values: { param: values }
+            caseInsensitive: false
+            inverted: false
+        parameters:
+          rollout: { param: rollout }
+          stickiness: { param: stickiness }
+          groupId: { param: feature }
+    live:
+      params: { project: SPONSON_LIVE_UNLEASH_PROJECT, feature: SPONSON_LIVE_UNLEASH_FEATURE, environment: SPONSON_LIVE_UNLEASH_ENVIRONMENT }

package/recipes/upstash.yaml

@@ -0,0 +1,130 @@
+# yaml-language-server: $schema=../../../schema/recipe.schema.json
+# Upstash Developer API recipes (Redis). QStash has its own API and credential: recipes/qstash.yaml.
+# Format and checklist: docs/adr/0020-recipes.md, CONTRIBUTING.md "Adding a recipe".
+provider: upstash
+title: Upstash Redis
+category: queues
+verified_on: "2026-10-11"
+docs:
+  - title: Developer API authentication
+    url: https://upstash.com/docs/devops/developer-api/authentication
+  - title: Developer API introduction (supported accounts)
+    url: https://upstash.com/docs/devops/developer-api/introduction
+  - title: Create a Redis database (global)
+    url: https://upstash.com/docs/devops/developer-api/redis/create_database_global
+  - title: List Redis databases
+    url: https://upstash.com/docs/devops/developer-api/redis/list_databases
+  - title: Get a Redis database
+    url: https://upstash.com/docs/devops/developer-api/redis/get_database
+  - title: Delete a Redis database
+    url: https://upstash.com/docs/devops/developer-api/redis/delete_database
+  - title: Upstash CLI (UPSTASH_EMAIL, UPSTASH_API_KEY)
+    url: https://upstash.com/docs/agent-resources/cli
+  - title: Terraform upstash_redis_database (exported credentials)
+    url: https://upstash.com/docs/devops/terraform/resources/upstash_redis_database
+api:
+  base_url: https://api.upstash.com/v2
+  base_url_env: UPSTASH_API_URL
+  auth: { basic: { user_env: UPSTASH_EMAIL, password_env: UPSTASH_API_KEY } }
+detect:
+  deps: ["@upstash/redis"]
+  env: ["UPSTASH_REDIS_*"]
+  starter:
+    - op: redis_database
+      values: { name: "app-${ctx.scope}" }
+assumptions:
+  - id: UR1
+    verified: true
+    text: "The Developer API authenticates with HTTP Basic, the account's email as user and an API key as password; the Upstash CLI reads them from `UPSTASH_EMAIL` and `UPSTASH_API_KEY`. Accounts created through Vercel or Fly cannot use it."
+    source: https://upstash.com/docs/devops/developer-api/authentication
+  - id: UR2
+    verified: true
+    text: "`POST /v2/redis/database` with `{ database_name, platform, primary_region, read_regions?, plan?, tls?, eviction? }` creates a global database and answers it bare, with `database_id`, `database_name`, `endpoint`, `port` and `state`."
+    source: https://upstash.com/docs/devops/developer-api/redis/create_database_global
+  - id: UR3
+    verified: true
+    text: "`GET /v2/redis/databases` answers every database of the account as a bare array (no paging)."
+    source: https://upstash.com/docs/devops/developer-api/redis/list_databases
+  - id: UR4
+    verified: false
+    text: "Database names are unique in the account, so `database_name` identifies one; a create whose answer was lost is found by it before another is created. (Not documented: a second database with the same name makes `find.match` ambiguous, which is refused with PARAM_INVALID rather than guessed.)"
+  - id: UR5
+    verified: true
+    text: "`GET /v2/redis/database/{id}` answers the database, with its credentials unless `?credentials=hide` is sent."
+    source: https://upstash.com/docs/devops/developer-api/redis/get_database
+  - id: UR6
+    verified: false
+    text: "The credentials are the fields `password` and `rest_token` (the documented schema omits them; the Terraform resource and the CLI expose them), so they are readable on every run, not only from the create: ordinary sensitive outputs, not once-only ones."
+    source: https://upstash.com/docs/devops/terraform/resources/upstash_redis_database
+  - id: UR7
+    verified: true
+    text: "`DELETE /v2/redis/database/{id}` deletes the database and answers 200 `\"OK\"`."
+    source: https://upstash.com/docs/devops/developer-api/redis/delete_database
+  - id: UR8
+    verified: false
+    text: "A database that is gone answers 404 on GET and DELETE (only 200 is documented)."
+  - id: UR9
+    verified: false
+    text: "The database is usable when the create answers (`state: active` in the documented example); nothing waits for it."
+    source: https://upstash.com/docs/devops/developer-api/redis/create_database_global
+  - id: UR10
+    verified: false
+    text: "`endpoint` is the database's host name (`<name>.upstash.io`); the documented example shows only its first label, so check the output before building a URL from it."
+    source: https://upstash.com/docs/devops/developer-api/redis/create_database_global
+ops:
+  redis_database:
+    kind: resource
+    title: Redis database
+    summary: "A global Redis database per scope, such as `app-pr-42`, with its endpoint, port, password and REST token as outputs (the last two sensitive). Located by name; only its existence is compared for drift (region, plan and TLS are set on create and not compared); destroy deletes it and its data."
+    covers: [upstash-redis-database]
+    params:
+      name:
+        type: string
+        required: true
+        description: The database's name.
+        example: "app-${ctx.scope}"
+      platform:
+        type: string
+        default: aws
+        enum: [aws, gcp]
+        description: The cloud it runs on.
+      primary_region:
+        type: string
+        required: true
+        description: The primary region, such as `us-east-1` or `eu-west-1`.
+        example: us-east-1
+      read_regions:
+        type: list
+        description: Read replica regions.
+      plan:
+        type: string
+        description: The plan (`free`, `payg`, `fixed_…`); the account's default when left out.
+      tls:
+        type: boolean
+        default: true
+        description: Whether TLS is enabled.
+      eviction:
+        type: boolean
+        description: Whether keys are evicted when the database is full.
+    http:
+      find:
+        path: /redis/databases
+        match: { database_name: { param: name } }
+      read: { path: "/redis/database/{id}" }
+      create:
+        path: /redis/database
+        body:
+          platform: { param: platform }
+          primary_region: { param: primary_region }
+          read_regions: { param: read_regions }
+          plan: { param: plan }
+          tls: { param: tls }
+          eviction: { param: eviction }
+      id_path: /database_id
+      outputs:
+        endpoint: /endpoint
+        port: /port
+        password: { path: /password, sensitive: true }
+        rest_token: { path: /rest_token, sensitive: true }
+    live:
+      params: { primary_region: SPONSON_LIVE_UPSTASH_REGION }

package/recipes/vercel.yaml

@@ -0,0 +1,116 @@
+# yaml-language-server: $schema=../../../schema/recipe.schema.json
+# Vercel REST API recipes. Format and checklist: docs/adr/0020-recipes.md, CONTRIBUTING.md "Adding a recipe".
+# Environment variables and deployments have the first-class `vercel` adapter (vercel.env, vercel.deploy).
+provider: vercel
+title: Vercel
+category: dns
+verified_on: "2026-10-11"
+docs:
+  - title: Add a domain to a project
+    url: https://vercel.com/docs/rest-api/projects/add-a-domain-to-a-project
+  - title: Get a project domain
+    url: https://vercel.com/docs/rest-api/projects/get-a-project-domain
+  - title: Update a project domain
+    url: https://vercel.com/docs/rest-api/projects/update-a-project-domain
+  - title: Remove a domain from a project
+    url: https://vercel.com/docs/rest-api/projects/remove-a-domain-from-a-project
+  - title: Errors
+    url: https://vercel.com/docs/rest-api/errors
+  - title: CLI global options (VERCEL_TOKEN)
+    url: https://vercel.com/docs/cli/global-options
+  - title: Working with domains (verification)
+    url: https://vercel.com/docs/domains/working-with-domains
+api:
+  base_url: https://api.vercel.com
+  base_url_env: VERCEL_API_URL
+  auth: { bearer_env: VERCEL_TOKEN }
+assumptions:
+  - id: VD1
+    verified: true
+    text: "Requests authenticate as `Authorization: Bearer <token>`; the Vercel CLI reads the token from `VERCEL_TOKEN` (the built-in `vercel` adapter uses the same variable)."
+    source: https://vercel.com/docs/cli/global-options
+  - id: VD2
+    verified: true
+    text: "`POST /v10/projects/{idOrName}/domains?teamId=` with `{ name, gitBranch, redirect, redirectStatusCode }` adds the domain to the project and answers it bare: `{ name, apexName, projectId, verified, gitBranch, redirect, redirectStatusCode, verification[] }`."
+    source: https://vercel.com/docs/rest-api/projects/add-a-domain-to-a-project
+  - id: VD3
+    verified: true
+    text: "`GET /v9/projects/{idOrName}/domains/{domain}?teamId=` answers the same shape; the domain's name identifies it within the project, so the read path names it and a create whose answer was lost is found by it."
+    source: https://vercel.com/docs/rest-api/projects/get-a-project-domain
+  - id: VD4
+    verified: false
+    text: "A domain that is not on the project answers 404 on GET and DELETE (documented with no description)."
+    source: https://vercel.com/docs/rest-api/projects/get-a-project-domain
+  - id: VD5
+    verified: true
+    text: "`PATCH /v9/projects/{idOrName}/domains/{domain}` changes `gitBranch`, `redirect` and `redirectStatusCode`; `DELETE` on the same path removes the domain from the project (200, `{}`)."
+    source: https://vercel.com/docs/rest-api/projects/update-a-project-domain
+  - id: VD6
+    verified: true
+    text: "Adding a domain that is already on a project of the account answers 409 (and, for the same project, the description says 400): someone else's domain is never taken over by name, and the conflict surfaces as an error."
+    source: https://vercel.com/docs/rest-api/projects/add-a-domain-to-a-project
+  - id: VD7
+    verified: true
+    text: "`gitBranch` and `redirect` cannot be set together, and the production branch cannot be a `gitBranch` (400)."
+    source: https://vercel.com/docs/rest-api/projects/add-a-domain-to-a-project
+  - id: VD8
+    verified: true
+    text: "A domain the account does not own answers `verified: false` with a `verification` challenge (a TXT record) that must be completed before it serves traffic; a domain bought through Vercel needs none."
+    source: https://vercel.com/docs/domains/working-with-domains
+  - id: VD9
+    verified: false
+    text: "A free `<name>.vercel.app` domain that no other project uses is verified on the spot (`verified: true`)."
+  - id: VD10
+    verified: false
+    text: "Every account has a team id (personal accounts are Hobby teams), so `teamId` can always be sent; the recipe requires it."
+ops:
+  project_domain:
+    kind: resource
+    title: Branch-bound project domain
+    summary: "A domain on a Vercel project that serves one git branch's latest preview, such as `pr-42.preview.example.com` for `feat/x`: a stable preview hostname. Located by name; a console edit of its branch or redirect is drift; destroy removes it from the project. Its `verified` output says whether DNS verification is still needed (VD8)."
+    covers: [vercel-domain]
+    params:
+      project:
+        type: string
+        required: true
+        description: The project's id or name.
+        example: prj_12HKQaOmR5t5Uy6vdcQsNIiZgHGB
+      team_id:
+        type: string
+        required: true
+        pattern: "^team_[A-Za-z0-9]+$"
+        description: The team's id (`team_…`, under Settings → General).
+        example: team_1a2b3c4d5e6f7g8h9i0j1k2l
+      name:
+        type: string
+        required: true
+        pattern: "^[a-z0-9*.-]+$"
+        description: The domain, lower-case.
+        example: "${ctx.scope}.preview.example.com"
+      git_branch:
+        type: string
+        description: The git branch whose latest deployment the domain serves.
+        example: "${ctx.git.branch}"
+      redirect:
+        type: string
+        description: Redirect to this domain instead of serving a branch (not with `git_branch`).
+      redirect_status_code:
+        type: integer
+        enum: [301, 302, 307, 308]
+        description: The redirect's status code.
+    http:
+      read: { path: "/v9/projects/{project}/domains/{name}?teamId={team_id}" }
+      create:
+        path: "/v10/projects/{project}/domains?teamId={team_id}"
+        body: { name: { param: name } }
+      update: { method: PATCH }
+      id_path: /name
+      fields:
+        gitBranch: { param: git_branch }
+        redirect: { param: redirect }
+        redirectStatusCode: { param: redirect_status_code }
+      outputs: { verified: /verified, apex_name: /apexName }
+    sim:
+      id_from: name
+    live:
+      params: { project: SPONSON_LIVE_VERCEL_PROJECT, team_id: SPONSON_LIVE_VERCEL_TEAM_ID, name: SPONSON_LIVE_VERCEL_DOMAIN }