Beta sync - superficial tweaks

[steveseguin]

# Beta sync - superficial tweaks

## Purpose

This Pull Request aims to synchronize a collection of minor adjustments and refinements from the `beta` branch into the `main` branch. The primary goal is to integrate "superficial tweaks" that enhance the overall stability, user experience, and code hygiene of the Raspberry Ninja project without introducing major new features or significant architectural changes.

## Key Changes

*(Note: The detailed summary of code changes (diff) was not provided in the input. This section outlines typical changes implied by "superficial tweaks" and should be precisely populated by the author of the PR based on the actual modifications.)*

Based on the PR title "Beta sync - superficial tweaks", the changes likely include:

*   **Minor Bug Fixes:** Addressing small issues identified during the beta phase that affect stability or specific functionalities (e.g., social stream parsing, API responses, TTS playback, overlay rendering).
*   **UI/UX Refinements:** Adjustments to front-end components such as `dock.html` or `overlay.html` for better responsiveness, alignment, or visual consistency. This could involve CSS adjustments or minor HTML structure changes.
*   **Code Cleanup/Refactoring:** Small-scale refactorings for improved readability, maintainability, or adherence to coding standards, without altering existing behavior.
*   **Text/Label Updates:** Corrections or improvements to user-facing text, labels, or error messages.
*   **Performance Optimizations:** Very minor optimizations that don't fundamentally change core logic.

Please refer to the actual commit history in the `beta` branch for the precise list of changes included in this sync.

## Context/Why

These changes represent iterative improvements and fixes that have been tested and refined within the `beta` environment. Integrating them into `main` ensures that the primary development branch benefits from these enhancements, contributing to a more polished, robust, and stable "Raspberry Ninja" experience for all users. It also helps keep the `main` branch up-to-date with the latest minor improvements from ongoing development.

## How to Test

To verify the changes introduced by this PR, reviewers should:

1.  **Deploy the `main` branch with these changes.**
2.  **Perform general functional testing** across key "Raspberry Ninja" features, including:
    *   Connecting and monitoring social streams (Twitch, YouTube, etc.).
    *   Testing Text-to-Speech (TTS) functionality.
    *   Verifying the display and interaction of the overlay (`overlay.html`).
    *   Interacting with the API endpoints.
    *   Checking the `dock.html` interface for any visual inconsistencies or regressions.
3.  **Pay close attention to subtle details:** Given the "superficial" nature, specifically look for improvements in UI elements, text displays, error messages, and overall responsiveness that may have been targeted.
4.  **Review application logs** for any new warnings, errors, or unexpected behavior.

## Considerations

*   As these are "superficial tweaks," the risk of major regressions is expected to be low. However, thorough testing is still recommended to ensure no unforeseen side effects are introduced.
*   This PR primarily focuses on integrating existing refinements from the `beta` branch rather than introducing new, untested features.