Keep generated C between runs: zi2c --prune-stale removes outputs this run
no longer writes, now including subdirectories, and unchanged files keep
their timestamps, so an edit recompiles only the C it changed instead of
all 858 generated files.
Custom RELEASE_READY_OUTPUT names now map to build/release-ready, and
only build/release-ready-phone keeps a separate purpose, so task and
version names no longer leave a new folder per run. Both share
build/release-ready/home under an exclusive cache lease held through
container exit. The release command uses the same mapping. Phone
installs take a lock, select only an APK this run built and reuse the
default signed path. Nothing prunes existing output.
The site deploy builds https://breeze.waozi.xyz/apt from the published release's .deb files, signed with the APT_SIGNING_KEY secret and checked against the committed keyring. install-apt.html explains setup and the Linux card links to it.
A run without RELEASE_READY_INCREMENTAL rebuilds outputs from fresh times;
dropping the record keeps a later incremental run from trusting them against
times recorded for another commit.
Generated tracked files such as src/apps/app_codec.zi are rewritten with the
same content during a build. Recording their final times after a pass keeps
the next no-change phone install from rebuilding the app packages and
reconfiguring CMake.
phone-install's container now keeps the times of files the commit did not
change and the Gradle and CMake build directories between runs, and the
Android source generator keeps the times of C files it emits unchanged, so
a small change no longer recompiles the whole app.
The breath and bell cues are Practices assets. Startup loaded them
while Practices was still opening, so the lookup failed once and the
cues stayed silent. Cues now load when first played and retry after
the asset generation changes.
Background sync kept failing with result 6 because a paged download
resumed from a cursor older than since_server_version, which Daochi
rejects with 400. daochi-client now restarts such a page.
Each pose shows a one-line form cue, the lunges name the leg that is back,
and a small held figure previews the next pose. A fresh session settles in
for three breaths before the first round and rests for two after the last,
with the narration's intro and closing lines. The first round never breathes
faster than 6 s, so every spoken line plays in full.
Breeze reads the account's picture from its node through Entity's shared
reader, on connecting and every ten minutes, and takes it with Entity's
rule: a picture chosen here that the node has not accepted yet stays. The
taken picture is saved as already published, so it is not sent back.
Entity is pinned at the reader; the lock also follows Kryon master.
Low lunge (right/left by round), knees-chest-chin, cobra and step-forward lines, plus settle-in and closing lines for the guided screen (SunSalutationIntroVoiceKey, SunSalutationClosingVoiceKey). Recorded in 12 languages for both voices; tests check every breath's key, the lunge side against the rig, and that each line is recorded and fits a 6 s breath.
An audio-only pack install now reports new assets without invalidating
the practice image folder, and the kryon lock moves to the release that
keeps images drawn while they are revalidated.
Breeze's own publisher sent the default picture even when nothing was
chosen, and its friend mapping dropped Entity's abstract pictures. Friend
rows, requests and Lists now draw icons through Entity, and a picture
chosen in Breeze goes to the node through Entity's one publisher.
Add the bounded entity.achievements service to the package bridge. It
takes metric, source and amount (1..1000), derives the app from the
verified node identity, accepts only <package id>.<name> metrics and
records the fact for today.
Installed package leaves that are not legacy Inbe apps are now captured
under their expected_id asset folder and canonical id, so their
achievements.json registers, evaluates and shows the usual toast. The
saved leaves format moves to 2 so older caches rescan once.
Only the -gplay edition may read a Google library. The google-services
plugin's classpath moves from the root plugins block into
droid/app/gplay-classpath.gradle and its application into
droid/app/gplay.gradle, both applied only in a Gradle run whose tasks name
gplay. Such a run refuses release or debug tasks beside it, so the Makefile
and the release workflow build the normal and gplay APKs in separate runs,
and the normal and F-Droid builds never resolve the plugin. The Moto check
builds only the normal APK and no longer writes the Firebase config.
CI checks the Gradle files with Kryon's google-free action, the release
workflow checks the normal, per-ABI and -fdroid APKs and finds Play
Billing in the -gplay APK, and the F-Droid workflow checks F-Droid's own APK.
The estimate left photos in Trash out by reading their trashed field, which made sync-record-fields-test ask every device to download its records again. The node reports the account's real usage in each sync, so the estimate keeps counting every photo.