0.0.27 was published TWICE with different trees — once from the branch and once from a tag pushed to give the APK a readable name. The registry kept the second; the handset held the first. Both said "0.0.27". The banner was honest and unfixable at the same time: staged != running, so it offered an update, and applying it changed no version string because both trees carry the same one. A banner that cannot be cleared by doing what it asks is worse than no banner. ⚠ Branch push only. Pushing a tag as well is what produced two builds of one version; the forge names a branch release by commit, which is uglier and true. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>