feat: Update people statuses and communication context for clarity and accuracy

vault/03-context/process/communication.md

@@ -30,6 +30,11 @@ When the format fits, prefer:
 - Always clarify authenticated vs non-authenticated when behavior depends on it.
 - Always separate external issues from regressions.
 - Always state reproducibility and scope.
+- Fidelity Teams consistently displays names in surname-first order.
+- Mattermost is a separate internal communication context; most people visible in Teams are not the same people David interacts with in Mattermost, with Jeff as the main exception.
+- Jeff is the main bridge into the Fidelity-side Teams context.
+- David works on the All-Win Software side and mainly helps advance the work Jeff needs to report on the Fidelity side.
+- Do not write updates as if David is directly embedded in the Fidelity Teams collaboration loop unless the context explicitly says so.
 - For standups, report the previous workday context, not blindly the prior calendar day.
 - On Mondays, use Friday's work context unless a later prior day has Mattermost activity.
 - If the previous calendar day has no project activity because of weekend, holiday, or OOO, use the latest prior day with Mattermost activity.