feat: Enhance memory management and promotion rules for Mattermost context and user prompts

.opencode/commands/mattermost-sync.md

@@ -1,8 +1,8 @@
 ---
-description: Force a Mattermost sync using the configured local script
+description: Sync Mattermost context and automatically promote high-confidence project memory
 ---
 
-Use the configured Mattermost sync command to fetch fresh communication context into the inbox only.
+Use the configured Mattermost sync command to fetch fresh communication context and maintain workspace memory automatically.
 
 Preferred command sources:
 
@@ -16,14 +16,17 @@ Run the command and use its output as fresh communication context:
 Then:
 
 - if the command fails, stop there and do not edit any workspace files
-- if no `ai/inbox/mattermost-latest.md` exists after the sync attempt, do not update project memory
-- inspect `ai/inbox/mattermost-latest.md` if it exists
-- extract only project-relevant candidate facts
-- do not update `ai/logs/`, `ai/state/`, or `ai/context/` in this command
-- if important candidate facts are found, summarize them as promotion candidates for a later explicit command
+- use `ai/inbox/mattermost-latest.md` if it exists and is non-empty
+- otherwise use `scripts/mattermost/generated/mattermost_context.jsonl` if it exists and is non-empty
+- apply the memory promotion rules from `knowledge/memory-promotion-rules.md`
+- automatically promote explicit, project-relevant, high-confidence facts
+- default destination is `ai/logs/$(date +%F).md`
+- update `ai/state/current.md` only for facts that materially change the current work window
+- do not write tooling noise, sync status, or generic chat chatter into project memory
+- if a fact is ambiguous, skip it rather than asking the user what to do
 
 Return:
 
 1. What was synchronized
-2. Candidate project facts worth promoting
-3. What still needs human confirmation
+2. Which files were updated
+3. Which facts were promoted or intentionally skipped