# Change: Add commercial desktop packaging flow

## Why
TrueGrowth desktop already runs in development, but customer delivery needs a repeatable commercial packaging flow for macOS and Windows. Customers should receive a branded installer/app bundle that starts the renderer and Local API without developer setup, while heavy local AI dependencies are either bundled/managed or initialized through Model Center.

## What Changes
- Add a production Electron packaging pipeline for macOS and Windows installers with TrueGrowth branding, icons, app identifiers, packaged renderer assets, and local preload/main assets.
- Add release scripts that build the web renderer, stage Electron runtime files, generate package metadata, and invoke the desktop packager per target platform.
- Keep Local API and product-critical desktop services bundled with the app; route optional heavyweight runtimes, model downloads, and environment setup through Model Center readiness actions.
- Document the internal build process, customer installation expectations, runtime directory behavior, and code-signing/notarization requirements.
- Add verification steps for packaged startup, Local API health, Model Center runtime guidance, and macOS/Windows artifact presence.

## Impact
- Affected specs:
  - `desktop-packaging`
  - `desktop-runtime-readiness`
- Affected code:
  - `package.json`
  - `apps/electron/`
  - `scripts/`
  - `docs/`
  - packaging config such as Electron Builder metadata

## Notes
- macOS artifacts can be built on macOS. Windows commercial installers should be built on Windows or CI; cross-building from macOS is not a reliable signing-ready release path.
- This change does not bundle large AI model files by default. Model Center remains the customer-facing path for downloading or connecting heavyweight local models and runtimes.