Remove dev-only notes from public release

README.md

@@ -8,6 +8,8 @@ Download the compiled Windows release from:
 
 [Taskbar Launcher Releases](https://git.mget.ca/MGET/Taskbar-Launcher/releases)
 
+Current stable release: `v1.0.2`
+
 ## Features
 
 - System tray launcher
@@ -36,6 +38,10 @@ Download the compiled Windows release from:
 - Optional Start with Windows shortcut
 - Windows light/dark theme support
 
+## Latest Stable
+
+`v1.0.2` adds the newer launcher management and polish work from the development builds, including recent items, pinned items, drag/drop item creation, item duplication, item notes, target validation, selected item import/export, run-as-administrator support, working folders, start-minimized launch options, launcher tooltips, and the refreshed Settings layout.
+
 ## Screenshots
 
 ### Launcher Popup
@@ -88,5 +94,5 @@ Recommended release flow for maintainers:
 1. Update `<Version>` in `TaskbarLauncher.csproj`.
 2. Commit the change.
 3. Build a release package locally.
-4. Tag the release, for example `v1.0.1`.
+4. Tag the release, for example `v1.0.2`.
 5. Upload the release zip to Gitea Releases.

TaskbarLauncher.csproj

@@ -11,10 +11,10 @@
     <IncludeSourceRevisionInInformationalVersion>false</IncludeSourceRevisionInInformationalVersion>
     <Authors>Ray Berezowski</Authors>
     <ApplicationIcon>Assets\AppIcon.ico</ApplicationIcon>
-    <Version>1.0.1</Version>
+    <Version>1.0.2</Version>
-    <AssemblyVersion>1.0.1.22</AssemblyVersion>
+    <AssemblyVersion>1.0.2.0</AssemblyVersion>
-    <FileVersion>1.0.1.22</FileVersion>
+    <FileVersion>1.0.2.0</FileVersion>
-    <InformationalVersion>1.0.1</InformationalVersion>
+    <InformationalVersion>1.0.2</InformationalVersion>
   </PropertyGroup>
 
   <ItemGroup>

docs/DEV-NOTES.md

@@ -1,47 +0,0 @@
-# Developer Notes
-
-This document is for the `dev` branch only. Do not publish it on `main`.
-
-## Screenshot and Testing Startup Switches
-
-Taskbar Launcher supports a few command-line switches to open specific UI surfaces for documentation screenshots and manual testing:
-
-```powershell
-TaskbarLauncher.exe --show-settings
-TaskbarLauncher.exe --show-about
-TaskbarLauncher.exe --show-launcher
-```
-
-- `--show-settings` opens the Settings window after startup.
-- `--show-about` opens the About window after startup.
-- `--show-launcher` opens the launcher popup after startup.
-
-These switches are not part of the normal user workflow. They exist so development and documentation captures can be repeated cleanly.
-
-## Future Ideas
-
-These ideas are intentionally tracked on `dev` only. Do not publish them on `main` until a feature is built, tested, and ready for users.
-
-### Open All for Menu Sections
-
-Add a simple right-click action on menu and submenu headers:
-
-- `Open All`
-
-Expected behavior:
-
-- Right-click a top-level menu or submenu title.
-- Click `Open All`.
-- Launch each direct child item in that section.
-- For nested submenus, decide later whether `Open All` should include only direct items or recursively include nested children.
-- Skip unsupported items safely and show/log a clear result if something cannot be opened.
-
-This keeps Taskbar Launcher focused as a launcher. It gives project-style behavior without adding a full project dashboard.
-
-### Project Launcher Concept
-
-Parked for later as a possible personal/custom feature:
-
-- Project item type with actions for folder, VS Code, terminal, docs, Git/Gitea page, local server, Docker Compose, and helper scripts.
-- Could become useful, but it is larger than the current public app direction.
-- Do not start this until the simpler `Open All` behavior is tested and proves insufficient.

docs/INSTALL.md

@@ -1,5 +1,7 @@
 # Install and Use Taskbar Launcher
 
+Current stable release: `v1.0.2`
+
 ## Small Package
 
 The small package requires:

docs/RELEASE.md

@@ -21,6 +21,7 @@ Examples:
 
 - `1.0.0`: first stable release
 - `1.0.1`: bug fix
+- `1.0.2`: tested feature and polish release
 - `1.1.0`: new feature
 
 Update version fields in:
@@ -37,9 +38,9 @@ TaskbarLauncher.csproj
 4. Tag the release:
 
 ```powershell
-git tag v1.0.0
+git tag v1.0.2
 git push origin main
-git push origin v1.0.0
+git push origin v1.0.2
 ```
 
 5. In Gitea, create a release from the tag.