Name the organisation the repository actually lives in

It moved to DodoTech-Public, and every address in the product still said
DodoTech. That looked like it worked, which is the part worth writing down:
Gitea leaves a 301 at the old path and HttpClient follows a redirect on a GET, so
both update channels would have kept polling through it.

What a 301 does not survive is a POST. `vpk upload gitea` publishes the desktop
release by POSTing to that URL, so the stale address would have failed at the one
step the whole feature depends on — and a redirect is a thing an operator can
delete, which turns "works today" into the same silent outage this session has
already spent two commits on.

So both channel constants, both release scripts, the workflow's REPO, the image's
source label and the curl in phase 16 all name the live path. The local remote
too, which had been printing a redirect warning on every push.

Measured after the move: the org, the repo and the nightly release all answer 200
anonymously, and that release now carries both assets — the manifest and a 54 MB
APK. The upload going through also answers the open question about the reverse
proxy's body-size limit, which nothing local could test.

src/DodoSSH.Client.Android/Platform/AndroidUpdateChannel.cs

@@ -76,7 +76,14 @@ internal sealed partial class ForgeJsonContext : JsonSerializerContext;
 internal sealed class AndroidUpdateChannel : IUpdateChannel
 {
     /// <summary>The project's own forge, and the one address in this file.</summary>
-    private const string RepositoryApi = "https://git.dodotech.cloud/api/v1/repos/DodoTech/DodoSSH";
+    /// <remarks>
+    /// ◆ The owner is <c>DodoTech-Public</c> and that half of the path matters. The repository was moved
+    /// between organisations, and Gitea leaves a 301 at the old one — so a client still naming it looks
+    /// fine, because <c>HttpClient</c> follows a redirect on a GET. What it buys is a dependency on a
+    /// redirect somebody can delete, and it does not extend to the release scripts, whose uploads are
+    /// POSTs. The live path is named here, in <c>VelopackUpdateChannel</c> and in both scripts.
+    /// </remarks>
+    private const string RepositoryApi = "https://git.dodotech.cloud/api/v1/repos/DodoTech-Public/DodoSSH";
 
     /// <summary>
     /// The session name the installer writes under, and it is reused rather than made unique.