feat: add comprehensive agent rules and workflows for memory curation, communication synchronization, and project documentation management

.agents/workflows/communication-sync.md

@@ -0,0 +1,47 @@
+---
+description: Sync live communication context and promote high-confidence memory
+---
+
+Use the configured live communication connector to fetch fresh evidence and maintain workspace memory automatically.
+
+Preferred command sources:
+
+- `AIW_MATTERMOST_SYNC_CMD`
+- Fidelity profile alias: `FIDELITY_MATTERMOST_SYNC_CMD`
+- workspace fallback: `bash scripts/mattermost/sync.sh`
+
+Run the connector:
+
+!`if [ -n "$AIW_MATTERMOST_SYNC_CMD" ]; then bash -lc "$AIW_MATTERMOST_SYNC_CMD"; elif [ -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 live communication sync command is configured."; fi`
+
+Read:
+
+@core/README.md
+@core/memory/operational-memory.md
+@core/integrations/communication-model.md
+@project-knowledge/01-current/current-work.md
+@project-knowledge/01-current/work-items.md
+@project-knowledge/03-context/project.md
+@agent-memory/memory/context-maintenance.md
+
+Fresh communication evidence:
+
+!`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 communication evidence available."; fi`
+
+Instructions:
+
+- if the sync command failed, stop and do not edit workspace memory
+- treat connector output as evidence, not automatically as project truth
+- promote only explicit, project-relevant, high-confidence facts
+- default destination is `project-knowledge/06-daily/$(date +%F).md`
+- update `project-knowledge/01-current/current-work.md` only for facts that materially change the active work window
+- update `project-knowledge/02-work-items/*.md` for explicit work-item IDs, approved titles, points, scope, and status notes
+- keep `project-knowledge/01-current/work-items.md` aligned as the compact summary of active work items
+- do not write tooling noise, sync status, or generic chat chatter into project memory
+- if a fact is ambiguous, skip it rather than asking what to do
+
+Return:
+
+1. What was synchronized
+2. Which files were updated
+3. Which facts were promoted or intentionally skipped