Harden relay reliability, redact diagnostics, document field validation

[Xare123]

Summary

• harden relay lifecycle, reconnect scheduling, and foreground recovery
• validate custom relay URLs and relay payloads before use
• redact credential-bearing values from app logs and store reconnect credentials in Keychain with a local fallback
• bound in-app log retention and add validation-request timeout and error handling
• add a checksum-verified bundled Apple validation certificate fallback when certificate retrieval fails due to trust errors
• document the field-tested device configuration and its release boundaries

Root causes addressed

The changes target reconnect races and zombie sockets from overlapping lifecycle paths, reconnect storms after transient network failures, weak protocol matching that could accept malformed messages or overwrite credentials, unbounded diagnostic-log growth, and validation failures caused by certificate trust or native-service errors. Registration secrets are no longer emitted in diagnostics, and reconnect credentials use protected storage when available.

Field validation

The following workflow has been exercised successfully on one concrete setup:

• macOS/Xcode compilation of the iOS target
• signing and installation on a non-jailbroken iPhone 7 through TrollStore/ImmortalizerTS
• iOS 15.7.9 Apple validation-data exchange, carrier registration, and physical-device relay behavior
• foreground/Keep Awake operation, plus locked-phone and display-off endurance with ImmortalizerTS working and the relay remaining operational

This validates the checked iPhone 7/iOS 15.7.9 configuration only. It is not a universal compatibility claim for other iOS releases, device models, carriers, signing environments, or network paths.

Automated and static checks

• git diff --check origin/main...HEAD
• git fsck --full --no-reflogs
• gitleaks detect --source . --no-banner --redact --exit-code 1
• parsed Info.plist, entitlements, and Package.resolved
• verified bundled certificate length and SHA-256 against the in-source checksum

Remaining limitations

• iOS suspension, background execution, and network-path migration remain device and OS dependent; a WebSocket that connects is not proof that Apple validation or downstream message acknowledgement succeeded.
• Xcode compilation and long locked/display-off endurance testing must be repeated for each future release candidate and for other device/OS combinations before release.
• Actual release readiness still requires target-device testing of sign-in, reconnects, network changes, validation failures, and message delivery on the intended deployment configuration.