feat: Update Mattermost sync command to fetch context into inbox only and add promote project context command

ai/AGENTS.md

@@ -65,6 +65,10 @@ When drafting messages for Jeff:
 - If `ai/inbox/mattermost-latest.md` exists, check it before answering prompts about current status, standups, or supervisor communication
 - If a Mattermost sync or other context-ingestion step fails, do not update `ai/logs/`, `ai/state/`, or stable context files based on that failure
 - Do not record missing dependencies, failed sync attempts, or missing inbox files as project facts unless the user explicitly asks to track the operational issue
+- Treat `mattermost-sync` as inbox refresh only. Do not automatically promote synced content into project memory
+- Promote Mattermost content only when it is clearly project-relevant, confirmed enough to keep, and the user explicitly asks to sync or promote project context
+- Prefer updating stable project context over appending generic operational summaries
+- Do not create daily log entries for tooling activity, sync status, or generic chat noise
 - When the user shares relevant new information, update today's log if the information belongs to the daily record
 - When the user corrects or changes stable context, update the canonical file directly:
   - `ai/state/current.md` for current focus or active concerns
@@ -82,7 +86,7 @@ For day-to-day prompts in this workspace:
 
 1. Verify the latest relevant context.
 2. Decide whether the prompt introduces new durable information.
-3. Update the workspace when needed, but never from a failed sync or failed tool run.
+3. Update the workspace when needed, but never from a failed sync or failed tool run, and never auto-promote Mattermost sync results.
 4. Then answer using the refreshed context.
 
 ---