Skip to content

PR_26171_069 message TTS profile contract alignment#23

Merged
ToolboxAid merged 2 commits into
mainfrom
codex/pr-26171-069-message-tts-profile-contract-alignment
Jun 20, 2026
Merged

PR_26171_069 message TTS profile contract alignment#23
ToolboxAid merged 2 commits into
mainfrom
codex/pr-26171-069-message-tts-profile-contract-alignment

Conversation

@ToolboxAid

Copy link
Copy Markdown
Owner

Summary

  • Align Message Studio around a Messages parent table with Message Parts children, removing visible Message-owned Emotion Profile and Available TTS Profile side tables.
  • Add Message Studio Stop playback through the shared Message TTS service registry and TextToSpeechEngine.stop().
  • Expand TTS Studio default profile emotion settings so the example profiles expose Neutral, Happy, Angry, and Scared settings.
  • Add PR docs, required Codex reports, ownership checklist, parent-child checklist, validation report, and manual notes.

Validation

  • PASS: node --check toolbox/messages/messages.js
  • PASS: node --check toolbox/messages/message-tts-service-registry.js
  • PASS: node --check toolbox/text-to-speech/text2speech.js
  • PASS: node --check tests/playwright/tools/MessagesTool.spec.mjs
  • PASS: node --check tests/playwright/tools/TextToSpeechFunctional.spec.mjs
  • PASS: node --check tests/tools/Text2SpeechShell.test.mjs
  • PASS: node --test tests/tools/Text2SpeechShell.test.mjs
  • PASS: npx playwright test tests/playwright/tools/MessagesTool.spec.mjs tests/playwright/tools/TextToSpeechFunctional.spec.mjs --project=playwright --workers=1 --reporter=list
  • PASS: npm run test:workspace-v2 (legacy command name; Project Workspace validation)

ZIP

  • Path: tmp/PR_26171_069-message-tts-profile-contract-alignment_delta.zip
  • Size: 48487 bytes
  • Contents: PR docs, required reports, Message Studio/TTS Studio code updates, and targeted Message/TTS tests.

…ssage-tts-profile-contract-alignment

# Conflicts:
#	docs_build/dev/reports/codex_changed_files.txt
#	docs_build/dev/reports/codex_review.diff
@ToolboxAid ToolboxAid merged commit b31b319 into main Jun 20, 2026
1 check passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 98b8d0e9d6

ℹ️ 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".

Comment on lines +254 to +256
createTextToSpeechProfileEmotion({ emotion: "happy", pitch: 1.08, rate: 1.04 }),
createTextToSpeechProfileEmotion({ emotion: "angry", pitch: 0.96, rate: 1.08, volume: 1 }),
createTextToSpeechProfileEmotion({ emotion: "scared", pitch: 1.12, rate: 1.12, volume: 0.9 }),

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Use profile emotion settings for Message Studio playback

Adding the profile-owned Happy/Angry/Scared settings here does not make them usable by Message Studio: the message tool still loads separate /messages/emotion-profiles records and speakTarget() applies target.emotionProfile.pitch/rate/volume instead of looking up the selected TTS profile's emotionSettings. As a result, any Message Part intended to use these new per-profile settings (notably Happy or Scared, which are not in the message emotion seed data) cannot select or play with them, so the TTS-profile emotion contract is only reflected in TTS Studio output, not in Message playback.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants