attested_secure_keys_android

The v0.1.1 tag failed to publish anything. Only the app-facing package was
bumped, which broke both workflows: CI's version-lockstep gate rejected the
0.1.0/0.1.1 mix, and the publish job aborted on its first step because
attested_secure_keys_platform_interface was still 0.1.0, a version pub.dev
already has.

Bump the platform interface and the two implementation packages to 0.1.1 so
the set is back in lockstep. No code or API changes in any of them.

Also guard each publish step with .github/scripts/publish-if-new.sh, which
skips a package whose version is already on pub.dev. dart pub publish
treats that case as a hard error, so a re-run after a partial release would
otherwise keep dying on the packages that already uploaded.

Co-Authored-By: Claude Opus 5 (1M context) [email protected]

• No code or API changes. Version bump only, to keep the four federated packages in lockstep with attested_secure_keys 0.1.1.

release: 0.1.0 (first stable) + clarify verification responsibility

First stable release. Android Keystore implementation device-verified (StrongBox/TEE attestation). No functional changes since 0.1.0-dev.2.

• Renamed the Android package/namespace from ro.roeid.attested_secure_keys to io.github.exilonx.attested_secure_keys. No API or behavior change.

First prerelease. Android Keystore implementation of AttestedSecureKeysApi: EC P-256 keygen (StrongBox → TEE → software fallback), ES256 signing with DER→raw R‖S via the JDK BigInteger, security-level introspection, attestation-chain passthrough, key CRUD, and a capability probe.