david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Enhance communication and documentation for standup context and work item clarity

Browse Source
This commit is contained in:
David Delagneau
2026-04-13 10:24:01 -06:00
parent 07e198a641
commit e0dd7538cc
8 changed files with 32 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
ai/work-items/index.md
View File

@@ -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` 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` active spike/planning work around dual UIKit/SwiftUI support, dynamic `UIHostingController` removal, and consumer rollout planning.
- [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.

9
ai/work-items/pdiap-14859.md
View File

@@ -1,14 +1,15 @@
# PDIAP-14859
# PDIAP-14859 - Spike - Research strategy to remove final UIKit wrapping from XFlowSDK and XFlowViewMaker without disrupting consumer implementation
## Status
- Active
- Current focus on April 10, 2026
- Rollout draft prepared and sent to Jeff for review on April 13, 2026
---
## Current Framing
- 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.
@@ -20,6 +21,7 @@
- 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.
@@ -28,9 +30,10 @@
## Notes
- The workspace does not currently hold an approved final title for this ticket beyond the Jira ID.
- 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.
---

1
ai/work-items/pdiap-15765.md
View File

@@ -19,6 +19,7 @@
- The issue reproduces only for authenticated users based on the currently stored evidence.
- Root cause was documented.
- The original external report was incomplete.
- For the config discussion, `CheckIdentity` was already correct. The `TeenIdentityCheck` issue had two config gaps inside `validation-rules`: the root key should be `validations`, and the age gate also needs `eighteenOrAbove` there when that rule is required.
---