refactor: update agent sync behavior, improve freshness detection patterns, and add diagnostic troubleshooting script

prompts/standup.md

@@ -4,6 +4,21 @@ Use `project-knowledge/01-current/current-work.md`, `project-knowledge/01-curren
 
 Generate a standup update for the active project profile.
 
+## Required refresh
+
+- At the start of the day, fetch Mattermost before drafting.
+- Fetch both latest available messages and previous-workday activity when the connector supports both modes.
+- If Mattermost refresh fails, say so internally and use only saved workspace memory with clear caution; do not invent fresher context.
+- Do not skip communication refresh for standup just to reduce latency, because stale standups cost more time to correct later.
+
+## Temporal grounding
+
+- Use the injected `Temporal Context` block as the source of truth for today's date, weekday, calendar yesterday, and default previous workday.
+- Resolve relative terms before drafting: `today` means the injected `today`; `yesterday` means the injected `calendar_yesterday`; `previous workday` means the injected `default_previous_workday` unless refreshed Mattermost evidence found a later prior day with activity.
+- For a Tuesday report, the previous-work section normally describes Monday's work.
+- Do not infer dates from model memory, conversation history, or file modification times when the injected temporal context is available.
+- If a requested report date conflicts with the injected current date, state the exact date being used before drafting.
+
 ## Output contract
 
 - Use the greeting required by the active profile or command. If no greeting is specified, omit the greeting and start with the previous-work section.