irisandClaude Opus 5
141402bcd2
strip.rs re-signs with this machine's ~/.android/debug.keystore on the assumption it is the key the build was signed with, and never checked. Where it isn't -- a keystore recreated after the APK was built signs as an entirely unrelated certificate -- the phone gets an APK Android refuses, reporting "App not installed" with no cause, which reads as the download rather than the signing. Both certificates are now read with `apksigner verify --print-certs`, compared as sets of digests so a v2 source and a v3 output still match, and a mismatch is refused with both digests and the keystore path in the message. The slim copy is deleted on refusal: nothing would serve it without its stamp, but serveable_now reports the size of whatever slim file is on disk. Verified both ways against tdep-survey's app-dioxus: with a fresh keystore under a throwaway HOME the download 500s with the message and leaves nothing behind, and with the real one it serves the same 52,685,076 bytes as before, signed by the same certificate as the raw build. Raised by the tdep-survey session, which measured that a fresh debug keystore is unrelated to the existing one. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>