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

chore: update work item statuses and daily logs for May 8, 2026, including new daily log entry

Browse Source
This commit is contained in:
David Delagneau
2026-05-08 08:09:39 -06:00
parent 1c9b9fd51a
commit 1382f1ac1a
7 changed files with 69 additions and 16 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
project-knowledge/01-current/current-work.md
View File

@@ -2,7 +2,7 @@
type: current
project: fidelity
status: active
updated: 2026-05-05
updated: 2026-05-08
tags:
- current-work
- fidelity
@@ -18,7 +18,8 @@ tags:
- Follow up on active tickets through `project-knowledge/02-work-items/`, especially branch maintenance for `PDIAP-15838` and implementation planning for `PDIAP-15836` / `PDIAP-12284`
- `PDIAP-15765` is done and `PDIAP-14859` is also done
- `PDIAP-15838` is Done from a Jira/status perspective after external review feedback was addressed, but its draft PR must remain unmerged and kept current with `main` until REST backend production readiness and the required REST-toggle consumer validation window allow merge
- `PDIAP-15836` is now paired with `PDIAP-12284` for the UIKit-removal / pure SwiftUI lifecycle implementation path; Quy already moved both into next sprint `26Q2.6`, David can start work now, but leave Jira status in To Do and do not move either story to In Progress until Thursday
- `PDIAP-15836` has moved to In Progress. David found a possible minimal dismissal fix path that would not require removing `UIHostingController`, but Jeff directed David to do the `PDIAP-15836` dismissal/lifecycle work and `PDIAP-12284` UIKit-removal work in the same branch because both are disruptive enough to require consumer testing.
- `PDIAP-12284` remains paired with `PDIAP-15836`; plan the branch as combined UIKit-removal / SwiftUI lifecycle work rather than splitting the dismissal sequencing into an independently merged path unless direction changes.
- Keep the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` scenario out of `PDIAP-15765` scope unless later evidence proves it belongs there
- Include feature-flag planning for the broader UIKit-removal spike, including dismissal sequencing changes that affect consumers
- Thoroughly verify current `ApexBridgingAddressComponent` / rule-loading usage before describing it as inactive or dead code

6
project-knowledge/01-current/work-items.md
View File

@@ -2,7 +2,7 @@
type: current-work-items
project: fidelity
status: active
updated: 2026-05-05
updated: 2026-05-08
tags:
- current-work
- work-item
@@ -24,11 +24,11 @@ Update the per-ticket files first when scope, status, sequencing, or communicati
- `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
Detail: `project-knowledge/02-work-items/pdiap-15836.md`
Current note: approved at `8` points and now paired with `PDIAP-12284` for the UIKit-removal implementation path. Quy already moved it into next sprint `26Q2.6`; leave it in To Do and do not move to In Progress until Thursday. Treat `PDIAP-15836` as blocked by `PDIAP-12284` unless validation proves the lifecycle fix can be implemented independently.
Current note: moved to In Progress on May 7. David found a possible minimal dismissal fix path that would not require removing `UIHostingController`, but Jeff directed David to do the dismissal/lifecycle work and `PDIAP-12284` UIKit-removal work in the same branch because both changes require consumer testing.
- `PDIAP-12284` - Remove UIKit wrapping from XFlow
Detail: `project-knowledge/02-work-items/pdiap-12284.md`
Current note: reopened after rollback and should be handled with `PDIAP-15836`. Quy already moved it into next sprint `26Q2.6`; work can begin now, but Jira status stays To Do until Thursday and merge/release waits until after REST-transition consumer validation.
Current note: reopened after rollback and should be handled with `PDIAP-15836` in the same branch. Jeff's current direction is to combine the UIKit-removal and dismissal/lifecycle changes because both are disruptive enough to require consumer testing; merge/release still waits until after REST-transition consumer validation.
## Backlog / Future Reference

6
project-knowledge/02-work-items/pdiap-12284.md
View File

@@ -8,7 +8,7 @@ systems: [xflowsdk, xflowviewmaker]
workstreams: [xflow-swiftui-migration, consumer-integration]
people: [jeff-dewitte]
related: [pdiap-15836, pdiap-15838]
updated: 2026-05-05
updated: 2026-05-08
tags:
- work-item
- fidelity
@@ -22,14 +22,14 @@ tags:
- Reopened after rollback.
- Quy already moved this story into the next sprint (`26Q2.6`); leave it in To Do until the sprint starts on Thursday.
- Jeff asked David to start working on this with `PDIAP-15836`, but not to move the active story to In Progress until Thursday.
- Jeff directed David to do this UIKit-removal work and `PDIAP-15836` dismissal/lifecycle work in the same branch because both are disruptive enough to require consumer testing.
---
## Context
- This is the original story for removing the UIKit wrapping.
- Current relationship to track: `PDIAP-15836` is blocked by this story because the lifecycle-sequencing fix depends on the UIKit removal landing, unless further validation proves part of `PDIAP-15836` can be implemented independently on the SwiftUI path.
- Current relationship to track: `PDIAP-12284` should be handled with `PDIAP-15836` in the same implementation branch. David identified a possible minimal `PDIAP-15836` fix path that does not require removing `UIHostingController`, but Jeff prefers combined branch work because both changes require consumer testing.
---

12
project-knowledge/02-work-items/pdiap-15836.md
View File

@@ -1,14 +1,14 @@
---
type: work-item
project: fidelity
status: backlog-ready
status: in-progress
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, pdiap-12284, pdiap-15838]
updated: 2026-05-05
updated: 2026-05-08
tags:
- work-item
- fidelity
@@ -19,9 +19,9 @@ tags:
## Status
- Approved, but should not be moved to In Progress until the next sprint starts
- Quy already moved this story into the next sprint (`26Q2.6`); leave it in To Do until the sprint starts on Thursday
- Jeff confirmed David can start the actual implementation work now, but must not move the story to In Progress until Thursday
- Moved to In Progress on May 7.
- David found a possible minimal dismissal fix path that would not require removing `UIHostingController`, and was validating it.
- Jeff directed David to do this dismissal/lifecycle work together with `PDIAP-12284` in the same branch because both changes are disruptive enough to require consumer testing.
- Sequenced after `PDIAP-15838` source work, but merge/release is delayed until after REST-transition consumer validation
- Sized at `8` points
@@ -47,7 +47,7 @@ tags:
- 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.
- Current working relationship: implement and validate `PDIAP-15836` together with `PDIAP-12284` in the same branch unless direction changes. David identified a possible isolated/minimal fix path, but Jeff prefers combined branch work because consumer testing is required either way.
- 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.

49
project-knowledge/06-daily/2026-05-08.md Normal file
View File

@@ -0,0 +1,49 @@
---
type: daily
project: fidelity
date: 2026-05-08
status: active
focus: [pdiap-15836, pdiap-12284]
work-items: [PDIAP-15836, PDIAP-12284]
blockers: []
tags:
- daily
- fidelity
updated: 2026-05-08
---
# 2026-05-08
## Focus
- Capture the May 7 Mattermost thread updates for `PDIAP-15836` / `PDIAP-12284` and keep current work memory aligned with Jeff's direction.
---
## Work Done
- Mattermost sync confirmed David moved `PDIAP-15836` to In Progress and found a possible minimal dismissal fix path that would not require removing `UIHostingController`.
---
## Findings
- David's early `PDIAP-15836` finding was that the tested dismissal approach appeared coupled to the `UIHostingController` removal path, but he was investigating whether the lifecycle/dismissal fix could be isolated.
---
## Communication
- Jeff directed David to do the `PDIAP-15836` dismissal/lifecycle work and `PDIAP-12284` UIKit-removal work in the same branch, because both changes are disruptive enough to require consumer testing.
---
## Next Steps
- Treat `PDIAP-15836` and `PDIAP-12284` as same-branch work unless later direction changes; keep consumer-testing impact explicit.
---
## Blockers
- None currently.

4
project-knowledge/06-daily/index.md
View File

@@ -1,7 +1,7 @@
---
type: daily-index
project: fidelity
updated: 2026-05-05
updated: 2026-05-08
tags:
- daily
- map
@@ -30,6 +30,8 @@ Promote durable facts into `project-knowledge/01-current/`, `project-knowledge/0
- [2026-04-29](2026-04-29.md)
- [2026-04-30](2026-04-30.md)
- [2026-05-05](2026-05-05.md)
- [2026-05-07](2026-05-07.md)
- [2026-05-08](2026-05-08.md)
---