Update work items and daily logs for project fidelity

- Updated work items with new statuses, notes, and dependencies:
  - `PDIAP-15838` moved to Done, draft PR remains unmerged.
  - `PDIAP-15836` status updated to backlog-ready, sequenced after `PDIAP-15838`.
  - `PDIAP-12284` reopened for UIKit removal, dependency for `PDIAP-15836`.
  - Added new backlog items: `PDIAP-11961`, `PDIAP-11962`, `PDIAP-11562`, `PDIAP-12226`, `PDIAP-12227`, `PDIAP-12228`.
- Completed `PDIAP-16167`, documented findings in Confluence.
- Created daily log for 2026-05-05 summarizing work item updates and backlog triage.
- Added diagnostic script for workspace analysis.
This commit is contained in:
2026-05-05 15:54:45 -06:00
parent 63e784cc97
commit 2a234701c5
15 changed files with 443 additions and 37 deletions

View File

@@ -1,14 +1,14 @@
---
type: work-item
project: fidelity
status: active
status: backlog-ready
ticket: PDIAP-15836
title: "Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment"
systems: [xflowsdk, xflowviewmaker, ftframeworks]
workstreams: [xflow-swiftui-migration, consumer-integration]
people: [jeff-dewitte]
related: [pdiap-14859]
updated: 2026-04-21
related: [pdiap-14859, pdiap-12284, pdiap-15838]
updated: 2026-05-05
tags:
- work-item
- fidelity
@@ -19,8 +19,9 @@ tags:
## Status
- Approved
- Sequenced after `PDIAP-15838`
- Approved, but should not be moved to In Progress until the next sprint starts
- Jeff asked David to start working on the `PDIAP-15836` / `PDIAP-12284` implementation path, with Jira status movement deferred until Thursday after lunch
- Sequenced after `PDIAP-15838` source work, but merge/release is delayed until after REST-transition consumer validation
- Sized at `8` points
---
@@ -44,8 +45,11 @@ tags:
## Sequencing And Dependencies
- This story should come after `PDIAP-15838`.
- `PDIAP-12284` is the original UIKit-wrapping removal story and was reopened after rollback.
- Current relationship to add/track in Jira: `PDIAP-15836` is blocked by `PDIAP-12284`, because the UIKit removal needs to land for the lifecycle fix to apply. David still needs to validate whether any part of `PDIAP-15836` can be implemented independently on the SwiftUI path.
- It is aligned with epic `26Q2 - Updating XFlowSDK to Decouple and Fix ApexKit Dependencies (Split Part 2)`.
- If possible, it should use the same consumer-impact feature flag strategy as the broader UIKit-removal rollout.
- Expect a long-lived branch: after implementation, maintain the branch until consumer-testing approval. Jeff expects the GraphQL-removal branch to merge first after the REST validation period, then that branch should be merged into the `PDIAP-15836` / `PDIAP-12284` branch. Current estimate is roughly 90-100 days from 2026-05-05 unless Fidelity shortens the review windows.
---
@@ -56,3 +60,4 @@ tags:
- The Confluence/root-cause document was updated to reflect that FTTransfer changes are not the primary need anymore.
- The primary recommendation is to adjust the dismissal handling/sequencing correctly in the hosting path.
- FTTransfer improvements can still be mentioned as a secondary improvement, but not as a required change to reproduce the same visual behavior.
- When explaining why code still remains, clarify that the spike identified and documented the root cause, but implementation changes have not yet been published.