Refactor Mattermost and Slack integration workflows to remove legacy Fidelity variables, streamline command execution, and enhance documentation for project profiles. Update scripts and README files to reflect changes in directory structure and configuration precedence, ensuring a consistent approach to project knowledge management across profiles. Improve error handling and validation in profile creation and doctor commands, and enhance test coverage for profile-related functionalities.

.agents/workflows/communication-sync.md

@@ -7,12 +7,11 @@ Use the configured live communication connector to fetch fresh evidence and main
 Preferred command sources:
 
 - `AIW_MATTERMOST_SYNC_CMD`
-- Fidelity profile alias: `FIDELITY_MATTERMOST_SYNC_CMD`
-- workspace fallback: `bash scripts/mattermost/sync.sh`
+- Built-in wrapper: `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`
+!`if [ -n "$AIW_MATTERMOST_SYNC_CMD" ]; then bash -lc "$AIW_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:
 
@@ -31,7 +30,7 @@ Fresh communication evidence:
 Instructions:
 
 - if the sync command failed, stop and do not edit workspace memory
-- prefer local proxy mirror evidence when present; legacy sync output is fallback evidence
+- prefer local proxy mirror evidence when present; use the configured sync wrapper only when a fresh API pull is required
 - treat connector output as evidence, not automatically as project truth
 - promote only explicit, project-relevant, high-confidence facts
 - default destination is `workspaces/fidelity/project-knowledge/06-daily/$(date +%F).md`