PDIAP-14859 - Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation

Status

Approved title: Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation.
This work is currently framed in the workspace as a dual UIKit/SwiftUI plan that removes UIHostingController dynamically while preserving both flows appropriately.
The remaining deliverable is process-oriented, not just technical implementation.

Define a consumer-facing rollout plan for the broader UIKit-removal work.
Preserve both UIKit and SwiftUI paths appropriately while introducing the new path safely.
Cover risky entry points such as FTTransfer.
Include validation expectations in XQ1.
Use a global feature-flag rollout model rather than entry-point-based enablement.
Include consumer communication expectations.
Include a 30-day production period with no reported bugs before final removal.
Include a follow-up release to remove the feature flag and old code after rollout confidence is achieved.

The feature-flag and rollout planning guidance applies to the broader UIKit-removal spike, not only to dismissal-sequencing work.
Jeff suggested sending the process-oriented rollout document to Quy for feedback when ready.
The draft shared with Jeff already reflects the global feature flag, broad XQ1 validation, and consumer-facing rollout flow guidance.
Await Jeff's review feedback before treating the rollout framing as final.