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

feat: Update standup prompt and daily log to enhance clarity and communication guidelines for Apollo removal progress

Browse Source
This commit is contained in:
David Delagneau
2026-04-27 07:43:47 -06:00
parent e5d41c876e
commit e19a10f588
4 changed files with 34 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
project-knowledge/06-daily/2026-04-21.md
View File

@@ -17,6 +17,8 @@ updated: 2026-04-21
## Focus
- Continue `PDIAP-15838` Apollo-removal cleanup.
- Continue validating the Apollo-removal state.
- If time allows, publish new XFlow and XFlowViewMaker versions.
---
@@ -39,6 +41,7 @@ updated: 2026-04-21
- 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 latest cleanup pass also removed the remaining direct Apollo package/build references, so the story is now in a cleaner post-removal state and ready for consumer-side validation from Fid4.
- 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.
@@ -53,6 +56,8 @@ updated: 2026-04-21
- 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.
- Continue validating the Apollo-removal state today.
- If time allows, publish new XFlow and XFlowViewMaker versions.
---