fix(tts): real Persian Gemini speech on Cloudflare runtime - #66
Merged
Conversation
AmirMotefaker
marked this pull request as ready for review
September 5, 2026 10:03
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.
Implements Issue #65 and fixes the real-browser stable blocker found during Issue #61.
Root cause
The preview Worker intentionally returned HTTP 503 for every
/api/ttscall, so Chrome had to fall back to Web Speech. On the tested Windows Chrome environment no usablefa/fa-IRvoice exists, making speech acceptance impossible.Fix
cloudflare/worker.mjs;Sulafatand maleIapetuspreserved;audio/wav;GEMINI_API_KEYis bound only to the isolated Cloudflare Worker, never bundled into the extension;/healthnow reports actual Gemini speech readiness;Safety
After CI passes, Cloudflare preview must prove real audio E2E before merge. Then a new exact-main stable candidate will be generated for Chrome/Edge acceptance.
Refs #65 #61