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

project-knowledge/03-context/systems/github-copilot.md

@@ -0,0 +1,47 @@
+---
+type: system
+project: fidelity
+status: active
+systems: []
+workstreams: []
+people: [jeff-dewitte]
+related: []
+tags:
+  - system
+  - fidelity
+updated: 2026-04-20
+---
+
+# GitHub Copilot
+
+## Role
+
+- GitHub Copilot is a broadly used AI tool in the Fidelity workflow, especially when product-side code access and richer implementation context are available on the Fidelity machine.
+
+---
+
+## Stable Patterns
+
+- Use this tool when the local Fidelity-side product context is richer than what can be summarized indirectly in chat.
+- It is useful for investigation, code-oriented debugging, and implementation support when David can provide concrete build, file, and runtime details from the Fidelity development environment.
+- Tool output should still be checked against local evidence, reproduction results, and confirmed project context.
+
+---
+
+## Current Example
+
+- During the April 20, 2026 REST / LaunchDarkly investigation, Jeff specifically suggested using GitHub Copilot with more detailed local context from David's side.
+
+---
+
+## Risks
+
+- Do not assume the tool output is authoritative without checking it against local evidence.
+- Keep the tool's Fidelity-side access level and data visibility labeled as contextual rather than assumed workspace-wide.
+
+---
+
+## Related Context
+
+- `project-knowledge/04-people/jeff-dewitte.md`
+- `project-knowledge/02-work-items/pdiap-15838.md`

project-knowledge/03-context/systems/index.md

@@ -81,6 +81,12 @@ tags:
 - [nexus-fidelity.md](./nexus-fidelity.md)
   Internal Fidelity tool identified from the current bookmark/tool set.
 
+- [launchdarkly.md](./launchdarkly.md)
+  Feature-flag platform used broadly across the Fidelity workflow for rollout and environment-controlled behavior.
+
+- [github-copilot.md](./github-copilot.md)
+  Fidelity-side AI tool used broadly when richer product-side context is available on the development machine.
+
 ---
 
 ## Guidance

project-knowledge/03-context/systems/launchdarkly.md

@@ -0,0 +1,47 @@
+---
+type: system
+project: fidelity
+status: active
+systems: []
+workstreams: []
+people: []
+related: []
+tags:
+  - system
+  - fidelity
+updated: 2026-04-20
+---
+
+# LaunchDarkly
+
+## Role
+
+- LaunchDarkly is the feature-flag platform used broadly in the Fidelity workflow.
+- It is part of the normal delivery path for controlled rollout, environment-specific behavior, and gradual activation of changes.
+
+---
+
+## Stable Patterns
+
+- LaunchDarkly can affect behavior by environment, context, targeting, timing, and cached flag state.
+- When a bug appears only on certain builds or devices, LaunchDarkly evaluation is a valid investigation path even if local simulator checks look correct.
+- Missing direct dashboard access does not remove LaunchDarkly from consideration; code-side evidence, payload inspection, and runtime evaluation still matter.
+
+---
+
+## Current Example
+
+- During the April 20, 2026 REST migration investigation, LaunchDarkly was a central part of the debugging path because the behavior differed between local validation and consumer real-device reports.
+
+---
+
+## Risks
+
+- Do not assume a simulator result fully represents real-device LaunchDarkly behavior.
+- Do not treat missing direct Flagship dashboard access as proof that LaunchDarkly is not involved; indirect evidence still matters.
+
+---
+
+## Related Context
+
+- `project-knowledge/02-work-items/pdiap-15838.md`