Last week a release needed a commit for every phone check and CI repair:
the release commit came first, then fixes, then "Record" commits, and CI
went red after phone checks because it only ran on GitHub.
make release-ready runs CI's checks before pushing: in the Test job's
Ubuntu 24.04 with its apt packages (.github/local-ci/Containerfile), on
HEAD's committed content with the locked packages, through an overlay of
this checkout so nothing reaches the working tree. It covers Secret Scan,
package URLs, the large-file guard, make test, make visual-test and make
package-compat-test, and records a stamp for that content.
make release then, with the development Moto connected, refuses
uncommitted app files and package overrides that are not clean on the
lock, syncs ./update_version.sh output, requires the release-ready stamp
for this content, builds the debug APK for the phone's ABI, runs the phone
check and makes the one "Release Inner Breeze X.Y.Z" commit with the
receipt. After a late fix, running it again moves the unpushed release
commit above the fix (commits are replayed with merge-tree; only refs
move) instead of adding another. It never pushes or tags.