fix: add explicit Sarvam WS/REST preference toggles

[mshivam019]

Summary

• Follow-up to merged Sarvam plugin work in feat: add Sarvam AI STT plugin #1046 (STT) and feat: add Sarvam AI TTS plugin #1038 (TTS): add explicit streaming preference toggles so users can choose WebSocket streaming or prefer REST/non-streaming behavior.
• Add streaming?: boolean support to both Sarvam STT and TTS, defaulting to current behavior (true), and fail fast with clear errors if .stream() is called while streaming is disabled.
• Update tests to include dummy API key unit coverage for toggle behavior, and make networked integration checks conditional on SARVAM_API_KEY so local verification works without secrets.

Why this is required

The original STT/TTS feature PRs established working WS and REST code paths, but they did not expose an explicit user-facing switch to prefer REST over WS when desired. In AgentSession, providers that advertise streaming are routed through .stream(); without a toggle users cannot opt into REST-first behavior even though those REST implementations already exist. This PR closes that gap with backwards-compatible defaults.

Changes

• STT:
  • add streaming?: boolean option and propagate it to capabilities
  • preserve the setting during updateOptions
  • guard .stream() when disabled with an actionable error message
• TTS:
  • add streaming?: boolean option and propagate it to capabilities
  • preserve the setting during updateOptions
  • guard .stream() when disabled with an actionable error message
• Tests:
  • add explicit non-streaming toggle tests using dummy API keys
  • integration suites run only when SARVAM_API_KEY is present
• Docs:
  • add STT and TTS usage examples for streaming: false

Verification

• LSP diagnostics: clean for updated TS files.
• Targeted tests:
  • pnpm -F @livekit/agents-plugin-sarvam exec vitest run src/stt.test.ts src/tts.test.ts
  • Result: pass with unit tests; integration tests are skipped when SARVAM_API_KEY is absent.

[changeset-bot]

🦋 Changeset detected

Latest commit: 933f1a6

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 20 packages

Name	Type
@livekit/agents-plugin-sarvam	Patch
@livekit/agents	Patch
@livekit/agents-plugin-anam	Patch
@livekit/agents-plugin-baseten	Patch
@livekit/agents-plugin-bey	Patch
@livekit/agents-plugin-cartesia	Patch
@livekit/agents-plugin-deepgram	Patch
@livekit/agents-plugin-elevenlabs	Patch
@livekit/agents-plugin-google	Patch
@livekit/agents-plugin-hedra	Patch
@livekit/agents-plugin-inworld	Patch
@livekit/agents-plugin-lemonslice	Patch
@livekit/agents-plugin-livekit	Patch
@livekit/agents-plugin-neuphonic	Patch
@livekit/agents-plugin-openai	Patch
@livekit/agents-plugin-resemble	Patch
@livekit/agents-plugin-rime	Patch
@livekit/agents-plugin-silero	Patch
@livekit/agents-plugin-xai	Patch
@livekit/agents-plugins-test	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 4 additional findings.

[mshivam019]

@toubatbrian this is a follow-up to #1046 and #1038 and closes an API gap in Sarvam STT/TTS: explicit streaming: false preference so users can choose REST over WS in AgentSession. Since the release PR #1049 is already open, could we land this before/with that release so the plugin ships with this toggle?