docs(release): the documents name 1.2.0 as the release that moves updates to git.kof22.com

There is no release numbered 1.1.1: the fixes planned for it and Gitea
support go out together as 1.2.0 (owner's decision, #200). The README, the
CLI guide, ADR 0009, the header of the threat model and a comment in
Directory.Build.props still named 1.1.1.

docs/RELEASING.md is left to the work on the release pipeline (#197).

Closes #218

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Signed-off-by: James Maes <james@kof22.com>

Directory.Build.props

@@ -53,8 +53,8 @@
        built-in SourceLink appends the git commit as "+<sha>" build metadata on
        AssemblyInformationalVersion, which the About dialog and the CLI's
        version output surface as the short hash. Prefix tracks the next expected
-       release: 1.2.0, the version that brings Gitea support (1.1.1 is cut from
-       the line before it). -->
+       release: 1.2.0, which carries the fixes that were planned as 1.1.1 and
+       Gitea support together (there is no release numbered 1.1.1). -->
   <PropertyGroup>
     <VersionPrefix>1.2.0</VersionPrefix>
     <VersionSuffix>dev</VersionSuffix>

README.md

@@ -121,7 +121,7 @@ On launch, gclo shows a brief branded splash and then opens where you left off:
 
 **Share:** Help > Share gclo by email… opens a new message in your email program with an invitation already written: what gclo is, where to download the latest release, and how to install it. Type an address and send; gclo itself sends nothing. If no email program is set up, the text is shown and copied to the clipboard, to paste into a message by hand.
 
-**Updates:** Help > Check for updates… downloads and applies the latest release for your channel from the project's releases on git.kof22.com. Versions up to 1.1.0 look for updates on GitHub; if they do not find 1.1.1 there, install it once by hand, and it updates itself from then on. Self-update is only available in installed builds (not the portable zip or a local debug build).
+**Updates:** Help > Check for updates… downloads and applies the latest release for your channel from the project's releases on git.kof22.com. Versions up to 1.1.0 look for updates on GitHub; if they do not find 1.2.0 there, install it once by hand, and it updates itself from then on. Self-update is only available in installed builds (not the portable zip or a local debug build).
 
 ### Saved accounts
 

docs/CLI.md

@@ -537,7 +537,7 @@ its offset from UTC (`2026-11-10 14:03:22.123 -06:00 [INFO] ...`). Text that cam
 
 Codes 3 and 4 were part of code 2 before version 1.1; a script that tested
 `-eq 2` for "usage error" should treat `3` and `4` as distinct outcomes.
-Before version 1.1.1, a refusal of access other than an invisible organization
+Before version 1.2, a refusal of access other than an invisible organization
 (403), a rate limit answered with 429, a network failure, a timeout, and an
 error on GitHub's side ended with code 70; they now end with `3` (the refusal)
 or `4` (the rest).
@@ -653,7 +653,7 @@ done
 
 ```console
 $ gclo --version
-1.1.1 (a893741d2)
+1.2.0 (a893741d2)
 ```
 
 Released builds print the semantic version and the short commit hash; local builds print the next-release version with a `-dev` suffix (e.g. `1.1.2-dev (<hash>)`).

docs/adr/0009-updates-and-downloads-from-gitea.md

@@ -29,7 +29,8 @@ would install an old version for ever.
 
 - Versions up to 1.1.0 look for updates on GitHub. They find a later version only
   if it is also published there; otherwise they are updated once by hand. From
-  1.1.1 on the app looks on `git.kof22.com`.
+  1.2.0 on the app looks on `git.kof22.com` (the change was made for a 1.1.1
+  that was not released on its own; it ships in 1.2.0).
 - The availability and the integrity of updates now rest on a self-hosted server
   instead of GitHub's release hosting. The updater verifies a package against the
   hash in the feed, and the feed comes from the same server; it checks no signature

docs/security/threat-model.md

@@ -4,7 +4,7 @@
      review it in every MINOR/MAJOR release checklist (K22-SEC-30).
      Method: data-flow diagram + STRIDE per trust boundary. -->
 
-- **Version reviewed:** v1.1.1 · **Last reviewed:** 2026-11-10
+- **Version reviewed:** v1.2.0 (in work; the rows dated 2026-11-10 were written for a 1.1.1 that ships as part of 1.2.0) · **Last reviewed:** 2026-11-11
 
 ## 1. What the product is and does