chore: align opencode memory docs with .memory project

.config/opencode/commands/save-memory.md

@@ -15,7 +15,8 @@ you noticed, or intent the user shared.
 
 Use `list_memory_projects` to find this repo's dedicated basic-memory project.
 If it doesn't exist, create one with `create_memory_project` using a short
-kebab-case name and the repo's root directory as `project_path`.
+kebab-case name and the repo's `.memory/` subdirectory as `project_path`
+(e.g., `/path/to/repo/.memory`).
 
 All project-specific notes must target `project="<repo-project-name>"`.
 Cross-project reusable knowledge must target `project="main"`.
@@ -68,7 +69,7 @@ Report what was added/updated, where, and in which project.
 
 If project `knowledge/` notes were **materially** updated (architecture, conventions,
 commands — not just plans/research), update `AGENTS.md` to reflect the changes.
-The symlinks automatically propagate to all tools.
+Keep repo instruction guidance in `AGENTS.md` only.
 
 If updates were only plans/research/tracking details, skip this step.
 
@@ -80,4 +81,4 @@ If updates were only plans/research/tracking details, skip this step.
 - Keep hierarchy shallow (max 2 heading levels preferred).
 - Be specific. "Handles auth" is weak. "JWT auth with RS256, validated in
   `src/middleware/auth.ts`, refresh tokens in Redis with 7d TTL" is useful.
-- Always pass the `project` parameter on every MCP call.
+- Always pass the `project` parameter on every MCP call.