[sayed0am]

What it does

• Daily check. Once a day, with a network, OpenStrap reads its release list from GitHub (an anonymous GET to api.github.com, only the app version in the user agent) and notifies once per new release. The notification shows the release's opening paragraph and opens the Updates page. The check is on by default, with a switch on the Updates page, and that switch is backed up.
• In-app install. Downloads the release APK, checks it against GitHub's SHA-256 digest (or SHA256SUMS.txt), and checks that it's OpenStrap signed with the installed copy's key. Then it hands it to Android's package installer. The first time, Android asks to allow "Install unknown apps". It never installs while a workout records. Afterwards it says "Updated to OpenStrap X", and the strap reconnects without opening the app (MY_PACKAGE_REPLACED).
• Changelog. The new Updates page (You → Updates) shows the notes of every release newer than the installed one, newest first, or this version's own when it's up to date. It reads both the hand-written notes and GitHub's generated ones.
• Docs. docs/privacy.md, the README and the manifest comment describe the new request and the install permission.

Testing

• All 1016 unit tests pass, 13 of them new (ReleasesTest, ReleaseNotesTest, UpdateCopyTest).
• Checked on the Fold's cover screen: the You row, the Updates page up to date and with an update (a build labelled 2.0.0), the notification and its tap, and Install opening the "Install unknown apps" screen.
• Not yet tested: the download and the package installer step. A debug build can't install a release over itself because the keys differ, so it shows the signed-with-another-key message. A real install needs one release build updating to a newer one.

🤖 Generated with Claude Code