v0.5.0

Deep architecture hardening, messenger delivery-chain detection, family share receipts, and OEM deep-link fallback chains — the largest jump in detection depth since Phase 1.

Added

• Deep architecture hardening. The risk engine moved from a boolean cascade to a continuous, point-based score (CRITICAL ≥ 80, HIGH ≥ 50, SUSPICIOUS ≥ 20). App signing certificates are checked against a hardcoded set of trusted keys as an absolute-trust override. Impersonation matching uses Levenshtein fuzzy matching plus a taskAffinity hijacking check. All Binder/PackageManager IPCs now run off the main thread.
• Scam delivery-chain detection for messengers. A new signal fires when an app's install traces back to WhatsApp, WhatsApp Business, Telegram, or another recognized messenger — the exact real-world path scam APKs travel.
• Danger reasons on the app-detail screen ranked by the engine's own point weights, most decisive first.
• Screen readers now announce the danger verdict before the app name.
• The scan is now resilient to the ~1 MB Binder reply-size limit on cheap phones with many installed apps.
• The mid-scam watchdog notification now speaks to someone being actively walked through an install by a scammer.
• "Send result to family" — an offline, timestamped share-sheet receipt so a remote family member can see what a scan found.
• A phone-health severity bar and per-app launcher icons on result cards; a complete dark-theme polish pass.
• OEM deep-link fallback chains — Device-Admin and auto-start "fix" buttons now try an ordered, per-maker chain (Samsung/Xiaomi/Oppo/Vivo/Huawei, with OnePlus/Realme/Poco/Redmi/iQOO sub-brand aliasing) instead of betting on one hardcoded screen.

Full detail: CHANGELOG.md

Fully offline, as always — no INTERNET permission, verified in the merged manifest before this release was built.