feat: Update documentation for PDIAP-14859 and PDIAP-15765, including rollout approvals and next steps

ai/work-items/index.md

@@ -9,7 +9,7 @@ Provide a quick view of active and recently relevant Jira-linked work while keep
 ## Active
 
 - [pdiap-14859.md](./pdiap-14859.md)
-  `PDIAP-14859` `Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation` active spike/planning work around dual UIKit/SwiftUI support, dynamic `UIHostingController` removal, and consumer rollout planning.
+  `PDIAP-14859` `Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation` spike wrap-up work around dual UIKit/SwiftUI support, dynamic `UIHostingController` removal, consumer rollout planning, and linking the final result documents.
 
 - [pdiap-15838.md](./pdiap-15838.md)
   `PDIAP-15838` next story to work on; approved scope removes Apollo and GraphQL-specific iOS transport code while leaving REST.
@@ -17,10 +17,10 @@ Provide a quick view of active and recently relevant Jira-linked work while keep
 - [pdiap-15836.md](./pdiap-15836.md)
   `PDIAP-15836` approved follow-up story for dismissal delegate lifecycle sequencing in pure SwiftUI; comes after `PDIAP-15838`.
 
-## Holding / Closure Pending
+## Active / Reopened
 
 - [pdiap-15765.md](./pdiap-15765.md)
-  `PDIAP-15765` authenticated-only TeenIdentityCheck DOB issue; root cause documented and waiting for the right closure timing.
+  `PDIAP-15765` authenticated-only TeenIdentityCheck DOB issue; reopened around the iOS-only Youth-flow handling gap while the separate cross-platform `HybridBrokerage` scenario stays out of scope.
 
 ---
 

ai/work-items/pdiap-14859.md

@@ -4,6 +4,7 @@
 
 - Active
 - Rollout draft prepared and sent to Jeff for review on April 13, 2026
+- Rollout document approved for publication; publish and close out the spike next
 
 ---
 
@@ -35,7 +36,11 @@
 - The draft shared with Jeff already reflects the global feature flag, broad `XQ1` validation, and consumer-facing rollout flow guidance.
 - Additional review feedback from April 13: rename the proposed flag to `xflow-swiftui-enabled`, make consumer contact and `XQ1` validation explicit in the first phase, remove overly technical rollout wording, and avoid implying there are no consumer-side changes without qualification.
 - On April 14, Jeff asked whether the FTTransfer part of the rollout document also needed updating; David confirmed the document had already been revised to clarify that root-cause section.
-- Await final follow-up after incorporating the latest review feedback.
+- April 15 clarification: do not reuse the existing SwiftUI LaunchDarkly flag for this rollout.
+- The new flag name for this work should be `xflow-swiftui-container-enabled`.
+- The document should note that the flag is `to be added in the future as part of implementation`.
+- Late April 14 guidance: the document was approved late in the day; the next step is to publish it, then close out the spike by commenting `Spike Results:` with the relevant document links and the new follow-up story link.
+- The new follow-up story should also be marked as a blocker for the reopened UIKit-removal story.
 
 ---
 

ai/work-items/pdiap-15765.md

@@ -2,8 +2,8 @@
 
 ## Status
 
-- Holding
-- Ready for closure timing review
+- Active again
+- Move back to In Progress on the next workday
 
 ---
 
@@ -38,4 +38,6 @@
 
 ## Next Step
 
-- Jeff approved moving the story to Done once the new sprint starts.
+- Resume the story and implement the iOS-side handling so the authenticated Youth `TeenIdentityCheck` service response is handled the same way as Android.
+- Keep the separate `HybridBrokerage` scenario out of the client-fix scope unless later evidence proves it is part of the same issue.
+- Consider a separate follow-up ticket for the cross-platform service-side issue if that path still stands after the iOS-only fix is underway.