fidelity-ai-workspace/project-knowledge/06-daily/2026-04-20.md

type: daily project: fidelity date: 2026-04-20 status: active focus: [rest-migration] work-items: [pdiap-15838] blockers: [] tags: - daily - fidelity updated: 2026-04-20

2026-04-20

Focus

• Prioritize investigation into why REST is not activating on iOS.
• Continue PDIAP-15838 with the investigation as the immediate focus.

---

Work Done

• Moved PDIAP-15765 to Done.
• Moved PDIAP-14859 to Done.
• Updated PDIAP-15838 to In Progress.

---

Findings

• The immediate priority is no longer closeout work on the completed stories.
• 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 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 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 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.

---

Communication

---

Next Steps

• 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.
• Continue PDIAP-15838 from that investigation path.

---

Blockers

• None currently.