feat: ship 1.0.8.0 release automation and runtime overhaul

- reduce ASAR IO overhead with streamed archive reads, buffered copies, faster relative-path handling and placeholder integrity records
- fix in-place app.asar.unpacked packing/extraction self-copy cases that caused locked-file failures
- tighten JS patch discovery with candidate bundle filters and search hints
- require prebuilt remote-panel dist artifacts and clean up embedded bridge/script packaging
- add unified build entrypoints for PowerShell, cmd and bash and move native CMake output under .tmp
- add release metadata validation, changelog section extraction, pre-commit hook and GitHub Actions validation/release pipelines
- make CHANGELOG the source of truth for release notes and document the tag-driven release flow
- add updater release notes UI with latest/full changelog loading and localize the new update strings
- modularize bridge renderer scripts, add installed apps and game status sync, and support remote launch/stop commands
- centralize bridge protocol, IPC and WebSocket constants and improve LAN IP selection for QR pairing
- refactor remote panel controls/state enums, persist accent color, polish library/session UI and refresh assets

CONTRIBUTING.md

@@ -8,6 +8,7 @@ Thank you for your interest in the WandEnhancer project! This document provides
 - [Bug Reports](#bug-reports)
 - [Feature Suggestions](#feature-suggestions)
 - [Creating a Pull Request](#creating-a-pull-request)
+- [Release Process](#release-process)
 - [Code Style](#code-style)
 - [Testing](#testing)
 - [License](#license)
@@ -82,6 +83,22 @@ Suggestions for new features or improvements are welcome! Create an Issue descri
 
 7. In the Pull Request description, explain the changes made and why they're necessary.
 
+## Release Process
+
+1. Update `WandEnhancer/Properties/AssemblyInfo.cs`.
+2. Add a new top section with the same version to `CHANGELOG.md`.
+3. Configure local hooks once:
+   ```
+   git config core.hooksPath .githooks
+   ```
+4. Commit and push the version/changelog changes.
+5. Create and push a tag matching the same version exactly, for example:
+   ```
+   git tag 1.0.8.0
+   git push origin 1.0.8.0
+   ```
+6. GitHub Actions will validate the version, build the project, extract the matching changelog section, and publish the release automatically.
+
 ## Code Style
 
 - Use C# naming conventions: