## ADDED Requirements

### Requirement: Desktop Auto Update Channel
The desktop application SHALL use `https://truegrowth.benchu.cloud/desktop/stable/` as the default stable auto-update channel.

#### Scenario: Packaged client checks for updates
- **GIVEN** a packaged installed desktop client
- **WHEN** the scheduled or manual update check runs
- **THEN** the client SHALL query the generic update metadata from the stable channel.

### Requirement: Desktop Update UI
The desktop application SHALL expose update status in the lower-left navigation utility area and provide a branded dialog for update actions.

#### Scenario: Update is available
- **WHEN** the updater reports a new version
- **THEN** the UI SHALL show the version, release notes when available, and a download action.

#### Scenario: Update is downloaded
- **WHEN** the updater finishes downloading an update
- **THEN** the UI SHALL offer restart-to-install without forcing restart automatically.

### Requirement: Release Artifact Manifest
The release tooling SHALL produce a `releases.json` manifest alongside electron-builder update metadata for the 1Panel static directory.

#### Scenario: Release artifacts are prepared
- **WHEN** desktop release artifacts exist in the release output directory
- **THEN** the tooling SHALL record version, channel URL, files, sizes, sha256 hashes, and upload guidance.

### Requirement: Production Signing Gate
Production auto-update releases SHALL require platform signing before customer distribution.

#### Scenario: Unsigned production package
- **WHEN** a production customer release is prepared without required platform signing
- **THEN** the release SHALL be treated as not ready for customer auto-update distribution.