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