* fix(ci): a test build's files outlive the catalog that names them, and a merged PR's build lasts until Preview carries it
- A new push's PR release keeps the previous push's files until the catalog names the new
ones, then five minutes more, so a download started from the old catalog still finds its APK.
The app also reloads the catalog and retries once when a test build's download fails.
- Closing a PR without merging still deletes its test build. A merged PR's build stays, and
stays listed, until the newest Preview build was built from a main holding the merge, or
three days pass (docs-only merges build no Preview). Main's build, the PR cleanup and the
sweep share one script for this.
* fix(ci): name the current push's APK in the catalog and prune nothing it still names
* fix(ci): only a Preview with every APK carries a merge or is offered
* fix(ci): publish no preview while none has every APK
* test(ci): build_catalog publishes no preview while its APKs are uploading
* perf: download hand tracking models and native libs on first use
* feat: build and publish add-on packs in CI, add Xbox and Comet packs
* feat: ship proot and DirectAudio drivers as CI-built packs
* test: hand tracking readiness requires the tracking pack
* ci: attach PR test-build packs to the PR release instead of Components
DROIDDECK_CI_TOKEN never existed, so PR Release Publish skipped its
upload, and a personal token would expire and belong to one person. Both
workflows now mint a token of the org's DroidDeck CI Publisher app,
installed on DroidDeck-CI only with Contents: write (its ID in the
DROIDDECK_CI_APP_ID variable, its key in DROIDDECK_CI_APP_KEY). No
fallback: a main build without them fails its announce job.
After a pull request's Build APK run succeeds, its APK is published as the
pr-<number> prerelease in Droid-Deck/DroidDeck-CI, named
DroidDeck-PR.<number>-<commit>.apk, with release notes taken from the pull
request. New commits to the same pull request replace its APK. Pull requests
from forks are resolved by head owner, branch and commit.
A pull request's build is signed only with the committed testkey, so every CI
build installs over the last; the publish checks the certificate against it
and refuses anything else.
Needs a DROIDDECK_CI_TOKEN secret: a fine-grained token with Contents
read/write on Droid-Deck/DroidDeck-CI. Without it the run skips with a warning.