[Kapusch]

What changed

• retain the TikTok Share request and managed callback for the full handoff
• use static iOS interop symbols and accept the OpenSDK-supported single-image flow
• add an idempotent escape hatch for a host app returning without an OpenSDK callback
• document the Photos identifier contract and lifecycle recovery

Why

OpenSDK can leave a share request pending when the user switches back to the host app without completing or cancelling in TikTok. The retained request then blocks subsequent shares and the managed caller never completes.

Impact

Consumers can call NativeTikTokShare.AbandonPendingShare() after a genuine background-to-active return and a short callback grace period. The pending task completes once with Cancelled and returned_without_callback; late SDK callbacks are ignored.

Validation

• native wrapper build for device and both simulator architectures
• managed Release build
• local NuGet pack and scripts/validate-package.sh
• physical-device share, explicit cancellation, manual return, and immediate second share