fix: final error-recovery audit and v1.1.4 release candidate

[Zudin987]

Final reliability audit — v1.1.4 release preparation

Merged to main as 9de9b4a181dfebbcb1e5aecbfeec815cd34b3205. v1.1.4 has not been published.

Changes

• Reject missing/tampered Android profiles, mismatched SHA-256 profile identity, PC IP, and missing or rotated SOCKS credentials; prevent silent credential regeneration and reject unconfirmed legacy profile state.
• Preserve original state files on replacement fallback and keep a recovery backup if restoration fails.
• Surface tray shutdown errors without closing the manager, distinguish degraded listener and actual firewall/profile health, log sanitized phone setup errors and bound UI log length.
• Add native regression cases for valid/missing/tampered/stale-credential and legacy profile states; bump native manager version to 1.1.4 with release notes.

Verification and evidence

• PR-head Windows Validate succeeded on 3968f12f36b627907e3fc9cba638b1bfaf14db71.
• PR-head Field Test Package succeeded and generated candidate package BPSR-Relay-v1.1.4-field-test (automated packaging, not device validation).
• Owner reported 'pass' for the requested field test in chat on September 20, 2026. This is a user-reported result; detailed device logs were not supplied and have not been independently reviewed.
• Merged by squash to exact main commit 9de9b4a181dfebbcb1e5aecbfeec815cd34b3205.
• Exact-main Windows Validate succeeded across native build, regression tests, UI/tray checks, sing-box self-test, two-stage TCP/UDP smoke, package integrity and artifact upload.
• Main test-package artifact BPSR-Android-DPSMeter-Relay-test-package generated from exact merge commit.

Release status: The planned gates are satisfied on the basis of the owner-reported field test and independently verified CI. Publication remains a separate explicitly requested step through the existing Release workflow with truthful field-test confirmation. No stable v1.1.4 release was created as part of this PR.