max / goingson

Make the Android build work, and give it a trust store The android tree was a husk: initialized once on mbp at 0.3.0, ignored wholesale, and missing its manifest and gradle files by the time anything looked again. It is regenerated at 0.5.0 and now tracked, because it stopped being purely generated the moment MainActivity called into our own code. The build failed in lettre, and the cause was worth more than the fix. lettre gates its Verifier::new_with_extra_roots call on the cargo feature alone, but rustls-platform-verifier only defines that constructor for apple, windows and others -- never android, where the verifier reaches the system store over JNI and extra roots have nowhere to go. So SMTP takes webpki-roots on android and the platform verifier everywhere else. HTTP and IMAP still honour CAs installed on the device; SMTP does not, which will look like a self-hosted server that fetches but refuses to send. Pulling that thread found two verifiers in the graph. The workspace asked for 0.6 while reqwest and lettre both pulled 0.7, and each version carries its own process-global init state, so one of them was always going to go uninitialized. Unified on 0.7, which is what the "one rustls stack" comment above it had been claiming all along. That crate needs the JVM handed to it before the first handshake and expects it rather than falling back, so an uninitialized verifier is not a degraded trust path, it is a panic on first network use. MainActivity now passes the application context to android_tls.rs before super.onCreate(), since Tauri starts the app inside that call and sync can beat it to the network. The Kotlin half ships inside the rustls-platform-verifier-android crate rather than on Maven Central, so gradle asks cargo where it landed and the version follows Cargo.lock. Verified: the JNI symbol is exported from the .so and CertificateVerifier is in the merged dex, so neither half was silently dropped.