fix(android): repair corrupt release APK + zero-byte motion recordings

[keyldev]

• AndroidUseAssemblyStore=false: the toolchain packed libassembly-store.so with a bad CRC-32, so Android rejected v0.3.4/v0.3.6 as "package corrupt"
• CI: hard-verify APK integrity (unzip -t) and give the x64 APK a distinct name so it no longer collides with arm64 in the release
• Recorder: add an interrupt callback bound to the CTS + real RTSP timeout so a stalled camera can't strand the writer thread before av_write_trailer, which left motion-triggered recordings on disk at 0 bytes

Summary

Related

Type

• Bug fix
• Feature
• Refactor / cleanup
• Docs / CI
• Other:

Checklist

• Builds with 0 warnings (TreatWarningsAsErrors=true).
• Tests pass (dotnet test); new Core logic has unit tests.
• No layering violation — App references Core only (Infrastructure / Video / Devices wired via DI in a head).
• Scope stays within one phase (didn't pull work from a later phase's "Не входит").
• README / docs updated if public commands, options, or setup changed.

Platforms tested

• Windows
• Linux
• macOS
• Android
• iOS
• CI build only

Screenshots / notes