feat: Obsidian integration via cli scripts

core/profiles/create-project-profile.md

@@ -58,6 +58,8 @@ Use generic variables first:
 
 ```text
 AIW_PROJECT_PROFILE=<project>
+AIW_MEMORY_VAULT_DIR=<optional custom vault path>
+AIW_MEMORY_BACKEND=auto
 AIW_CHANNEL_PREFIX=<project-or-team-prefix>
 AIW_MATTERMOST_SYNC_CMD=<optional custom command>
 AIW_SLACK_EXPORT_PATH=<optional archive path>
@@ -72,6 +74,8 @@ Connector secrets belong in ignored `.env` files, not in profile files.
 Start with generic commands:
 
 - `/workspace-context`
+- `/memory-health`
+- `/memory-create`
 - `/communication-sync`
 - `/archive-import`
 - `/standup`
@@ -92,6 +96,7 @@ Before using the workspace for real work:
 - run a communication sync with test channels or a dry sample
 - generate one standup from sample context
 - verify that imported evidence and promoted memory stay separate
+- run `bash scripts/memory/memory.sh health`
 
 ---
 
@@ -99,6 +104,8 @@ Before using the workspace for real work:
 
 Open `vault/` as the Obsidian vault.
 
+Use `scripts/memory/` as the project-agnostic memory interface. Obsidian is the default visual and CLI-backed adapter, but profile logic should not depend on Obsidian.
+
 Recommended rules:
 
 - keep `vault/` as the clean canonical human/AI memory