fidelity-ai-workspace/ai/logs/2026-04-10.md

2026-04-10

Clarification

• PDIAP-15838 should not be framed as directly tied to the UIKit-removal spike.
• Avoid wording that implies PDIAP-15838 is dependent on or part of the dismissal-sequencing / UIKit-removal spike.
• Standups should prioritize updates directly tied to active work items and omit side questions such as version reminders that were only for internal context.
• Current focus for today is to finalize PDIAP-14859 with a dual UIKit/SwiftUI plan that removes UIHostingController dynamically while preserving both flows appropriately.
• Omit standup items that are not directly related to a story.
• Use the approved title Remove Apollo for iOS for PDIAP-15838.
• 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.