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

project-knowledge/01-current/current-work.md

@@ -18,7 +18,7 @@ tags:
 - Follow up on active tickets through `project-knowledge/02-work-items/`, especially `PDIAP-15838` and `PDIAP-15836`
 - `PDIAP-15765` is done and `PDIAP-14859` is also done
 - `PDIAP-15838` is now in progress
-- The current top priority is investigating why REST is not activating on iOS
+- The current top priority is back to `PDIAP-15838` implementation work for removing GraphQL and related LaunchDarkly toggles
 - `PDIAP-15836` comes after the current REST-investigation / Apollo-removal work
 - Keep the separate `HybridBrokerageAccountOpening` / `JointIdentityCheck` scenario out of `PDIAP-15765` scope unless later evidence proves it belongs there
 - Include feature-flag planning for the broader UIKit-removal spike, including dismissal sequencing changes that affect consumers
@@ -39,6 +39,9 @@ tags:
 - The `PDIAP-15765` compatibility fix is now fully closed out and the story is in Done
 - A new urgent consumer report says REST calls fail on iOS when the toggle is enabled, but current local validation says REST works on both `main` and `release/4.30`; treat version/flag mismatch as the leading explanation until broader evidence says otherwise
 - David has now confirmed the production build already contains the commit that added the LaunchDarkly flag, so the current investigation should focus more on LaunchDarkly evaluation context, targeting, initialization timing, and any additional transport-selection gating on iOS
+- Jeff explicitly wants the REST-flag investigation to stay ahead of Adam's separate service-side flow report for now and wants faster visible progress on that path
+- Jeff suggested broadening the investigation support path while direct Flagship LaunchDarkly access is still missing: monitor the Tauf thread, follow up with 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 David should switch back to the current Jira story work for removing GraphQL and related LaunchDarkly toggles
 - Before closing out the AO thread, send one more working-group Teams reply that summarizes the original iOS issue, links the Jira comment, Discourse comment, and PR, and separates the remaining `HybridBrokerageAccountOpening` / `JointIdentityCheck` service-side issue
 - The `HybridBrokerageAccountOpening` / `JointIdentityCheck` rule-content issue appears unchanged between QA and Production in Cogstore and should be treated as the remaining service-side follow-up
 
@@ -55,8 +58,10 @@ tags:
 - Keeping REST deprecation scope explicit while GraphQL fallback still exists
 - Current LaunchDarkly access does not include Flagship LD projects; only the sample app LD project is available from David's side
 - David does not yet know where the iOS app assembles or identifies the LaunchDarkly context attributes, but can inspect source code and use Charles Proxy during investigation
+- Current local evidence shows the LaunchDarkly boolean evaluating to `true`, with payload and context present from the iOS side, so the remaining uncertainty is around production-side context interpretation, timing, caching, or additional downstream gating
+- The urgent REST-activation investigation is no longer the immediate blocker after Adam reported the latest build working, but the earlier context/timing uncertainty remains useful background if the issue reappears
 - Defining a consumer rollout plan for UIKit-removal sequencing changes, including validation, communication, and feature-flag retirement
-- Investigating why REST is not activating on iOS before continuing broader REST-migration cleanup
+- Continue broader Apollo-removal / REST-migration cleanup now that the latest build is reportedly activating REST again
 - Avoiding assumptions when comparing iOS and Android validation behavior; scenario-specific parity needs to be confirmed before reporting scope
 - Avoiding assumptions about legacy Apex/ApexKit paths; breakpoint evidence and helper usage both need to be reconciled before reporting ownership or replacement guidance
 - When ownership is still uncertain under production pressure, prefer rollback-plus-investigation framing over confident blame assignment to consumers

project-knowledge/01-current/work-items.md

@@ -20,7 +20,7 @@ Update the per-ticket files first when scope, status, sequencing, or communicati
 
 - `PDIAP-15838` - Remove Apollo for iOS
   Detail: `project-knowledge/02-work-items/pdiap-15838.md`
-  Current note: now in progress; the immediate priority is investigating why REST is not activating on iOS, then continue the broader Apollo-removal / REST-migration work.
+  Current note: now in progress; Adam says the latest build is activating REST again, so the story focus should return to removing GraphQL and the related LaunchDarkly toggles.
 
 - `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
   Detail: `project-knowledge/02-work-items/pdiap-15836.md`