PrivCloud Companion beta artifacts
Desktop Companion version: 0.1.4
Android app version: 0.2.9 (21)
Android Companion version: 0.1.5 (6)
PQ Vault version: 2.1.5 (7)

These artifacts are beta builds generated from the private SaaS repository.
They are not signed, not notarized, and not published in browser or mail stores.

Production release requirements:
- Linux: sign .deb/.rpm/AppImage artifacts and publish checksums.
- Windows: build and sign an MSI with Authenticode.
- macOS: build, sign, and notarize a pkg/app with Apple Developer ID.
- Browser/mail stores: submit Chrome, Firefox, Thunderbird, Microsoft 365 and Google Workspace packages for review.
- Android: replace the debug-signed app APK with a release build signed by an upload key, and publish it through Play.

Android artifacts:
- privcloud-android-app-*-beta-debug.apk is the full native client.
- privcloud-android-companion-*-beta-debug.apk is the local WebDAV/Nextcloud connector, a different and much smaller tool.
Both are debug-signed, so Android will warn about an unknown app and Play Protect may ask for confirmation.
Signing in to the native app and activating WebDAV/Companion require a Pro plan
or an active Team membership. Companion uses a short-lived SaaS entitlement;
installing the binary alone does not unlock the integration.

PQ Vault artifacts:
- pq-vault-android-*-arm64-v8a-beta-debug.apk targets current physical Android devices.
- pq-vault-android-*-x86_64-beta-debug.apk targets x86_64 emulators and compatible devices.
PQ Vault is a separate Android passkey manager. It stores passkeys in an encrypted,
self-hosted WebDAV vault and does not manage passwords. These APKs are debug-signed;
verify checksums.sha256 before sideloading them.

Runtime note:
The current beta Companion is a dependency-free Node.js script. The target
machine must provide Node.js 20 or newer until signed desktop bundles embed a
runtime. NVM runtimes are supported: run without sudo in your NVM shell:
  /usr/bin/privcloud-companion --configure-runtime "$(command -v node)"
Then register the browser's exact extension ID, without sudo:
  PRIVCLOUD_CHROME_EXTENSION_ID=YOUR_32_LETTER_EXTENSION_ID     sh /usr/share/privcloud-companion/register-native-messaging.sh
For portable archives, use ./privcloud-companion --configure-runtime instead.
The validated runtime path is stored per user; rerun configuration after removing
that NVM version. Chromium Flatpak registration uses its own profile directory
and the existing filesystem permissions, without granting host execution access.
