feat(setup): enhance setup and release automation with platform-specific scripts

Author: Maik Roland Damm

CHANGELOG.md

@@ -9,8 +9,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 
+- **Interactive setup scripts**: platform-specific post-clone setup helpers under `scripts/setup/` for Linux, macOS and Windows. They install/check Rust, `wasm32-unknown-unknown`, Trunk, Tauri CLI, Node/npm frontend assets, OS-native Tauri dependencies, and optional verification/bundle builds.
+- **Native release script counterparts**: PowerShell and Command Prompt release entrypoints (`scripts/release.ps1`, `scripts/release.cmd`, `scripts/release-windows.*`) plus a macOS launcher (`scripts/release-macos.sh`). The PowerShell modules under `scripts/release/*.ps1` mirror the Bash release pipeline for version bumps, CHANGELOG finalization, Tauri builds, artifact discovery, and GitHub uploads.
+
 ### Changed
 
+- **Docs**: README, developer setup, build guide, and `.env.release.example` now document the setup and cross-platform release automation paths.
+
 ### Fixed
 
 ### Removed

README.md

@@ -76,12 +76,12 @@ BLXCode is early-stage open source. Core desktop, workspace, memory, plans, task
 After cloning, run the setup script for your platform:
 
 ```bash
-./scripts/setup-linux.sh
-./scripts/setup-macos.sh
+./scripts/setup/setup-linux.sh
+./scripts/setup/setup-macos.sh
 ```
 
 ```powershell
-powershell -ExecutionPolicy Bypass -File scripts/setup-windows.ps1
+powershell -ExecutionPolicy Bypass -File scripts/setup/setup-windows.ps1
 ```
 
 Use `--check-only` to inspect missing prerequisites without installing anything, or `--with-bundle` to run `cargo tauri build` after the default checks.
@@ -122,6 +122,22 @@ The Tauri dev command starts Trunk automatically through `src-tauri/tauri.conf.j
 cargo tauri build
 ```
 
+### Release Automation
+
+Use the release scripts for local bundle builds, version bumps, changelog finalization, tags, and GitHub release uploads:
+
+```bash
+./scripts/release.sh
+./scripts/release-macos.sh
+```
+
+```powershell
+scripts\release.cmd
+powershell -ExecutionPolicy Bypass -File scripts/release.ps1 --platform windows
+```
+
+Release scripts are unsigned by default for local builds. Copy `.env.release.example` to `.env.release` only when you need signing keys, notarization credentials, or GitHub upload overrides.
+
 ### Useful Checks
 
 ```bash

docs/developer/setup.md

@@ -12,12 +12,12 @@ BLXCode is a two-crate Rust workspace:
 After cloning, you can let the platform setup script install/check the local toolchain and run the default verification:
 
 ```bash
-./scripts/setup-linux.sh
-./scripts/setup-macos.sh
+./scripts/setup/setup-linux.sh
+./scripts/setup/setup-macos.sh
 ```
 
 ```powershell
-powershell -ExecutionPolicy Bypass -File scripts/setup-windows.ps1
+powershell -ExecutionPolicy Bypass -File scripts/setup/setup-windows.ps1
 ```
 
 Useful options are `--check-only`, `--skip-system`, `--no-verify`, and `--with-bundle`.
@@ -86,6 +86,22 @@ cargo tauri build
 
 Bundle configuration lives in `src-tauri/tauri.conf.json`.
 
+## Release Automation
+
+Release helpers live at the repo root under `scripts/` and share the same option set where possible:
+
+```bash
+./scripts/release.sh --help
+./scripts/release-macos.sh --help
+```
+
+```powershell
+scripts\release.cmd --help
+powershell -ExecutionPolicy Bypass -File scripts/release.ps1 --help
+```
+
+The Bash pipeline remains the Linux/macOS path. The PowerShell pipeline mirrors it for native Windows releases and is split into matching modules under `scripts/release/*.ps1` for common helpers, version bumping, changelog finalization, build preparation, Linux target handling, and GitHub uploads.
+
 ## Important Config Files
 
 - `Cargo.toml`: workspace and frontend crate manifest.