chore: move desktop packages to packages.healthchat.ch

.claude/skills/releasing-healthchat/SKILL.md

@@ -29,8 +29,10 @@ Releases are driven by git tags of the form `healthchat-v<semver>` pushed to
   **does not publish them**. See "Deploying the desktop release" below.
 - `.github/workflows/deploy-healthchat-desktop.yaml` (desktop deploy) — **manual
   dispatch only.** Downloads that tarball and mirrors it to
-  `https://healthchat.ch/packages/desktop/` over FTPS (the private GitHub Release can
-  serve neither end users nor the auto-updater). This is what makes installed apps
+  `https://packages.healthchat.ch/desktop/` over FTPS (the private GitHub Release can
+  serve neither end users nor the auto-updater), plus the legacy
+  `https://healthchat.ch/packages/desktop/` path while clients built <= 1.5.0 are still
+  in the field. This is what makes installed apps
   self-update; see `apps/desktop/element.io/healthchat/README` for the feed layout and
   the two caveats (first install is manual; Windows auto-update needs the Setup.exe path,
   not the .msi).
@@ -185,7 +187,7 @@ run or `:latest` had not moved yet.
 ## Deploying the desktop release
 
 The desktop build attaches `healthchat-desktop-feed-<version>.tar.gz` to the Release but
-leaves `https://healthchat.ch/packages/desktop/` untouched. Until you run this, installed
+leaves `https://packages.healthchat.ch/desktop/` untouched. Until you run this, installed
 apps keep whatever version they have and the public download links still serve the old
 installers.
 
@@ -321,7 +323,7 @@ warning. Prefer fixing the changelog over relying on the fallback.
       "* Setup*.exe") **plus** `healthchat-desktop-feed-<version>.tar.gz`. Without that
       tarball the desktop deploy has nothing to publish.
 - [ ] Confirm the live feed is still on the **previous** version — releasing must not have
-      moved it. `curl -fsS https://healthchat.ch/packages/desktop/update/macos/releases.json`
+      moved it. `curl -fsS https://packages.healthchat.ch/desktop/update/macos/releases.json`
 - [ ] Smoke-check signing before shipping to users: macOS `spctl -a -vvv -t install <app>`
       is accepted; Windows installer shows a valid publisher (no SmartScreen block).
 
@@ -332,9 +334,10 @@ release"):
 
 - [ ] Web deployed and `curl -fsS https://app.healthchat.ch/version` reports the new version.
 - [ ] Desktop feed deployed: the "Deploy HealthChat Desktop" run is green. Its own verify
-      step already asserts the five feed URLs return 200, so a green run is the check.
+      step already asserts the feed URLs (canonical + legacy) return 200, so a green run is
+      the check.
 - [ ] `releases.json` now advertises the new version:
-      `curl -fsS https://healthchat.ch/packages/desktop/update/macos/releases.json | jq -r '.releases[0].updateTo.version'`
+      `curl -fsS https://packages.healthchat.ch/desktop/update/macos/releases.json | jq -r '.releases[0].updateTo.version'`
 - [ ] Spot-check auto-update on a real installed client (or at least confirm the app's
       update check reaches the feed) before announcing.
 
@@ -346,7 +349,7 @@ Configured in repo Settings → Secrets and variables → Actions:
 |---|---|
 | `HEALTHCHAT_WORKSPACE_TOKEN` | PAT with read access to `Novaloop-AG/healthchat-workspace`. Needed by `actions/checkout` for the private plugin repo. |
 | `GITHUB_TOKEN` | Auto-provided. Used for ghcr.io login and GitHub Release creation. No manual setup required. |
-| `FTP_SERVER` / `FTP_USERNAME` / `FTP_PASSWORD` | Credentials for the healthchat.ch FTP(S) account. Used **only** by `deploy-healthchat-desktop.yaml` to publish the update feed + public installers under `/public_html/healthchat.ch/packages/desktop/`. `FTP_SERVER` is the hostname only (explicit FTPS / AUTH TLS). The release workflows never touch FTP, so a missing/expired credential breaks the deploy but never the release. |
+| `FTP_SERVER` / `FTP_USERNAME` / `FTP_PASSWORD` | Credentials for the healthchat.ch FTP(S) account. Used **only** by `deploy-healthchat-desktop.yaml` to publish the update feed + public installers under `/public_html/packages/desktop/` (docroot of packages.healthchat.ch) plus, during the URL migration, the legacy `/public_html/healthchat.ch/packages/desktop/`. `FTP_SERVER` is the hostname only (explicit FTPS / AUTH TLS). The release workflows never touch FTP, so a missing/expired credential breaks the deploy but never the release. |
 
 Desktop signing additionally requires two GitHub **environments** (Settings →
 Environments). Without them the desktop builds still run but produce