32. Packaging, Distribution, and Updates

Official artifact names follow glitchpad-{version}-{platform}-{arch}.{ext} and contain or accompany LICENSE, NOTICE, THIRD_PARTY_NOTICES, SHA-256 checksums, CycloneDX SBOM, and provenance attestation.

Windows publishes an unsigned x86_64 NSIS current-user installer and portable ZIP. macOS publishes one universal DMG containing an ad-hoc-signed application without Apple notarization. Linux publishes an x86_64 AppImage and Debian package built against the declared glibc baseline. Android publishes a universal APK, a split ARM64 APK, and an AAB signed by the stable project-owned update key.

Desktop packages register only stable editable/viewable formats from the release matrix. Android intent filters follow the same rule. Uninstall removes application binaries and registered associations while preserving user-created documents; platform conventions decide whether preferences and recovery data remain, and the uninstaller must disclose any removal option.

v0.1.4 has no in-app updater. Direct-distribution users obtain community releases through the project release channel. A future updater requires a separate threat model, authenticated manifest, rollback policy, channel model, proxy/offline behavior, and recovery test matrix.

No artifact is official without its declared trust state, checksum, SBOM, provenance, license notices, source revision, and exact version evidence. Windows is explicitly unsigned, macOS is ad-hoc signed and non-notarized, Linux is repository-attested, and Android uses the stable project-owned update key. Manual validation tracked by issue #66 continues after v0.1.4 publication.