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

feat: Update focus of PDIAP-15838 to GraphQL removal and LaunchDarkly toggle cleanup after confirming REST activation on iOS

Browse Source
This commit is contained in:
David Delagneau
2026-04-20 11:53:55 -06:00
parent a3bdf9c3ea
commit 8bfa29f78c
4 changed files with 22 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
project-knowledge/02-work-items/pdiap-15838.md
View File

@@ -20,7 +20,7 @@ tags:
## Status
- In Progress
- Current top priority within this story is investigating why REST is not activating on iOS
- Current top priority within this story is back to the GraphQL-removal / LaunchDarkly-toggle cleanup after Adam reported the latest build activating REST correctly
- Sized at `8` points
---
@@ -47,6 +47,10 @@ tags:
- Do not imply it is dependent on or part of dismissal-sequencing work.
- Keep the migration framing explicit: REST remains behind a feature flag until otherwise confirmed, and GraphQL fallback context still matters when describing the overall migration.
- Treat the REST-activation investigation as the immediate priority before resuming broader Apollo-removal cleanup.
- Jeff confirmed this investigation should stay ahead of Adam's separate service-side flow report for now and asked for faster progress.
- Current local evidence shows the LaunchDarkly boolean evaluating to `true`, with payload and context present from the iOS side; remaining uncertainty is around production-side context interpretation, timing/caching, or downstream transport gating.
- Use the current support path while direct Flagship LaunchDarkly access is missing: monitor the Tauf thread, follow the outreach path to 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.
- Jeff later relayed that Adam says the latest build is now activating REST correctly, so the story should shift back to the planned GraphQL-removal and related LaunchDarkly-toggle cleanup work.
---