feat: Update standup guidelines for clarity and audience accessibility

vault/03-context/process/communication.md

@@ -2,7 +2,7 @@
 type: process
 project: fidelity
 status: active
-updated: 2026-04-16
+updated: 2026-04-17
 tags:
   - process
   - fidelity
@@ -35,6 +35,8 @@ When the format fits, prefer:
 - If the previous calendar day has no project activity because of weekend, holiday, or OOO, use the latest prior day with Mattermost activity.
 - For standups, when a Jira item has multiple concrete updates, use one top-level `JIRA-ID - Title` bullet and indented markdown sub-bullets instead of repeating the same Jira line.
 - When a flow/page shorthand could be ambiguous, prefer the real flow identifier and page name from `vault/03-context/workstreams/flow-page-references.md`.
+- For standups that may also be sent to Teams, prefer plain audience-friendly wording over internal implementation shorthand; avoid terms like `fallback` unless the audience already has the necessary context.
+- When a release is waiting on approvals or pipeline movement, make the concurrent work explicit so the update does not imply idle waiting.
 - Avoid vague phrasing such as:
   - "same behavior"
   - "looks fixed"