From 010639b5928562707dc63f7e62b5be948d78f680 Mon Sep 17 00:00:00 2001 From: "david.delagneau" Date: Fri, 10 Apr 2026 09:16:06 -0600 Subject: [PATCH] feat: Enhance documentation for UIKit-removal spike and clarify work item dependencies --- ai/logs/2026-04-10.md | 2 ++ ai/state/current.md | 2 ++ ai/state/work-items.md | 2 +- 3 files changed, 5 insertions(+), 1 deletion(-) diff --git a/ai/logs/2026-04-10.md b/ai/logs/2026-04-10.md index b34a527..0f9222c 100644 --- a/ai/logs/2026-04-10.md +++ b/ai/logs/2026-04-10.md @@ -11,3 +11,5 @@ - When a documentation or root cause update directly supports a story, report it under that story instead of as a separate standup item. - In standups, format Jira references as `ID - Title` or `ID Title`, not `ID, Title`. - Jeff clarified that `PDIAP-15838` is the next story to work on and `PDIAP-15836` comes later. +- Clarification: the feature-flag and rollout planning feedback applies to the broader UIKit-removal spike, not only to the dismissal sequencing changes; the sequencing work should fit into that same consumer rollout plan. +- Jeff said the remaining spike deliverable is a clear consumer-facing rollout plan covering risky entry points like FTTransfer, consumer communication, XQ1 validation, a 30-day production period with no reported bugs, and a follow-up release to remove the feature flag and old code; he suggested sending that process-oriented document to Quy for feedback when ready. diff --git a/ai/state/current.md b/ai/state/current.md index ba2115d..720055b 100644 --- a/ai/state/current.md +++ b/ai/state/current.md @@ -9,6 +9,7 @@ - Follow up on `PDIAP-15765`, `PDIAP-15836`, and `PDIAP-15838` - Finalize `PDIAP-14859` with a dual UIKit/SwiftUI plan that removes `UIHostingController` dynamically while preserving both flows appropriately - Prioritize `PDIAP-15838` next; `PDIAP-15836` comes later +- Include feature-flag planning for the broader UIKit-removal spike, including dismissal sequencing changes that affect consumers --- @@ -21,6 +22,7 @@ - Preserving accurate context when summarizing work from another machine - Validating dismissal sequencing changes across SwiftUI flows - Keeping REST deprecation scope explicit while GraphQL fallback still exists +- Defining a consumer rollout plan for UIKit-removal sequencing changes, including validation, communication, and feature-flag retirement --- diff --git a/ai/state/work-items.md b/ai/state/work-items.md index d55dd43..82687f4 100644 --- a/ai/state/work-items.md +++ b/ai/state/work-items.md @@ -10,7 +10,7 @@ Update it only with explicit, project-relevant information that is useful for fu Current note: root cause was documented; the DOB validation issue was confirmed on TeenIdentityCheck for authenticated users, and Jeff approved moving the story to Done once the new sprint starts. - `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment - Current note: story came out of the AccountLink root cause investigation and related root cause document update; it was sized at 8 points, aligned with epic `26Q2 - Updating XFlowSDK to Decouple and Fix ApexKit Dependencies (Split Part 2)`, is meant to cover SwiftUI dismissal sequencing validation, and should come after `PDIAP-15838`. + Current note: story came out of the AccountLink root cause investigation and related root cause document update; it was sized at 8 points, aligned with epic `26Q2 - Updating XFlowSDK to Decouple and Fix ApexKit Dependencies (Split Part 2)`, is meant to cover SwiftUI dismissal sequencing validation, should come after `PDIAP-15838`, and should use the same consumer-impact feature flag as the UIKit-removal rollout if possible. - `PDIAP-15838` - Remove Apollo for iOS Current note: approved at 8 points; description and ACs were filled in and Jeff approved the scope to remove Apollo, GraphQL-specific networking code, related tests and mocks, and transport feature flags so REST remains. This is the next story to work on before `PDIAP-15836`.