@@ -72,9 +72,10 @@ The code is open source; the Shadowfetch and ShadowCode product identity is cove
   own terminal, go from commit to pull request, preview the app you're
   building, dictate with your voice, and follow along from your phone.
 
-ShadowCode **2.3.0** is available in [GitHub releases](https://github.com/ShadowfetchStudio/ShadowCode/releases/tag/v2.3.0) for x86_64 and 64-bit ARM Linux, from the signed APT repository below, for macOS (Apple silicon and Intel) and, for the first time, for Windows.
-See the [2.3.0 release notes](docs/RELEASE_NOTES.md) for changes and qualification
-limits, and the [release history](CHANGELOG.md).
+ShadowCode **2.2.0** is the current release, available in [GitHub releases](https://github.com/ShadowfetchStudio/ShadowCode/releases/tag/v2.2.0) for x86_64 and 64-bit ARM Linux, from the signed APT repository below and for macOS (Apple silicon and Intel).
+See the [2.2.0 release notes](https://github.com/ShadowfetchStudio/ShadowCode/releases/tag/v2.2.0) for changes and qualification
+limits, and the [release history](CHANGELOG.md). Windows is in development
+for the next release and is not released yet (see [Windows](#windows)).
 
 ## Install
 
@@ -91,13 +92,12 @@ file name. See
 From 2.2.0 each release also carries Flatpak bundles for both architectures
 (`ShadowCode_VERSION_x86_64.flatpak`, `ShadowCode_VERSION_aarch64.flatpak`,
 checked with `ShadowCode_VERSION_flatpak.sha256`; see [Flatpak](docs/FLATPAK.md))
-and macOS disk images (see [macOS](#macos)); from 2.3.0 a Windows installer
-too (see [Windows](#windows)).
+and macOS disk images (see [macOS](#macos)).
 Check [GitHub releases](https://github.com/ShadowfetchStudio/ShadowCode/releases)
-for published versions. The 2.3.0 x86_64 packages and checksums are:
+for published versions. The 2.2.0 x86_64 packages and checksums are:
 
-- `ShadowCode_2.3.0_amd64.AppImage`
-- `ShadowCode_2.3.0_amd64.deb`
+- `ShadowCode_2.2.0_amd64.AppImage`
+- `ShadowCode_2.2.0_amd64.deb`
 - `SHA256SUMS`, `RELEASE-MANIFEST.json`, `RELEASE-AUTH` and
   `RELEASE-AUTH.sig` (download these beside the package; the installer checks
   the publisher's signature before running anything)
@@ -131,7 +131,11 @@ cmake.
 
 ### Windows
 
-From 2.3.0, releases also carry `ShadowCode_VERSION_x64-setup.exe` for
+> **Not released yet.** Windows support is in development for the next
+> release (2.3.0). No published release includes a Windows installer yet, so
+> the steps below do not work today; they describe the planned installer.
+
+From 2.3.0, releases are planned to also carry `ShadowCode_VERSION_x64-setup.exe` for
 64-bit Windows 10 (version 1809 or later) and 11, with its SHA-256 checksum in
 `ShadowCode_VERSION_windows.sha256`. It installs for your user only (no
 administrator rights) and includes llama.cpp for local models (CPU) and the
@@ -182,7 +186,7 @@ bundle and bootstrap requirements.
 From that independently authenticated installer bundle, run:
 
 ```bash
-bash /path/to/trusted-bundle/scripts/install-appimage.sh /path/to/downloads/ShadowCode_2.3.0_amd64.AppImage
+bash /path/to/trusted-bundle/scripts/install-appimage.sh /path/to/downloads/ShadowCode_2.2.0_amd64.AppImage
 ```
 
 The installer takes the AppImage path (or `--recover`), resolves its own trusted
@@ -228,7 +232,7 @@ as `--trust-dir` are not installer options.
   cannot corrupt it.
 
 After obtaining and verifying the intended package, run the AppImage without installing it:
-`./ShadowCode_2.3.0_amd64.AppImage --appimage-extract-and-run`. FUSE is not
+`./ShadowCode_2.2.0_amd64.AppImage --appimage-extract-and-run`. FUSE is not
 required.
 
 ### Debian package
@@ -276,16 +280,16 @@ installed. The repository is published by the release workflow only; nothing
 in ShadowCode adds or contacts it by itself.
 
 To install one release by hand instead, verify the Debian artifact using the independently trusted verifier bundle.
-`verified-deb-2.3.0` must not already exist; install the verified snapshot:
+`verified-deb-2.2.0` must not already exist; install the verified snapshot:
 
 ```bash
 bash /path/to/trusted-bundle/scripts/verify-native-release.sh \
   --bundle-dir /path/to/downloads \
   --trust-dir /path/to/trusted-bundle/release/trust \
-  --artifact ShadowCode_2.3.0_amd64.deb \
-  --stage-dir ./verified-deb-2.3.0 \
-  --expect-version 2.3.0
-sudo apt install ./verified-deb-2.3.0/ShadowCode_2.3.0_amd64.deb
+  --artifact ShadowCode_2.2.0_amd64.deb \
+  --stage-dir ./verified-deb-2.2.0 \
+  --expect-version 2.2.0
+sudo apt install ./verified-deb-2.2.0/ShadowCode_2.2.0_amd64.deb
 ```
 
 A `.deb` installed by hand this way gets no updates and none of the APT
@@ -871,6 +875,10 @@ xvfb-run -a dbus-run-session -- node scripts/test-native-first-run.mjs
 - Package notices: [licenses/native](licenses/native/README.md). Packaging
   for distributions: [Distributing ShadowCode](docs/DISTRIBUTING.md).
 
+## Support the project
+
+If ShadowCode is useful to you, you can [buy me a coffee](https://www.buymeacoffee.com/shadowfetcu).
+
 ## License
 
 ShadowCode is licensed under the [Apache License 2.0](LICENSE) · Copyright
 
@@ -49,7 +49,7 @@ The Flatpak bundles are attached after publication by
 `.github/workflows/release-flatpak.yml` (from 2.2.0), with SHA-256 checksums
 in `ShadowCode_VERSION_flatpak.sha256` rather than publisher signatures; the
 macOS disk images likewise (`release-macos.yml`, `ShadowCode_VERSION_macos.sha256`),
-and from 2.3.0 the Windows installer with the complete source of its bundled
+and, once 2.3.0 is published (Windows is not released yet), the Windows installer with the complete source of its bundled
 busybox-w32 (`release-windows.yml`, `ShadowCode_VERSION_windows.sha256`).
 
 Releases before 2.1.0 have no aarch64 packages; build them from source (below)
 
@@ -16,12 +16,12 @@ Download the bundle for your computer and the checksum file from the
 release, then:
 
 ```sh
-sha256sum --check --ignore-missing ShadowCode_2.3.0_flatpak.sha256
-flatpak install --user ./ShadowCode_2.3.0_x86_64.flatpak
+sha256sum --check --ignore-missing ShadowCode_2.2.0_flatpak.sha256
+flatpak install --user ./ShadowCode_2.2.0_x86_64.flatpak
 flatpak run com.shadowfetch.shadowcode
 ```
 
-On 64-bit ARM, install `ShadowCode_2.3.0_aarch64.flatpak` instead.
+On 64-bit ARM, install `ShadowCode_2.2.0_aarch64.flatpak` instead.
 
 The bundle points to Flathub for the GNOME runtime. Installation exports the
 application launcher and icons into the desktop's Applications menu.
 
@@ -20,7 +20,7 @@ server is installed from **Settings › Accounts** (see
 | Claude Code | `claude` | [Claude Code](https://code.claude.com/docs/en/headless) | **Connect** runs `claude auth login` |
 | Cursor | `cursor-agent` | [Cursor CLI](https://cursor.com/docs/cli/acp) | **Connect** runs `cursor-agent login` |
 | Antigravity | `agy_acp_server.par` (Google's ACP agent server) | **Install** in **Settings › Accounts** downloads Google's official agent server (334 MB from dl.google.com, checked against a pinned SHA-256) | **Connect** signs in with Google in the browser |
-| Grok | `grok` | [xAI CLI](https://docs.x.ai/build) | **Connect** runs `grok login` |
+| Grok | `grok` | [xAI CLI](https://docs.x.ai/build/cli/reference) | **Connect** runs `grok login` |
 
 - **Connect** runs the login command with your environment, minus provider API
   keys. The vendor opens your browser or prints a URL or device code, and