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

9
project-knowledge/01-current/current-work.md
View File

@@ -18,7 +18,7 @@ tags:
- Follow up on active tickets through `project-knowledge/02-work-items/`, especially `PDIAP-15838` and `PDIAP-15836` - 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-15765` is done and `PDIAP-14859` is also done
- `PDIAP-15838` is now in progress - `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 - `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 - 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 - 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 - 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 - 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 - 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 - 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 - 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 - 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 - 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 - 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 - 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 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 - 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 - When ownership is still uncertain under production pressure, prefer rollback-plus-investigation framing over confident blame assignment to consumers

2
project-knowledge/01-current/work-items.md
View File

@@ -20,7 +20,7 @@ Update the per-ticket files first when scope, status, sequencing, or communicati
- `PDIAP-15838` - Remove Apollo for iOS - `PDIAP-15838` - Remove Apollo for iOS
Detail: `project-knowledge/02-work-items/pdiap-15838.md` 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 - `PDIAP-15836` - Modernize dismissal delegate lifecycle sequencing for pure SwiftUI environment
Detail: `project-knowledge/02-work-items/pdiap-15836.md` Detail: `project-knowledge/02-work-items/pdiap-15836.md`

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

@@ -20,7 +20,7 @@ tags:
## Status ## Status
- In Progress - 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 - Sized at `8` points
--- ---
@@ -47,6 +47,10 @@ tags:
- Do not imply it is dependent on or part of dismissal-sequencing work. - 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. - 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. - 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.
--- ---

10
project-knowledge/06-daily/2026-04-20.md
View File

@@ -35,6 +35,12 @@ updated: 2026-04-20
- The immediate priority is to investigate why REST is not activating. - The immediate priority is to investigate why REST is not activating.
- David confirmed the production build already contains the commit that added the LaunchDarkly flag, so the working hypothesis should move away from "missing code in production build" and toward LaunchDarkly evaluation context, targeting, initialization timing, or downstream gating conditions. - David confirmed the production build already contains the commit that added the LaunchDarkly flag, so the working hypothesis should move away from "missing code in production build" and toward LaunchDarkly evaluation context, targeting, initialization timing, or downstream gating conditions.
- David has source-code access and can use Charles Proxy during local investigation, but does not yet know where the LaunchDarkly context attributes are assembled on iOS. - David has source-code access and can use Charles Proxy during local investigation, but does not yet know where the LaunchDarkly context attributes are assembled on iOS.
- Jeff explicitly confirmed the REST-flag investigation should remain the priority over Adam's separate service-side flow issue.
- Jeff wants faster progress on the REST-flag investigation and asked David to keep him updated while continuing the current research.
- Jeff suggested using outside help while the direct Flagship LaunchDarkly access gap remains: monitor the Tauf thread, follow the redirect to Jeffrey O'Leary, describe the issue in detail to the AI tool with build settings and tool details, and ask Aylwing for a quick sanity check if available.
- Current local evidence says the LaunchDarkly boolean evaluates to `true`, the payload is present, and the context is being sent; the remaining questionable area is whether the production-side context or timing is still affecting real-device behavior.
- Jeff later relayed that Adam says the latest build is now activating REST correctly, so the urgent production-toggle investigation is no longer the immediate focus.
- Jeff directed David to switch back to the current Jira story work for removing GraphQL and related LaunchDarkly toggles.
- David clarified additional Fidelity-side process context: Quy acts as Scrum Master, manages retrospectives, DSE/daily syncs, sprint review, and sprint planning, retrospectives use Miro, Jira is the tracking system, and the Fidelity-side sprint cadence is two weeks with labels like `PDIAP 26Q1.1` and `PDIAP 26Q2.1`. - David clarified additional Fidelity-side process context: Quy acts as Scrum Master, manages retrospectives, DSE/daily syncs, sprint review, and sprint planning, retrospectives use Miro, Jira is the tracking system, and the Fidelity-side sprint cadence is two weeks with labels like `PDIAP 26Q1.1` and `PDIAP 26Q2.1`.
- David corrected the Q2 sprint examples: `PDIAP 26Q2.1` is `3/26 - 4/09`, and `PDIAP 26Q2.2` is `4/09 - 4/23`. - David corrected the Q2 sprint examples: `PDIAP 26Q2.1` is `3/26 - 4/09`, and `PDIAP 26Q2.2` is `4/09 - 4/23`.
- David clarified that Jira should be represented as a first-class Fidelity tool/system because it is used more heavily than Confluence in day-to-day work tracking. - David clarified that Jira should be represented as a first-class Fidelity tool/system because it is used more heavily than Confluence in day-to-day work tracking.
@@ -51,7 +57,9 @@ updated: 2026-04-20
- Investigate why REST is not activating on iOS. - Investigate why REST is not activating on iOS.
- Inspect where iOS builds and identifies the LaunchDarkly context so local logs and Charles captures can confirm which attributes are actually sent. - Inspect where iOS builds and identifies the LaunchDarkly context so local logs and Charles captures can confirm which attributes are actually sent.
- Continue `PDIAP-15838` from that investigation path. - Package the current reproduction details for the AI tool, including build settings and the external tool being used.
- Keep watching the outreach thread with Tauf / Jeffrey O'Leary and ask Aylwing for a quick perspective if he is available.
- Resume `PDIAP-15838` implementation work for removing GraphQL and related LaunchDarkly toggles.
--- ---