The compatibility check fetches the published Arcade's art and games from
the node and runs the cover-library check, which serves the library art and
answers Apfelwurm's controls question; the isolated test keeps its loopback.
The device key's browser build links the crypto package's SHA-256.
This host no longer draws Habits' and Practices' screens, so a package of
theirs built for an older host interface would leave them blank. Each app
in apps/versions.json may now name the oldest host interface its packages
must be built for; Habits and Practices name 30. An older installed or
rolled-back package gives way to the bundled copy, and the compatibility
test skips the node's older releases of those two as this build does.
Ziran 0.3.1 writes portable bundles as .zx with a ZX header and rejects
.zib. Pin Ziran 620c407, Kryon 935d5fc1, Apps 12e52c0 and Entity 86e72720,
and build, embed, download, verify and store every bundle as .zx: the root
and cell bundles, node apps (the node is asked for format=zx releases),
practice packs and the shared Apps controller, now the only trusted one.
Practice packs stored by older versions count as installed and update
themselves to ZX; a node app's unusable .zib payload is removed so its ZX
release installs. Bundle staging starts empty, so no stale bundle is
embedded, and Android reads asset names by their length.
The generated app codec matches the pinned generator again.
A pushed version that is already released no longer starts the forty-minute release builds; CI still tests every push. A package version waiting for the next release is a notice in App packages instead of a failure. The web build keeps saving its storage while practice packs install (up to about ten seconds of retries), and the package compatibility check asks the node again while a deploy restarts it. The pre-push hook now runs the quick checks that match the pushed files (versions, translations and fonts, UI APIs, app bundles, workflows, script syntax); make pre-push-check runs them by hand.
Xvfb resets when its last client disconnects. An app started during that
reset lost its display and kept running without a window, so UI tests
waited for a window that never came. Every test display now uses -noreset.
Anonymous GitHub API calls share 60 an hour per address, and CI runners
ran out (a 403 in the package compatibility test). The test now sends
GITHUB_TOKEN or GH_TOKEN with api.github.com requests only, never with
release downloads, which redirect to signed storage URLs; the workflows
that run it pass their token. The site's release asset check sends it too
when it has to fall back to curl.
make package-compat-test runs every package the Waozi node serves in this
build, and unpacks the last released Linux app to run each new package that
declares an interface it has. A failed host call inside a package fails the
check, since the screen would otherwise silently lose that part. The Release
test job runs both directions, and the package workflow runs new packages in
the last release before publishing them.
make phone-check APK=... installs the exact APK on the development Moto,
starts the Wim Hof session through the app's start-practice intent, reads
SurfaceFlinger's frame times for a minute, checks resuming from the
background and records releases/phone-checks/VERSION.json for the commit it
checked. The Release workflow creates a new version tag only with a passing
receipt whose sources match the release, so a laggy build cannot publish.