feat: Update work items and daily log for Apollo removal progress and SwiftUI migration cleanup

project-knowledge/06-daily/2026-04-21.md

@@ -3,8 +3,8 @@ type: daily
 project: fidelity
 date: 2026-04-21
 status: active
-focus: [rest-migration]
-work-items: [pdiap-15838]
+focus: [rest-migration, xflow-swiftui-migration]
+work-items: [pdiap-15838, pdiap-15836]
 blockers: []
 tags:
   - daily
@@ -24,6 +24,8 @@ updated: 2026-04-21
 
 - Cleaned up the active production model layer so it no longer depends on Apollo-generated models for the current path.
 - Removed the three `NetworkClient.shared.updateAppSyncURL(...)` calls from `XFlowInitManager` and removed `getAppSyncEndPoint()` after it became unused; the project still compiles.
+- Updated the Confluence/root-cause document for the FTTransfer discussion so it now reflects the current recommendation.
+- Removed the `ApolloGeneratedCode` runtime tree and its project wiring from XFlowSDK.
 
 ---
 
@@ -34,6 +36,12 @@ updated: 2026-04-21
 - Any Apollo dependency that remains only through PicoSDK should be treated separately from source-level cleanup.
 - Copilot's focused runtime/init guidance says the safest next source-level step is to remove only the three `updateAppSyncURL(...)` calls from `XFlowInitManager`, then delete internal `getAppSyncEndPoint()` if it becomes unused, while leaving `NetworkClient.swift` and `XFlowInitManagerConfig.swift` in place temporarily as disconnected compatibility surface until later cleanup.
 - After that step, no live init/session runtime wiring from `XFlowInitManager` into Apollo/AppSync remains; the remaining Apollo surface appears to be disconnected compatibility/runtime code plus later package/build/test cleanup.
+- Follow-up scan says `GraphQL/NetworkClient.swift` now appears runtime-dead for production, `GraphQL/ApolloGeneratedCode` appears unreferenced by production runtime after model cleanup, and the safest next step is to remove `NetworkClient.swift` first, then validate before removing `ApolloGeneratedCode`.
+- Broader Apollo cleanup has now removed `NetworkClient.swift`, `ApolloGeneratedCode`, Apollo-specific test files/mocks, and related project-file entries. Current reported state says production code has zero live Apollo imports/references and retained REST behavior, while remaining follow-up work is package/build cleanup plus the deferred compatibility API surface in `XFlowInitManagerConfig.swift`.
+- Test-target cleanup is now also in a good state: a minimal update to `XFlowTransportSelectionTests.swift` removed obsolete GraphQL/Apollo assertions, preserved REST-oriented coverage, and left no remaining non-environment test-target compile errors.
+- The current FTTransfer communication should say the primary fix is the dismissal adjustment in the UIKit hosting path; FTTransfer-side improvements are secondary and not strictly required to reproduce the same visual behavior.
+- After the `ApolloGeneratedCode` removal, local compilation still succeeds for David; the Copilot-reported `ApexKitSwiftUI` blocker should be treated as environment-specific noise unless it becomes reproducible in the real local build.
+- No live production Apollo runtime references remain in `XFlowSDK/XFlowSDK`; the next cleanup surface is deferred test references plus any intentionally retained AppSync compatibility APIs.
 
 ---
 
@@ -44,6 +52,7 @@ updated: 2026-04-21
 - Identify the runtime Apollo files that can now be removed safely after the model and init cleanup.
 - Remove Apollo-only tests, mocks, codegen scripts, and build wiring once runtime references are gone.
 - Treat any transitive PicoSDK Apollo dependency as a separate dependency-exit step.
+- Continue cleanup by removing GraphQL/Apollo-era test references and related test-only helpers without changing production runtime behavior.
 
 ---