Beta

[steveseguin]

## PR Description

**Note:** The provided summary of code changes (diff) was empty, preventing a detailed, auto-generated description of the specific changes in this PR. The following provides a standard structure for a beta merge PR description. Please fill in the specific details based on the actual contents of the `beta` branch.

### Purpose

This Pull Request merges the `beta` branch into `main`. The `beta` branch contains features, fixes, and improvements developed and tested during the beta phase of the Social Stream Ninja project.

The primary goal of this merge is to integrate the stable and validated changes from the beta environment into the main production-ready codebase, preparing for the next official release or deployment.

### Key Changes

*(Please list the significant changes included in the `beta` branch here. Refer to commit messages, feature branches merged into beta, or internal release notes for the beta phase. Use bullet points.)*

*   [Example: Implemented core feature X (e.g., improved OBS overlay customization)]
*   [Example: Added support for social platform Y (e.g., integrated Kick chat)]
*   [Example: Refactored critical component Z for performance/maintainability (e.g., restructured API client)]
*   [Example: Fixed major bugs identified during beta testing (e.g., resolved TTS voice cutting out, fixed stream disconnection issues)]
*   [Example: Updated dependencies or build process]
*   [Example: Improved UI/UX for [specific area]]

### How to Test

*(Suggest specific areas or features for reviewers to test to ensure stability and correct functionality after the merge.)*

*   Verify core stream integration for supported platforms ([List platforms, e.g., Twitch, YouTube, Kick]).
*   Test the OBS overlay features ([List specific features, e.g., chat display, event alerts, custom styling]).
*   Check Text-to-Speech (TTS) functionality and settings.
*   Review API endpoints and their responses if relevant changes were made.
*   Test installation and setup process if applicable changes were included.
*   Perform general usage testing across different configurations.

### Considerations

*(Mention any potential impacts, required migration steps, or known issues associated with this merge.)*

*   [Example: Are there any database schema changes?]
*   [Example: Does this merge require users to update configuration files?]
*   [Example: Are there any known minor issues still being tracked from beta?]
*   [Example: Performance implications of new features.]

This merge represents the culmination of the beta development cycle. Reviewers are encouraged to thoroughly test the integrated features and fixes.