Beta

[steveseguin]

# Beta

This PR merges the `beta` branch into `main`, incorporating a collection of changes developed during the recent beta phase.

## Purpose

[**Describe the overall goal of the beta phase and this merge.** Examples:
- To integrate a significant set of new features and improvements tested in the beta environment.
- To stabilize the main branch with bug fixes and performance enhancements gathered during beta testing.
- To prepare for the next major release by consolidating all changes from the beta branch.]

## Key Changes

This PR includes numerous modifications across the project. Key areas impacted include:

*   **[Major Feature/Component 1]:** Summarize changes related to this area (e.g., "Implemented new [feature name]", "Refactored [module name]", "Improved [specific functionality]").
*   **[Major Feature/Component 2]:** Summarize changes (e.g., "Added support for [new platform/API]", "Optimized [performance critical section]").
*   **[Bug Fixes/Improvements]:** Mention general categories of fixes (e.g., "Resolved various issues identified during beta testing", "Improved UI responsiveness", "Enhanced error handling for [specific integration]").
*   **[Configuration/Build]:** Note any changes to setup or build processes if applicable.

[**Note:** A detailed list of all individual commits in the beta branch provides further specifics on individual changes.]

## How to Test

[**Suggest specific steps for reviewers to test the changes.** Examples:
- Pull the `beta` branch locally and build the application.
- Verify core functionalities: [List essential features like stream display, overlay activation, TTS].
- Test new features: [List specific new features added and steps to try them].
- Check common use cases: [Describe typical scenarios users would encounter].
- Review console logs for errors.]

## Considerations

*   **[Potential Impact]:** Mention any known or potential impacts (e.g., "Requires re-configuration of X setting", "May introduce minor changes in Y's appearance").
*   **[Dependencies]:** Note any updated or new dependencies if applicable.
*   **[Known Issues]:** List any known issues that are being merged but might be addressed in subsequent PRs.

---

[**Optional:** Add any other relevant context or notes about the beta phase or this merge.]