feat: add mem9 integration documentation, enhance AI-to-AI prompting guidelines, and create daily logs for May 1 and May 7

project-knowledge/01-current/current-work.md

@@ -103,6 +103,7 @@ tags:
 - For standups that may also be sent to Teams, keep the update concise, omit internal review-feedback details, and avoid phrasing like `confirmed` when the audience lacks the internal context for what was confirmed
 - When a release item is waiting on approvals or pipeline work, make the parallel story work explicit instead of making the update sound blocked on waiting alone
 - Standups should omit side questions or manager-only context refreshes unless they materially changed story work
+- For `PDIAP-16167` standups after May 1, do not report story creation as previous-day work unless the previous-workday evidence explicitly says the story was created that day; focus on report publication, findings shared, closure, or remaining follow-up instead
 - For `PDIAP-15838` standups, focus on Apollo-removal progress and the `PicoSDK` transitive dependency work; omit extra exploratory asks unless they directly changed the story outcome or created a blocker
 - If a root cause document or other documentation update directly supports a story, it should be reported under that story instead of as a separate standalone item
 - Standups should omit items not tied to a story unless they are real blockers

project-knowledge/02-work-items/IA improvements.md

@@ -0,0 +1,17 @@
+- Experiment-driven investigation
+	- Debug print auto added
+		- Iteratively detect now possible debug prints
+	- Structured ticket artifacts with jira, patch, prompts, sessions
+	- Tolerant to pre-experiment fix steps to fix any build error between experiments
+	- Swift skill, specialized to debug prints
+- Xcode logs analysis
+	- Find and read the full Xcode artifacts
+	- Extract relevant logs
+- Xcode Integration
+	- Efficient use of xcode commands to build, test, contexted for tuist, cocoapods, sample projects
+	- Execute unit test proficiently, like executing only new tests or related
+- Investigation: Differences from skills with cli commands vs mcps
+- Investigation: Differences of skills vs instructions from vscode copilot
+- Investigation: Differences from agents vs skills using agent, what is more general? correct relationship and use
+- Charles Proxy integration
+- LaunchDarkly integration

project-knowledge/06-daily/2026-05-01.md

@@ -22,7 +22,6 @@ updated: 2026-05-04
 
 ## Work Done
 
-- Created `PDIAP-16167 - AccountLink - XFlow causing web view rewrites investigation`.
 - Prepared the root-cause report for the FTTransfer AccountLink issue.
 - Verified that XFlow eventing does not appear to be the direct cause of the reload.
 - Verified that the issue persists when rolling back `XFlowSDK` to `v0.1.0`, which predates REST and modern architecture changes.

project-knowledge/06-daily/2026-05-07.md

@@ -0,0 +1,19 @@
+---
+type: daily
+project: fidelity
+date: 2026-05-07
+updated: 2026-05-07
+focus: [pdiap-15836, pdiap-12284, rest-validation]
+work-items: [PDIAP-15836, PDIAP-12284]
+blockers: [production-test-account]
+tags:
+  - daily
+  - fidelity
+---
+
+# 2026-05-07
+
+## Notes
+
+- Clarified REST validation context: forcing Fid4 production endpoints by editing `initializeAppEnvironment` is related to validating REST enablement, not to the Apollo-removal story. It was a point-in-time ask that may still be useful later, but the immediate need is access to a production test account to complete validation.
+- Clarified `PDIAP-15836` status: the dismissal approach David tested appears coupled to the `UIHostingController` removal path, but there may be a strategy to isolate the fix. David will investigate whether the lifecycle/dismissal fix can be applied independently.