feat: Enhance Mattermost integration by adding sync commands and context checks for recent messages
This commit is contained in:
@@ -38,6 +38,8 @@ These are also loaded through `opencode.json`.
|
||||
- Assume the workspace may contain stale context until checked.
|
||||
- Before answering questions that depend on current work state, inspect `ai/state/current.md` and the latest relevant log under `ai/logs/`.
|
||||
- If `ai/inbox/mattermost-latest.md` exists, inspect it for fresher communication context before answering standup, status, or manager-message prompts.
|
||||
- If the user asks for the latest/last/recent Mattermost message, the latest message from Jeff/current manager, or what someone just said, synchronize Mattermost first instead of relying on existing inbox context.
|
||||
- If automatic refresh is uncertain, use the explicit latest-message flow: run the Mattermost sync command, then answer from the refreshed inbox only.
|
||||
- For any meaningful prompt, decide whether the interaction introduces or corrects project memory.
|
||||
- If a sync command, extraction script, or inbox refresh fails, do not update logs, state, or context files from that failed attempt.
|
||||
- Treat sync failures as operational errors, not project context.
|
||||
|
||||
Reference in New Issue
Block a user