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

refactor: update agent sync behavior, improve freshness detection patterns, and add diagnostic troubleshooting script

Browse Source
This commit is contained in:
David Delagneau
2026-05-05 07:43:45 -06:00
parent f685ac37dd
commit 63e784cc97
11 changed files with 168 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -53,6 +53,8 @@ tags:
- Deeper Discourse / FTTransfer analysis now points to presentation-layer SwiftUI identity/lifecycle churn around `BankInformationView` and `BankSetupWebView`: XFlow eventing appears to set shared consumer-observed state, but current evidence does not show it directly mutating view identity, host lifecycle, or alert state.
- The working non-XFlow route appears to avoid the issue because it bypasses the extra XFlow destination presentation layer and associated state-coupling surface, while the failing playground path keeps the alert/popup transition and cover lifecycle coupled in the same reactive chain.
- The next implementation direction for the Discourse / FTTransfer issue is a pure SwiftUI fix that decouples alert state from the cover identity chain, avoiding unnecessary UIKit dependencies
- `PDIAP-16167 - AccountLink - XFlow causing web view rewrites investigation` was created for the FTTransfer AccountLink investigation and root-cause report
- Include in the `PDIAP-16167` report that the issue persists when rolling back `XFlowSDK` to `v0.1.0`, predating REST and modern architecture changes; Jeff explicitly asked David to include this in the document
- Before closing out the AO thread, send one more working-group Teams reply that summarizes the original iOS issue, links the Jira comment, Discourse comment, and PR, and separates the remaining `HybridBrokerageAccountOpening` / `JointIdentityCheck` service-side issue
- The `HybridBrokerageAccountOpening` / `JointIdentityCheck` rule-content issue appears unchanged between QA and Production in Cogstore and should be treated as the remaining service-side follow-up

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

@@ -25,3 +25,7 @@ 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, rooted in the AccountLink dismissal sequencing investigation, and sequenced after `PDIAP-15838`.
- `PDIAP-16167` - AccountLink - XFlow causing web view rewrites investigation
Detail: `project-knowledge/02-work-items/pdiap-16167.md`
Current note: active documentation/root-cause story for the FTTransfer AccountLink issue. The report should include the `XFlowSDK v0.1.0` rollback evidence and the minimal presentation-anchor fix.

24
project-knowledge/06-daily/2026-05-01.md
View File

@@ -1,10 +1,10 @@
---
type: daily
project: fidelity
date: 2026-05-04
date: 2026-05-01
status: active
focus: []
work-items: []
focus: [ao-discourse, xflow-debugging]
work-items: [pdiap-16167]
blockers: []
tags:
- daily
@@ -12,35 +12,41 @@ tags:
updated: 2026-05-04
---
# 2026-05-04
# 2026-05-01
## Focus
-
- Verify and document the root cause for the FTTransfer AccountLink web-view reload issue.
---
## Work Done
-
- Created `PDIAP-16167 - AccountLink - XFlow causing web view rewrites investigation`.
- Prepared the root-cause report for the FTTransfer AccountLink issue.
- Verified that XFlow eventing does not appear to be the direct cause of the reload.
- Verified that the issue persists when rolling back `XFlowSDK` to `v0.1.0`, which predates REST and modern architecture changes.
- Identified a minimal presentation-anchor change that resolves the alert auto-dismiss and web-view reload behavior.
---
## Findings
-
- Current evidence points to a consumer SwiftUI presentation-layer issue rather than recent XFlowSDK or XFlowViewMaker changes.
- The rollback-to-`XFlowSDK v0.1.0` finding should be included in the report because it helps separate the issue from recent XFlow changes.
---
## Communication
-
- Jeff asked David to put the findings into a Confluence report, share it with Zachary, and comment it on the story.
- Jeff specifically asked David to include the XFlowSDK version / rollback evidence in the report.
---
## Next Steps
-
- Finalize and share the root-cause report with the rollback evidence and minimal fix note.
---