feat: Enhance project documentation with updates on REST migration, GitHub Copilot, and LaunchDarkly integration

project-knowledge/04-people/adam-abdelhadi.md

@@ -0,0 +1,41 @@
+---
+type: person
+project: fidelity
+role: consumer-side validator
+status: active
+teams: []
+topics: [rest-migration, launchdarkly, real-device-validation]
+related: [pdiap-15838, launchdarkly]
+tags:
+  - person
+  - fidelity
+updated: 2026-04-20
+---
+
+# Adam Abdelhadi
+
+## Role
+
+- Adam reported the iOS-side REST activation problem during the current `PDIAP-15838` investigation.
+- He or his team validate behavior on real devices.
+
+---
+
+## Collaboration Pattern
+
+- Jeff relayed Adam's report that REST was not activating for the affected build and later relayed Adam's update that the latest build was working.
+- Adam's reports are currently relevant as real-device validation input rather than as direct ownership proof for the root cause.
+
+---
+
+## Communication Notes
+
+- Treat Adam's observations as high-value consumer-side validation, especially when simulator and real-device behavior differ.
+- If future context clarifies his exact team or ownership boundary, update this file directly.
+
+---
+
+## Related Context
+
+- `project-knowledge/02-work-items/pdiap-15838.md`
+- `project-knowledge/03-context/systems/launchdarkly.md`

project-knowledge/04-people/aylwing-olivas.md

@@ -3,7 +3,7 @@ type: person
 project: fidelity
 role: collaborator
 status: active
-updated: 2026-04-16
+updated: 2026-04-20
 tags:
   - person
   - fidelity
@@ -31,4 +31,5 @@ Repeated Fidelity collaborator visible across multiple historical Slack channels
 
 - Treat Aylwing as a useful source for higher-level technical framing and dependency risk context
 - Treat Aylwing as a strong reviewer for architecture direction, refactor scope, and risk framing
+- Jeff explicitly suggested asking Aylwing for a quick perspective during the April 20, 2026 REST / LaunchDarkly investigation because of his broad cross-project experience
 - If future context clarifies the formal team or title, update this file directly

project-knowledge/04-people/index.md

@@ -53,6 +53,12 @@ tags:
 - [tauf.md](./tauf.md)
   Taufiqur Ashrafy, often referred to as Tauf; CI/Jenkins support contact who helps with release-pipeline troubleshooting and related publication issues.
 
+- [jeffrey-oleary.md](./jeffrey-oleary.md)
+  Fidelity-side support contact that Tauf redirected David to during the April 20, 2026 REST / LaunchDarkly investigation; exact team and ownership still need confirmation.
+
+- [adam-abdelhadi.md](./adam-abdelhadi.md)
+  Consumer-side validator who reported the REST activation problem during `PDIAP-15838`; he or his team test on real devices.
+
 ## Usage
 
 When a person appears repeatedly in project communication, create or update their file here so the agent can reuse:

project-knowledge/04-people/jeff-dewitte.md

@@ -74,3 +74,5 @@ Good updates usually clarify:
 - Use polished native-sounding English for external-facing comments; avoid sending rough wording when a cleaner version is easy to produce
 - When a consumer issue may actually belong to another team/framework, document the finding clearly and route ownership instead of carrying it indefinitely in XFlow
 - For cross-team status messages, make the sequence of events extremely explicit so the reader can tell what was the original issue, what changed, what XFlow changed, and what remains a separate service-side issue
+- When direct access is missing, Jeff may push for progress through adjacent evidence sources and support contacts instead of waiting on missing permissions
+- Jeff explicitly suggested using the Fidelity-approved AI tool with detailed local context, plus outreach to Aylwing / Tauf / Jeffrey O'Leary, during the April 20, 2026 REST / LaunchDarkly investigation

project-knowledge/04-people/jeffrey-oleary.md

@@ -0,0 +1,41 @@
+---
+type: person
+project: fidelity
+role: support contact
+status: active
+teams: []
+topics: [rest-migration, launchdarkly, build-debugging]
+related: [pdiap-15838, github-copilot]
+tags:
+  - person
+  - fidelity
+updated: 2026-04-20
+---
+
+# Jeffrey O'Leary
+
+## Role
+
+- Fidelity-side contact that Tauf redirected David to during the April 20, 2026 REST / LaunchDarkly investigation.
+- Exact team and formal ownership are still unknown.
+
+---
+
+## Collaboration Pattern
+
+- Jeff approved reaching out to Jeffrey after Tauf suggested he might be familiar with this type of issue.
+- Jeffrey is currently relevant as a possible support contact for build-specific or environment-specific behavior affecting REST activation on iOS.
+
+---
+
+## Communication Notes
+
+- Treat Jeffrey as a suggested escalation/support contact, not yet as a confirmed owner.
+- If future context clarifies his team, access level, or ownership boundary, update this file directly.
+
+---
+
+## Related Context
+
+- `project-knowledge/02-work-items/pdiap-15838.md`
+- `project-knowledge/03-context/systems/github-copilot.md`

project-knowledge/04-people/tauf.md

@@ -10,7 +10,7 @@ aliases: [Taufiqur Ashrafy, Tauf]
 tags:
   - person
   - fidelity
-updated: 2026-04-17
+updated: 2026-04-20
 ---
 
 # Taufiqur Ashrafy
@@ -35,6 +35,7 @@ updated: 2026-04-17
 - Often referred to informally as `Tauf`.
 - Fidelity Teams may show names in a surname-first style, so this person may appear under a different display order there.
 - In the current XFlowViewMaker propagation issue, Tauf clarified that the needed fix belongs in the podspec repo rather than FTFrameworks source, and pointed David toward removing the XFlowViewMaker version constraint for `ftaccountopen`.
+- During the April 20, 2026 REST / LaunchDarkly investigation, Tauf redirected David toward Jeffrey O'Leary as a better contact for that scenario.
 
 ---
 
@@ -42,3 +43,5 @@ updated: 2026-04-17
 
 - `project-knowledge/03-context/workstreams/consumer-integration.md`
 - `project-knowledge/02-work-items/pdiap-15765.md`
+- `project-knowledge/02-work-items/pdiap-15838.md`
+- `project-knowledge/04-people/jeffrey-oleary.md`