chore: regenerate examples from updated skills

[cursor]

Summary

Regenerated examples after elevenlabs/skills#119 merged (Add npm as an install option for the ElevenLabs CLI).

pnpm generate completed successfully in 12m 10s:

generated	verified	updated	failed
0	17	2	0

Generation table

• agents/expo/quickstart — updated
• agents/nextjs/guardrails — verified, no changes
• agents/nextjs/quickstart — verified, no changes
• dubbing/nextjs/quickstart — verified, no changes
• music/nextjs/quickstart — verified, no changes
• music/python/quickstart — verified, no changes
• music/typescript/quickstart — verified, no changes
• sound-effects/nextjs/quickstart — verified, no changes
• sound-effects/python/quickstart — verified, no changes
• sound-effects/typescript/quickstart — verified, no changes
• speech-engine/nextjs/quickstart — verified, no changes
• speech-to-text/nextjs/realtime — updated
• speech-to-text/python/quickstart — verified, no changes
• speech-to-text/typescript/quickstart — verified, no changes
• text-to-speech/nextjs/quickstart — verified, no changes
• text-to-speech/python/quickstart — verified, no changes
• text-to-speech/typescript/quickstart — verified, no changes
• voice-changer/nextjs/quickstart — verified, no changes
• voice-isolator/nextjs/quickstart — verified, no changes

Directories that changed (git diff --stat)

 agents/expo/quickstart/example/package.json        |   8 +
 speech-to-text/nextjs/realtime/example/app/page.tsx | 167 +++++++++------------
 2 files changed, 79 insertions(+), 96 deletions(-)

Are the changes meaningful?

Yes, with a caveat that they are not about the triggering skills change (npm as a CLI install option is docs-only and did not require example code updates).

What landed:

1. agents/expo/quickstart — pins livekit-client to 2.16.1 via npm overrides and pnpm.overrides. This is a real compatibility pin used by ElevenAgents WebRTC clients; worth keeping.
2. speech-to-text/nextjs/realtime — more useful token/error handling (parse API error JSON, surface Error.message, include an error status label). Mixed in with some UI restyle (removed Clear History, simpler layout). Net improvement, not churn-only.

Test plan

• pnpm generate completed with 0 failures
• Spot-check Expo agents quickstart still installs with the livekit-client override
• Spot-check realtime STT Start/Stop and token error path

  

[tadaspetra]

Livekit shouldn't need to be pinned anymore. Double check the version of this example and why agent thought this needed to be done.

[cursor]

PR Summary

Low Risk
Changes are limited to example apps (dependency override and demo UI/error handling), with no production auth or data-path changes.

Overview
Regenerated example apps touch two areas: dependency pinning for the Expo agents quickstart and demo UX for the Next.js realtime Scribe page.

The Expo package.json now forces livekit-client to 2.16.1 through both top-level overrides and pnpm.overrides, so npm and pnpm installs resolve a known-good WebRTC client version for ElevenAgents-style stacks.

The realtime transcription page.tsx improves start flow and errors: token fetch parses JSON safely, surfaces API error text when present, and shows Error.message in the UI. A statusLabel helper drives Connecting / Transcribing / Connected / Error / Disconnected next to Start/Stop. The layout is simplified (single primary button styling, lighter transcript/history presentation, LiveWaveform no longer passes processing, and Clear History was removed).

^{Reviewed by Cursor Bugbot for commit 7dc4881. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7dc4881. Configure here.}

[cursor]

Outdated livekit-client version pin

Medium Severity

The new livekit-client 2.16.1 overrides and pnpm.overrides reintroduce a temporary WebRTC workaround that is no longer required. Sibling Next.js agent examples using the same @elevenlabs/react range do not pin it, so this example can lock users onto an old client and hide the current SDK/server resolution.

 

^{Reviewed by Cursor Bugbot for commit 7dc4881. Configure here.}

[tadaspetra]

Skill caused the pin