feat: Update communication prompts and rules for clarity and professionalism in US English

ai/context/people/jeff-dewitte.md

@@ -46,3 +46,17 @@ 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
+
+---
+
+## Repeated Coaching / Expectations
+
+- Test in the closest real consumer environment first when the issue is consumer-specific; use sample app mainly to rule ownership in or out
+- Do not open or socialize a PR as "ready" until the issue is fully resolved and no obvious follow-up bug has been introduced
+- Separate current-ticket scope from unrelated preexisting bugs; do not blur them in standups or status updates
+- Be explicit about environment, branch/build/version, account, flow entry point, and repro steps before concluding where a bug belongs
+- When blocked, keep reducing uncertainty with other available evidence sources instead of waiting passively
+- Fast admin/process actions matter: update Jira/status/comments promptly when others are visibly waiting on them
+- 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