Before and afterRe-contract the integration
Resolve each dimension explicitly. “It compiled” does not prove identity, lifecycle, failure, privacy, or operational compatibility.
DimensionLegacy exposureCandidate targetRequired proof
DistributionHistorical binaries or monolithic SDK setup may be embedded manually.
Use the approved modular distribution channel and pin compatible package identities and versions.
Resolved Package.resolved/binary checksums, license inventory, clean archive, and launch test.
InitializationCredential and SDK setup can be tied to application-delegate assumptions.
Initialize once at the documented app/scene boundary and inject narrow providers into features.
Multi-scene, background, restoration, logout, and test-host behavior.
OwnershipMap views, delegates, observers, or navigation sessions can outlive screens.
Give every resource one owner and explicit cancellation/retirement behavior.
Repeated present/dismiss, memory pressure, interrupted navigation, and leak checks on hardware.