release 1.3.2: update from Gitea, Linux-only CLI, desktop app for Linux and Windows

The updater reads latest.json from Gitea, built by scripts/make-latest-json.py
against the Gitea API (no gh CLI). Release workflow builds the Linux CLI and
the Linux+Windows desktop app, signs the updater artifacts and attaches
everything to the release.

Needs the repo secrets TAURI_SIGNING_PRIVATE_KEY and
TAURI_SIGNING_PRIVATE_KEY_PASSWORD, which I could not set (secret-store writes
are reserved for the user) - set them from ~/.tauri/guara-updater.key and
.pass before pushing a tag.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

CHANGELOG.md

@@ -4,6 +4,23 @@
 
 Format based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow SemVer.
 
+## [1.3.2] - 2026-10-30
+
+The project moved from GitHub to Gitea, and the update check followed it.
+
+### Changed
+- **Updates now come from Gitea.** The desktop app's update card reads
+  `latest.json` from `git.lucasrguerra.dev.br` instead of GitHub Releases.
+  Versions up to 1.3.1 still look at GitHub, which is no longer reachable, so
+  they cannot find this release: download 1.3.2 once, and later updates are
+  automatic.
+- The CLI is published for Linux x86_64 and aarch64 only, built by the Gitea CI
+  when a `v*` tag is pushed, with a `.sha256` next to each package. **There is
+  no Windows CLI any more.** The desktop app still ships for Linux (AppImage,
+  `.deb`) and Windows (NSIS `.exe`, cross-compiled from Linux). There is no
+  macOS build: it needs Apple's SDK and code signing, which this project's CI
+  (one Linux runner) cannot provide.
+
 ## [1.3.1] - 2026-10-23
 
 ### Changed