Rename project to GoSentry

Rename the application, Go module path, command package, build artifacts, resource script, and embedded icon assets from PySentry/pysentry to GoSentry/gosentry.

Move portable settings to gosentry.yaml while reading legacy pysentry.yaml during the transition, then rewrite settings under the new name.

Update Windows and Linux autostart integration to use GoSentry names while cleaning up legacy PySentry registry, desktop-entry, and systemd artifacts.

Refresh README, architecture notes, roadmap, changelog, and release examples for version 0.3.0.

docs/ARCHITECTURE.md

@@ -1,6 +1,6 @@
-# PySentry Architecture
+# GoSentry Architecture
 
-This document shows the current component interaction model. PySentry is still a
+This document shows the current component interaction model. GoSentry is still a
 single desktop process: the GUI, scheduler, storage, and command runner live in
 one application and communicate through Go function calls and shared in-memory
 job state.
@@ -15,7 +15,7 @@ flowchart LR
     scheduler["src/core Scheduler - @every and cron timing"]
     runner["src/core Runner - shell command execution"]
     autostart["src/core Autostart - Windows Startup shortcut / Linux desktop startup"]
-    config["pysentry.yaml - application settings"]
+    config["gosentry.yaml - application settings"]
     jobs["jobs.yaml - job definitions"]
     logs["logs_dir - per-run command output logs"]
     shell["Platform shell - cmd.exe /C or sh -c"]
@@ -41,8 +41,8 @@ flowchart LR
 ## Main Flows
 
 1. Startup:
-   The executable starts `cmd/pysentry`, which calls the GUI package. The GUI
-   opens the store, loads `pysentry.yaml` and `jobs.yaml`, creates the main tabs,
+   The executable starts `cmd/gosentry`, which calls the GUI package. The GUI
+   opens the store, loads `gosentry.yaml` and `jobs.yaml`, creates the main tabs,
    then starts the scheduler with the loaded job slice.
 
 2. Editing settings or jobs:

docs/CHANGELOG.md

@@ -1,6 +1,14 @@
 # Changelog
 
-All notable PySentry changes are recorded in this file.
+All notable GoSentry changes are recorded in this file.
+
+## 0.3.0 - 2026-06-17
+
+- Renamed the project from PySentry to GoSentry across the GUI, module path, build scripts, generated artifacts, desktop integration, and documentation.
+- Renamed the command package to `cmd/gosentry` and Windows resource script to `packaging/windows/gosentry.rc`.
+- Renamed portable application settings from `pysentry.yaml` to `gosentry.yaml`, while keeping one-time read compatibility for existing `pysentry.yaml` files.
+- Renamed build artifacts from `pysentry-*` to `gosentry-*`.
+- Updated autostart and Linux desktop integration to use GoSentry names while cleaning up older PySentry autostart entries.
 
 ## 0.2.5 - 2026-06-16
 
@@ -27,7 +35,7 @@ All notable PySentry changes are recorded in this file.
 
 ## 0.2.2 - 2026-06-15
 
-- Added Linux desktop integration that installs a user-level `.desktop` file and icon so taskbars can match the running window to the PySentry icon.
+- Added Linux desktop integration that installs a user-level `.desktop` file and icon so taskbars can match the running window to the GoSentry icon.
 - Added the installed icon path to Linux autostart desktop entries when available.
 - Added `ARCHITECTURE.md` with a component interaction diagram and moved project documentation under `docs/`.
 - Adjusted the Mermaid architecture diagram to avoid line-break syntax that breaks rendering in Gitea.

docs/ROADMAP.md

@@ -1,22 +1,6 @@
 # Roadmap
 
-This file tracks planned PySentry work that is larger than a single bug fix.
-
-## Project Rename
-
-Plan a rename from PySentry to GoSentry.
-
-Rename checklist:
-
-- Decide the final repository path and Go module path.
-- Update application name, window title, tray menu, and desktop integration text.
-- Update app ID and autostart entry names.
-- Rename build artifacts from `pysentry-*` to `gosentry-*`.
-- Decide whether runtime files should stay backward-compatible with existing
-  `pysentry.yaml`, `jobs.yaml`, and log directories or migrate to new names.
-- Update README, CHANGELOG, ROADMAP, build scripts, Docker image names, and
-  package metadata.
-- Consider a transition note for users with existing PySentry configuration.
+This file tracks planned GoSentry work that is larger than a single bug fix.
 
 ## Post-Field-Test Cleanup
 
@@ -56,7 +40,7 @@ runtime YAML files live next to the executable by default.
 
 Planned delivery variants:
 
-- Windows portable `.zip` with `pysentry.exe`, `README.md`, and `CHANGELOG.md`.
+- Windows portable `.zip` with `gosentry.exe`, `README.md`, and `CHANGELOG.md`.
 - Linux portable `.tar.gz` archives for `linux-amd64` and `linux-arm64`.
 - Debian/Ubuntu `.deb` package once the Linux runtime paths are settled.
 - Windows installer later, likely Inno Setup first and MSI/WiX only if needed.
@@ -68,8 +52,8 @@ Packaging design note:
 
 - Portable builds can keep settings and jobs next to the executable.
 - Installer/package builds should move runtime data to per-user locations:
-  `%APPDATA%\PySentry` on Windows, and XDG directories such as
-  `~/.config/pysentry` and `~/.local/share/pysentry` on Linux.
+  `%APPDATA%\GoSentry` on Windows, and XDG directories such as
+  `~/.config/gosentry` and `~/.local/share/gosentry` on Linux.
 
 Initial priority: