fidelity-ai-workspace/project-knowledge/06-daily/2026-04-21.md

type, project, date, status, focus, work-items, blockers, tags, updated

type	project	date	status	focus	work-items	blockers	tags	updated
daily	fidelity	2026-04-21	active	rest-migration xflow-swiftui-migration	pdiap-15838 pdiap-15836		daily fidelity	2026-04-21

2026-04-21

Focus

• Continue PDIAP-15838 Apollo-removal cleanup.

---

Work Done

• 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.

---

Findings

• The model-decoupling step for PDIAP-15838 is now in a cleaner state.
• The next focus should shift to the remaining Apollo-dependent runtime and infrastructure surface: init/session coupling through NetworkClient, Apollo-generated/runtime code that is no longer needed, and Apollo-specific tests/scripts/build wiring.
• 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.

---

Next Steps

• Confirm whether NetworkClient.swift still has any live production callers or can now be treated as removable runtime dead code.
• Confirm whether XFlowInitManagerConfig.swift AppSync getters are truly compatibility-only or still externally used.
• 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.

---

Blockers

• None currently.