feat: (regen) diarization v2 batch GA, listen-provider dedup, think/models route fix (#499)

## Summary
Regenerate the SDK from the 2026-05-14 Fern build and reconcile the
temporarily-frozen patches against the new generator output.

### Re-applied patches (existing freezes)
- **`package.json`** — kept `@types/node ^20.17.57` pin, re-added
`@commitlint/cli`, `@commitlint/config-conventional`, `tsx`,
`playwright`, `vite`, `terser` (generator's `5.2.1` version bump kept).
- **`src/api/.../keys/client/Client.ts`** — restored optional `request?`
parameter to `manage.v1.projects.keys.create` (3 spots).
- **`src/api/types/CreateKeyV1Request.ts`** — restored legacy
`CreateKeyV1RequestOne` alias.
- **`src/api/.../AgentV1Settings.ts`** — restored interface form of
`Agent` with named sub-types + `AgentReference = Agent | string` opt-in
alias.
- **`src/api/.../AgentV1SettingsAgentListenProvider.ts`** — restored
one-line alias to `AgentV1SettingsAgentContextListenProvider`.

### New freezes added this cycle
- **`biome.json`** — generator emits `"vcs": { "enabled": false }`,
which caused biome lint to scan the gitignored
`examples/browser/deepgram.js` bundle. Restored `useIgnoreFile: true`
and added to `.fernignore` so this patch survives the next regen.
Documented in `AGENTS.md`.
- **`src/api/.../AgentV1SettingsAgentContextListenProvider.ts`** — the
2026-05-14 regen dedup'd listen-provider sub-types into top-level
`DeepgramListenProviderV1` / `DeepgramListenProviderV2` and dropped the
nested `AgentV1SettingsAgentContextListenProviderV2.LanguageHint`
namespace path. Restored the nested namespace as a one-line alias `type
LanguageHint = DeepgramListenProviderV2.LanguageHint`. Regression
coverage added in `tests/unit/compat-aliases.test.ts`.
- **`src/Client.ts`** — generator switched the `client.fetch()`
passthrough helper's default `baseUrl` from `env.base`
(api.deepgram.com) to `env.agentRest` (agent.deepgram.com) after the
upstream spec introduced the new `agentRest` slot for the think-models
endpoint. The passthrough should default to the canonical Deepgram REST
host. Reverted locally; likely a Fern generator artifact — drop this
freeze when the upstream fix lands.

### Patches dropped
None — every prior patch still addresses surface the new regen misses.

### Notable generator changes
- **Intentional fix from
[deepgram-docs#886](deepgram/deepgram-docs#886)
+ [#887](deepgram/deepgram-docs#887:
`DeepgramEnvironment.Agent` removed; `Production` gained an `agentRest`
slot; the `agent.v1.settings.think.models` endpoint now routes via HTTPS
instead of WSS. Not a breaking change in practice — the old
`DeepgramEnvironment.Agent` would have routed every REST client at
`https://agent.deepgram.com` (404 on `/v1/listen`, etc.) and
`think/models` was misrouted over WSS, so no consumer could have had a
working flow through it.
- New optional `diarize_model` field on `ListenV1RequestUrl` +
`MediaTranscribeRequestOctetStream` (purely additive); new
`MediaTranscribeRequestDiarizeModel` enum.
- New top-level `DeepgramListenProviderV1` / `DeepgramListenProviderV2`
exports.
- Generator version bumped to `5.2.1`.
- `pnpm-lock.yaml` rebuilt after the `package.json` reconciliation.

## Test plan
- [x] `make build` passes (CJS + ESM + ESM validation)
- [x] `make test` passes (535 unit tests + 132 wire tests, including 2
new regression cases for the `LanguageHint` shim)
- [x] `make test-esm` passes (5 tests)
- [x] `make lint` passes (warnings only, no errors)
- [x] `make examples` — 30/36 pass against the real API; remaining 6
failures are env-config (missing `DEEPGRAM_PROJECT_ID`) or transient
network, not regen-related
- [x] Example 9 (Voice Agent) exercises the rerouted
`agent.v1.settings.think.models.list()` endpoint and passes end-to-end
- [x] All `.bak` files removed; `.fernignore` paths restored from `.bak`
back to originals (plus 2 new freezes for `biome.json` and
`AgentV1SettingsAgentContextListenProvider.ts`, plus 1 local-patch
freeze for `Client.ts`)

Author: GregHolmes

.fern/metadata.json

@@ -11,8 +11,8 @@
         "shouldGenerateWebsocketClients": true,
         "enableForwardCompatibleEnums": true
     },
-    "originGitCommit": "d1854cf6d560a0e27c9f46c1d83a6d7d9924f045",
+    "originGitCommit": "abcbb3b91ae2fb48a85a3db83a94865804395740",
     "originGitCommitIsDirty": true,
     "invokedBy": "manual",
-    "sdkVersion": "5.2.0"
+    "sdkVersion": "5.2.1"
 }

.fernignore

@@ -96,3 +96,29 @@ src/api/resources/agent/resources/v1/types/AgentV1Settings.ts
 # the new V2. Regression coverage in tests/unit/compat-aliases.test.ts.
 # Swap to .bak before regen.
 src/api/resources/agent/resources/v1/types/AgentV1SettingsAgentListenProvider.ts
+
+# biome.json: Fern's generator emits `"vcs": { "enabled": false }`, which makes
+# biome lint every tracked-or-untracked file under the repo — including the
+# `examples/browser/deepgram.js` bundle produced by `make browser-serve`, which
+# is .gitignored but not biome-ignored. We restore `useIgnoreFile: true` so the
+# generated browser artifact stays out of lint. Swap to .bak before regen.
+biome.json
+
+# src/api/resources/agent/resources/v1/types/AgentV1SettingsAgentContextListenProvider.ts:
+# the 2026-05-14 regen consolidated listen-provider sub-types into top-level
+# DeepgramListenProviderV1/V2 and dropped the nested
+# `AgentV1SettingsAgentContextListenProviderV2.LanguageHint` namespace path.
+# We restore the nested namespace as a one-line alias to
+# DeepgramListenProviderV2.LanguageHint so deep imports keep resolving.
+# Regression coverage in tests/unit/compat-aliases.test.ts.
+# Swap to .bak before regen.
+src/api/resources/agent/resources/v1/types/AgentV1SettingsAgentContextListenProvider.ts
+
+# src/Client.ts: the 2026-05-14 regen switched the `client.fetch()` passthrough
+# helper's default baseUrl from `base` (api.deepgram.com) to `agentRest`
+# (agent.deepgram.com) after the upstream spec introduced the new agentRest
+# slot. The passthrough is documented as the catch-all for endpoints not yet
+# supported in the SDK and should default to the canonical Deepgram REST host.
+# Likely a Fern generator artifact — when the upstream fix lands, drop this
+# entry. Swap to .bak before regen.
+src/Client.ts

AGENTS.md

@@ -64,6 +64,9 @@ Current temporarily frozen files:
 - `src/api/types/CreateKeyV1Request.ts` — preserve the old exported `CreateKeyV1RequestOne` alias alongside `CreateKeyV1Request` so existing type imports keep compiling.
 - `src/api/resources/agent/resources/v1/types/AgentV1Settings.ts` — backward-compat patch for the `AgentV1Settings.Agent` namespace. The 2026-05-06 regen restructured `Agent` from an interface with named sub-types into a union with anonymous shapes plus a string variant (`{...} | string`) for the new agent-by-ID-string flow. We restore the original interface form so existing imports of the sub-types (`Agent.Context`, `Agent.Listen`, `Agent.Think`, `Agent.Speak`, `Agent.Context.Messages.Item`) AND direct field reads (`settings.agent.context`, `.greeting`, etc.) keep compiling in TS strict mode without a `typeof` narrowing guard. The new agent-by-ID-string variant is surfaced as the opt-in `AgentReference = Agent | string` alias for callers who want to pass a string ID at the type level. Mirrors the Python SDK's compat shims for the same regen. Regression coverage in `tests/unit/compat-aliases.test.ts`.
 - `src/api/resources/agent/resources/v1/types/AgentV1SettingsAgentListenProvider.ts` — backward-compat alias for the type renamed by the 2026-05-06 regen to `AgentV1SettingsAgentContextListenProvider`. The new V2 only adds an optional `language_hint` field, so the regenerated duplicate is replaced with a one-line `type AgentV1SettingsAgentListenProvider = AgentV1SettingsAgentContextListenProvider` (plus namespace merge for `.V1`/`.V2` access). Purely additive at the type level — pinned-name callers (`const p: AgentV1SettingsAgentListenProvider = ...`) keep compiling without a cast. Regression coverage in `tests/unit/compat-aliases.test.ts`.
+- `biome.json` — Fern's generator emits `"vcs": { "enabled": false }`, which makes biome lint every tracked-or-untracked file under the repo, including `examples/browser/deepgram.js` (the bundle produced by `make browser-serve`, which is `.gitignore`d but not biome-ignored). We restore `clientKind: "git"`, `enabled: true`, `useIgnoreFile: true` so generated browser artifacts stay out of lint.
+- `src/api/resources/agent/resources/v1/types/AgentV1SettingsAgentContextListenProvider.ts` — backward-compat shim for the listen-provider dedup in the 2026-05-14 regen. The new spec consolidated 5 PascalCase listen-provider types into top-level `DeepgramListenProviderV1` / `DeepgramListenProviderV2` and dropped the nested `AgentV1SettingsAgentContextListenProviderV2.LanguageHint` namespace path. We restore the nested namespace as a one-line alias `type LanguageHint = DeepgramListenProviderV2.LanguageHint` inside the outer namespace so deep import paths keep resolving. Regression coverage in `tests/unit/compat-aliases.test.ts`.
+- `src/Client.ts` — patch for the `client.fetch()` passthrough helper's default `baseUrl`. The 2026-05-14 regen switched this default from `env.base` (api.deepgram.com) to `env.agentRest` (agent.deepgram.com) after the upstream spec introduced the new `agentRest` slot for the think-models endpoint. The passthrough is documented as the catch-all for "endpoints not yet supported in the SDK" and should default to the canonical Deepgram REST host, not the agent host. Likely a Fern generator artifact — when the upstream fix lands, drop this entry.
 
 **Note:** If you need to patch a Fern-generated file, add it to `.fernignore` with a comment describing the patch, and add it to the "temporarily frozen" list above.
 

package.json

@@ -1,6 +1,6 @@
 {
     "name": "@deepgram/sdk",
-    "version": "5.2.0",
+    "version": "5.2.1",
     "private": false,
     "repository": {
         "type": "git",