feat: Update documentation and clarify communication guidelines for AO and Youth issues

ai/context/people/jeff-dewitte.md

@@ -46,6 +46,7 @@ Good updates usually clarify:
 - Jeff approvals can change what belongs in current state or work-item memory
 - Jeff feedback is often a signal to tighten wording before communicating externally
 - Jeff often asks for evidence, reproduction detail, and exact next action before approving external communication
+- If a draft is still ambiguous, Jeff may prefer to rewrite it directly so the external version is unambiguous and does not generate avoidable follow-up
 
 ---
 
@@ -60,3 +61,4 @@ Good updates usually clarify:
 - Prefer evidence-heavy communication: screenshots, videos, exact error text, branch/version, and direct comparisons to main/web/UIKit/Fid4 when relevant
 - 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