Move release script out of public source

README.md

@@ -21,12 +21,11 @@ Taskbar Launcher is a small Windows tray launcher for folders, applications, scr
 TaskbarLauncher/
   App.xaml
   MainWindow.xaml
+  Assets/
   Models/
   Services/
   Views/
-  Tools/
   docs/
-  builds/        generated locally, ignored by Git
 ```
 
 ## Build
@@ -37,25 +36,9 @@ Requires the .NET 10 SDK on the developer machine.
 dotnet build
 ```
 
-## Release
+## Download
 
-Create the small framework-dependent release package:
-
-```powershell
-.\Tools\New-TaskbarLauncherRelease.ps1
-```
-
-Create a self-contained package that does not require users to install .NET:
-
-```powershell
-.\Tools\New-TaskbarLauncherRelease.ps1 -SelfContained
-```
-
-Release zips are written to:
-
-```text
-builds/releases/
-```
+Compiled downloads are published through Gitea Releases when a stable version is ready.
 
 ## Config Files
 
@@ -63,16 +46,16 @@ builds/releases/
 
 `config.example.json` is a public-safe sample config for documentation and reference. New users do not need to copy it; if `config.json` is missing, the app creates a clean starter config on first run.
 
-Personal test configs should stay in `config.json`; release packages do not include it unless the release script is run with `-IncludeCurrentConfig`.
+Personal test configs should stay in `config.json`; public release packages do not include private configs.
 
 ## Versioning
 
 The app version is controlled in `TaskbarLauncher.csproj`.
 
-Recommended release flow:
+Recommended release flow for maintainers:
 
 1. Update `<Version>` in `TaskbarLauncher.csproj`.
 2. Commit the change.
-3. Run `.\Tools\New-TaskbarLauncherRelease.ps1`.
+3. Build a release package locally.
 4. Tag the release, for example `v1.0.1`.
-5. Upload the generated zip to Gitea Releases.
+5. Upload the release zip to Gitea Releases.