feat: Enhance Mattermost integration by adding sync commands and context checks for recent messages

.opencode/commands/latest-message.md

@@ -0,0 +1,40 @@
+---
+description: Force-sync Mattermost and answer from the latest matching message
+---
+
+Force-refresh Mattermost first, then answer the user's question from the refreshed inbox.
+
+Use this when the user asks for:
+
+- the latest or last message
+- what Jeff or another person just said
+- the latest Mattermost update
+- the latest message in `fidelity-preguntas`
+
+Run sync:
+
+!`if [ -n "$FIDELITY_MATTERMOST_SYNC_CMD" ]; then bash -lc "$FIDELITY_MATTERMOST_SYNC_CMD"; elif [ -f scripts/mattermost/sync.sh ]; then bash scripts/mattermost/sync.sh; else echo "No Mattermost sync command is configured."; fi`
+
+Read refreshed Mattermost context:
+
+!`if [ -s ai/inbox/mattermost-latest.md ]; then cat ai/inbox/mattermost-latest.md; elif [ -s scripts/mattermost/generated/mattermost_context.jsonl ]; then cat scripts/mattermost/generated/mattermost_context.jsonl; else echo "No Mattermost context available after sync."; fi`
+
+User request:
+
+$ARGUMENTS
+
+Instructions:
+
+- Do not answer from old conversation memory.
+- Use only the refreshed Mattermost output above.
+- If the user asks for Jeff/current manager, filter messages by `jeff`, `jeff.dewitte`, or the current manager profile when visible.
+- If multiple messages match, return the newest matching message first.
+- Include timestamp, channel, sender, and concise summary.
+- If the message changes project context, update the appropriate workspace memory after answering.
+- If sync fails or no refreshed context is available, say that directly and do not infer from stale context.
+
+Return:
+
+1. Latest matching message
+2. Why it matters
+3. Any memory update made