david.delagneau/fidelity-ai-workspace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: update Mattermost rendering guidelines for standups and enhance daily logs with recent validation details

Browse Source
This commit is contained in:
David Delagneau
2026-05-13 07:44:30 -06:00
parent bc467c8a8c
commit 286adf2d6c
11 changed files with 83 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -8,7 +8,7 @@ systems: [xflowsdk]
workstreams: [rest-migration]
people: [jeff-dewitte, bruce-meeks, adam-abdelhadi, tauf, jeffrey-oleary, aylwing-olivas]
related: [launchdarkly, github-copilot]
updated: 2026-05-12
updated: 2026-05-13
tags:
- work-item
- fidelity
@@ -92,6 +92,7 @@ tags:
- Jeff confirmed May 11 that the REST back end has now been deployed, and a meeting is scheduled for May 12 with the team lead and Bruce to toggle the flag and test both REST and non-REST states.
- REST detection for the meeting: Charles Proxy to verify `/xflow/api` endpoints and inspect `mobile.launchdarkly.com` bulk payloads for the raw evaluated flag value.
- Production testing: Raj is trying to get approval to test in production. A production test account will be needed; currently only Bruce is known to have one. David found a way to force the production environment from the simulator if needed.
- May 12 REST validation nuance: pointing Fid4 at production through the plist by itself still showed GraphQL, but the fuller meeting result was successful iOS REST validation after Raj enabled the production LaunchDarkly toggle with specific targeting for the production test user's context, specifically the MID for the account tested with Bruce. Treat this as evidence that the production REST path can activate on iOS when the LD targeting context matches.
---