chore: move desktop packages to packages.healthchat.ch

apps/desktop/element.io/healthchat/README

@@ -98,14 +98,14 @@ runs can reach the signing credentials.
 
 Auto-update + public installer hosting
 --------------------------------------
-The apps self-update over a feed hosted on healthchat.ch (the GitHub Release is private to this
-internal fork, so it can serve neither end users nor the Squirrel auto-updater). Both the update
-feed and the public installers live under https://healthchat.ch/packages/desktop/ (FTP web root
-/public_html/healthchat.ch maps to https://healthchat.ch/; no packages. subdomain, so it's a path):
+The apps self-update over a feed hosted on packages.healthchat.ch (the GitHub Release is private
+to this internal fork, so it can serve neither end users nor the Squirrel auto-updater). Both the
+update feed and the public installers live under https://packages.healthchat.ch/desktop/ (the
+subdomain's docroot on the healthchat.ch FTP account is /public_html/packages):
 
   update/   the Squirrel feed the installed apps poll hourly. config.json sets
-              "update_base_url": "https://healthchat.ch/packages/desktop/update/"
-            and the macos job passes base-url: https://healthchat.ch/packages/desktop so the
+              "update_base_url": "https://packages.healthchat.ch/desktop/update/"
+            and the macos job passes base-url: https://packages.healthchat.ch/desktop so the
             generated releases.json points the *-mac.zip at this origin.
               update/macos/releases.json + HealthChat-<ver>-mac.zip   (Squirrel.Mac)
               update/win32/<arch>/RELEASES + HealthChat-<ver>-full.nupkg   (Squirrel.Windows; x64 + arm64)
@@ -113,14 +113,20 @@ feed and the public installers live under https://healthchat.ch/packages/desktop
               install/macos/HealthChat-<ver>.dmg + HealthChat.dmg (stable "latest")
               install/win32/<arch>/HealthChat-Setup-<ver>.exe + HealthChat-Setup.exe (stable) + *.msi
 
-The `release` job in build-healthchat-desktop.yaml stages these trees and uploads them via lftp/FTPS
-(mirror -R, no-delete so prior nupkgs survive for delta history). Add these repo secrets:
+The `release` job in build-healthchat-desktop.yaml stages these trees; the manually dispatched
+deploy-healthchat-desktop.yaml uploads them via lftp/FTPS (mirror -R, no-delete so prior nupkgs
+survive for delta history). Add these repo secrets:
   FTP_SERVER     hostname only (explicit FTPS / AUTH TLS on port 21; if the host cert is untrusted,
                  flip ssl:verify-certificate to no in the workflow)
   FTP_USERNAME
   FTP_PASSWORD
 
 Caveats:
+  - URL migration: builds <= 1.5.0 poll the legacy feed at
+    https://healthchat.ch/packages/desktop/ (docroot /public_html/healthchat.ch/packages/) —
+    they only learn the new URL by installing an update delivered over that old feed. The
+    deploy workflow therefore dual-publishes to both directories; drop the legacy mirror and
+    its verify checks once the installed base is on a build carrying the new update_base_url.
   - First install is manual. Apps already installed without update_base_url (<= 1.1.2) cannot
     self-update to the first build that carries it; users must download once from the install/ URL.
     Every release after that updates automatically.

apps/desktop/element.io/healthchat/config.json

@@ -88,7 +88,7 @@
         ]
     },
     "show_labs_settings": false,
-    "update_base_url": "https://healthchat.ch/packages/desktop/update/",
+    "update_base_url": "https://packages.healthchat.ch/desktop/update/",
     "modules": ["/modules/healthchat-module.js"],
     "ch.healthchat": { "api_base_url": "https://api.healthchat.ch", "elements_base_url": "/webapp/modules/elements" }
 }