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

feat: update daily logs and work items for 2026-04-29; refine Apollo removal strategy and address FTTransfer issue

Browse Source
This commit is contained in:
David Delagneau
2026-04-29 07:39:55 -06:00
parent d3c5d8f7de
commit fa1ab57de8
6 changed files with 99 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -2,7 +2,7 @@
type: current
project: fidelity
status: active
updated: 2026-04-28
updated: 2026-04-29
tags:
- current-work
- fidelity
@@ -42,8 +42,12 @@ tags:
- Jeff suggested broadening the investigation support path while direct Flagship LaunchDarkly access is still missing: monitor the Tauf thread, follow up with Jeffrey O'Leary, package the scenario for the AI tool with build settings and tool details, and ask Aylwing for a quick perspective if available
- The Fidelity-side AI tool Jeff referenced for this investigation is GitHub Copilot
- Jeff later relayed that Adam says the latest build is now activating REST correctly, so David should switch back to the current Jira story work for removing GraphQL and related LaunchDarkly toggles
- Do not merge the GraphQL/Apollo removal PR until the REST backend is deployed to production; GraphQL fallback is still needed before then
- Current `PDIAP-15838` follow-up includes Fid4 validation, simulator-vs-device/generated-build configuration checks, and investigating the `PicoSDK` upgrade path for `SampleApp` because current `PicoSDK` usage still brings Apollo transitively
- `PDIAP-15838` draft PR is open for internal review; after internal review, send the link to Bruce
- Do not merge the GraphQL/Apollo removal PR until the previous REST-toggle implementation has been QA-tested and active in production with REST enabled for all consumers for 30 days without issues
- Current `PDIAP-15838` follow-up centers on the `PicoSDK` update in `SampleApp`: the newer Pico path removes the remaining transitive Apollo dependency, re-enables FGO and FidFolios testing in `SampleApp`, and aligns the sample implementation with current Fid4 usage
- The `PicoSDK` update affects `SampleApp`, not the `XFlowSDK` production runtime directly
- The new Discourse / FTTransfer AccountLink issue is under investigation; Zachary believes it may come from XFlow, but ownership should not be stated until David reproduces it and confirms scope
- For the Discourse / FTTransfer issue, David has `FTTransferPlayground` running near Zachary's reported path but is currently blocked before the web view by phone-number verification / a Face ID-related error
- 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
@@ -65,7 +69,7 @@ tags:
- Adam reported the earlier REST activation problem, and he or his team validate behavior on real devices rather than simulator-only paths
- Avoid treating GitHub Copilot or LaunchDarkly as story-specific tools; both are broader Fidelity workflow tools that happened to matter in this investigation
- Defining a consumer rollout plan for UIKit-removal sequencing changes, including validation, communication, and feature-flag retirement
- Keep Apollo-removal / REST-migration cleanup grounded in backend readiness: source-level cleanup can continue, but merge/release timing depends on REST backend production deployment
- Keep Apollo-removal / REST-migration cleanup grounded in production readiness: source-level cleanup can continue, but merge/release timing depends on the prior REST-toggle implementation being QA-tested and stable in production for the agreed window
- Avoiding assumptions when comparing iOS and Android validation behavior; scenario-specific parity needs to be confirmed before reporting scope
- Avoiding assumptions about legacy Apex/ApexKit paths; breakpoint evidence and helper usage both need to be reconciled before reporting ownership or replacement guidance
- When ownership is still uncertain under production pressure, prefer rollback-plus-investigation framing over confident blame assignment to consumers

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

@@ -2,7 +2,7 @@
type: current-work-items
project: fidelity
status: active
updated: 2026-04-28
updated: 2026-04-29
tags:
- current-work
- work-item
@@ -20,7 +20,7 @@ Update the per-ticket files first when scope, status, sequencing, or communicati
- `PDIAP-15838` - Remove Apollo for iOS
Detail: `project-knowledge/02-work-items/pdiap-15838.md`
Current note: active Apollo-removal cleanup and validation; do not merge the PR until the REST backend is deployed to production because GraphQL fallback is still needed. Current follow-up includes Fid4 validation, simulator-vs-device/generated-build configuration checks, and `PicoSDK` upgrade investigation for `SampleApp` because the current setup still brings Apollo transitively.
Current note: active Apollo-removal cleanup and validation; draft PR is open for internal review. `SampleApp` was updated to a newer `PicoSDK` path so Apollo is removed from the transitive sample-app dependency path too. Do not merge until the previous REST-toggle implementation has been QA-tested and active in production with REST enabled for all consumers for 30 days without issues.
- `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
Detail: `project-knowledge/02-work-items/pdiap-15836.md`