chore: migrate release pipeline to signed filemap and wire rainyun s3

.trae/specs/pdc-incremental-migration/checklist.md

@@ -0,0 +1,10 @@
+# Checklist
+
+- [x] `release.yml` produces signed FileMap incremental assets for Windows x64/x86 and Linux x64.
+- [x] `release.yml` no longer depends on `vpk`/VeloPack packaging.
+- [x] Launcher update engine applies only signed FileMap payload path.
+- [x] Host update workflow no longer expects `releases.win.json`/`*.nupkg`.
+- [x] Update source setting includes `pdc` and preserves GitHub fallback behavior.
+- [ ] CI run attached proving all release matrix jobs pass.
+- [ ] N-1 -> N incremental update verified on Windows x64/x86 and Linux x64.
+- [ ] Rollback verification report attached.

.trae/specs/pdc-incremental-migration/spec.md

@@ -0,0 +1,30 @@
+# PDC Incremental Update Migration
+
+## Goal
+
+Replace VeloPack-based incremental packaging with a unified signed FileMap pipeline and prepare for PDC/S3 distribution compatibility, while keeping Launcher installation, rollback, and update orchestration ownership unchanged.
+
+## Stage 1 (Completed in this round)
+
+- Release workflow outputs signed FileMap incremental assets as the primary path:
+  - `files-windows-x64.json` / `.sig` / `update-windows-x64.zip`
+  - `files-windows-x86.json` / `.sig` / `update-windows-x86.zip`
+  - `files-linux-x64.json` / `.sig` / `update-linux-x64.zip`
+- Launcher and host update runtime remove VeloPack branches and return to signed FileMap apply path.
+- Host update asset discovery supports platform-scoped names with fallback to legacy generic names.
+- Optional S3 sync publishes incremental assets in parallel with GitHub Release assets.
+
+## Stage 2 (In Progress)
+
+- Introduce PDC-compatible update source (`pdc`) with fallback to GitHub.
+- Add PDC metadata/latest/distribution API consumption abstraction.
+- Keep Launcher install/apply/rollback state machine unchanged.
+- Prepare `phainon.yml`-compatible release metadata for future PDCC integration.
+
+## Acceptance
+
+- `release.yml` no longer contains VeloPack packaging steps.
+- Windows x64/x86 and Linux x64 release jobs all upload signed FileMap incremental assets.
+- Host auto-update can detect and download platform-matching signed FileMap assets.
+- Launcher `update apply` succeeds with signed FileMap payload and rollback behavior remains unchanged.
+- Optional S3 upload step works when S3 secrets/vars are configured.

.trae/specs/pdc-incremental-migration/tasks.md

@@ -0,0 +1,12 @@
+# Tasks
+
+- [x] Remove VeloPack packaging from release workflow.
+- [x] Promote signed FileMap generation to release primary path.
+- [x] Output platform-scoped incremental assets for Windows x64/x86 and Linux x64.
+- [x] Remove launcher/runtime VeloPack branches.
+- [x] Update host asset discovery to platform-scoped signed FileMap naming.
+- [x] Add optional S3 sync for incremental assets.
+- [x] Extend update source values with `pdc`.
+- [x] Add PDC check fallback service skeleton in settings domain.
+- [ ] Add full PDC FileMap object-hash download/deploy path.
+- [ ] Add PDCC publish integration and `phainon.yml` CI publishing flow.

.trae/specs/velopack-update-integration/checklist.md

@@ -1,7 +1,5 @@
-# Checklist
+# Checklist (Deprecated)
 
-- [x] `releases.win.json` recognized by host update download flow.
-- [x] Launcher pending update check supports VeloPack payload.
-- [x] Launcher apply uses deployment markers (`.current/.partial/.destroy`) unchanged.
-- [x] Legacy script path retained as emergency fallback.
-- [ ] Staging verification report attached.
+- [x] Spec marked as deprecated.
+- [x] Active implementation ownership moved to `pdc-incremental-migration`.
+- [x] No release workflow dependency remains on VeloPack.

.trae/specs/velopack-update-integration/spec.md

@@ -1,16 +1,15 @@
-# VeloPack Update Integration
+# VeloPack Update Integration (Deprecated)
 
-## Goal
-Switch incremental package generation and release assets to VeloPack native outputs while keeping Launcher as the update installer and rollback authority.
+## Status
 
-## Requirements
-- CI/release pipeline produces `releases.win.json` and `*.nupkg` assets for Windows x64.
-- Launcher can detect pending VeloPack payload in `.launcher/update/incoming`.
-- Launcher applies update into new `app-*` deployment and preserves rollback snapshot behavior.
-- Existing launcher responsibilities (OOBE/startup/plugin upgrade) remain unchanged.
+This spec is deprecated and superseded by `.trae/specs/pdc-incremental-migration/`.
 
-## Acceptance
-- Build and quality workflows pass after migration changes.
-- Release workflow publishes VeloPack assets.
-- Launcher `update apply` succeeds with VeloPack full package payload.
-- Manual rollback still works after a VeloPack-based update.
+## Deprecation Reason
+
+- VeloPack native package generation introduced unstable release blocking (version format coupling and platform divergence).
+- The project has switched back to signed FileMap incremental assets as the primary update path.
+- Launcher remains the update installer/rollback authority; packaging and distribution are being migrated to PDC/S3-compatible flows.
+
+## Migration Note
+
+Use `.trae/specs/pdc-incremental-migration/spec.md` as the active authority for incremental update implementation and acceptance.

.trae/specs/velopack-update-integration/tasks.md

@@ -1,9 +1,6 @@
-# Tasks
+# Tasks (Deprecated)
 
-- [x] Fix Launcher `LoadingDetailsWindow.axaml` compile regression.
-- [x] Add VeloPack feed/package model support in Launcher update engine.
-- [x] Keep legacy delta flow behind disabled fallback switch.
-- [x] Migrate release workflow packaging assets to VeloPack outputs.
-- [x] Update host-side update workflow to download VeloPack payload files.
-- [ ] Run full release workflow dry-run on GitHub and validate artifacts.
-- [ ] Validate end-to-end update + rollback on a staging machine.
+- [x] Mark VeloPack integration spec as deprecated.
+- [x] Remove VeloPack runtime branches from launcher/host update path.
+- [x] Remove VeloPack release workflow packaging steps.
+- [ ] Keep archive for historical context only (no new implementation tasks here).