feat: Update standup and work item documentation for clarity and story prioritization

ai/logs/2026-04-09.md

@@ -9,6 +9,7 @@
 - Created `PDIAP-15836` for dismissal delegate lifecycle sequencing in pure SwiftUI (`8` points)
 - Aligned `PDIAP-15838` scope with REST migration cleanup and feature-flag removal
 - Confirmed XFlowViewMaker `0.5.0` is already in Fid4
+- Updated the root cause document for the AccountLink dismissal sequencing issue tied to `PDIAP-15836` and got approval on the proposed wording
 
 ---
 
@@ -26,6 +27,7 @@
 
 - Prepared clearer wording for Jeff
 - Focused on context, observation, and action instead of vague comparison language
+- Proposed a root cause document update and got confirmation on the revised wording
 
 ---
 

ai/logs/2026-04-10.md

@@ -0,0 +1,12 @@
+# 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`.