a5c3188686
cargo-apk panics with "Bin is not compatible with Cdylib" after successfully signing the APK, when cargo-subcommand's artifact iterator walks the bin target after the cdylib has been produced. The APK file survives the panic on disk, but the non-zero exit fails the workflow step before the upload runs. Passing --lib scopes the build to the cdylib target only. SESSION_HANDOFF.md documented this as the canonical workaround. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>