PR_26171_BETA_069 message tts profile contract alignment#25
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 06b262d25e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| description: "Balanced local browser playback option until authored TTS profiles are available.", | ||
| language: "en-US", | ||
| name: "Browser Speech Default", | ||
| name: "Default Balanced TTS Profile", |
There was a problem hiding this comment.
Migrate the old TTS seed name instead of duplicating it
In an existing Messages SQLite database created before this commit, changing the seed name here causes seedDefaults() to miss the previous Browser Speech Default row because it only checks findTtsProfileByName(profile.name), then inserts a second active default profile. Since listTtsProfiles() orders by name and Message Studio chooses the first active TTS profile as the default, those existing databases will keep using/displaying Browser Speech Default ahead of the new balanced profile rather than aligning to the new contract. Add a migration/rename path for the old seed instead of treating the new label as a separate seed.
Useful? React with 👍 / 👎.
Summary
TEAM Ownership
Validation
Note:
npm run test:workspace-v2is a legacy command name; user-facing language remains Project Workspace / Game Hub.Reports
ZIP