Repository navigation
chore(frontend): add the Tavus steering live verification script - #86
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the LIVE Tavus steering verification script used on 2026-10-09 (spike L1 to L8 of
tavus-single-session-interview) underscripts/live/, with a README. It SPENDS REAL TAVUS CREDITS and needs the owner's explicit authorization each time; it is never run by tests or CI (rg scripts/live testsis empty).tavus-steering-verify.mjsjoins ONE existing Tavus conversation as a Daily participant (video off, mic off, headless Chromium with fake devices), exercises the data-channel interactions (steer,leave,observescenarios) and prints a JSON summary. It never creates or ends a conversation: the caller does that from the api side so the Tavus key never reaches this process. It has no env access and no auth header; the conversation id is printed as its last four characters and the room URL as<redacted>. Output goes under the OS temp directory (--outoverrides).letthat is always reassigned, a commented empty catch).Provenance
The original parked file was lost with a scratchpad reset, so this is the version recovered from the transcript of the agent that first wrote it; it may differ from the 2026-10-09 run by later small edits (noted in the README). The api-side helper
spike.phpwas not recoverable and is not included.Verification
bun run lint0 errors (3 pre-existing warnings inInput.vue), prettier clean. The script was never run.