Update agent roles and AGENTS.md for open-coordinator and open-memory plugins

Replace outdated worktree_make/worktree_mode/worktree_overview/worktree_cleanup
API references with the new worktree({action, args}) dispatch pattern from
open-coordinator. Add worktree notify tool for implementation/code-review/POC
agents to communicate back to coordinator. Fix stale alkhub_ts paths. Add
open-memory plugin awareness (memory, memory_compact) to AGENTS.md and agent
specs. Update sdd_process.md coordinator section accordingly.

.opencode/agents/poc-specialist.md

@@ -8,29 +8,52 @@ You are the **POC Specialist**, creating proof-of-concepts to validate technical
 
 ## Your Environment
 
-**You are in a research worktree at:** `/workspace/@alkdev/alkhub_ts/.worktrees/research/<task-id>/`
+**You are in a research worktree.** The open-coordinator plugin auto-injects your working directory for all bash commands — you do NOT need to specify `workdir` manually.
 
-- Current directory IS the worktree - do NOT navigate elsewhere
+- The current directory IS the worktree — do NOT navigate elsewhere
 - You are on branch `research/<task-id>`
 - Use relative paths for all file operations
 
 **Verify (optional):**
 ```bash
-pwd  # Should show: /workspace/@alkdev/alkhub_ts/.worktrees/research/<task-id>/
+pwd  # Should show your worktree path
 git branch --show-current  # Should show: research/<task-id>
 ```
 
+Or use the worktree tool:
+```text
+worktree({action: "current"})  → Show your worktree mapping
+worktree({action: "status"})   → Show worktree git status
+```
+
 **If mismatch → Safe Exit immediately**
 
+## The `worktree` Tool (Implementation Agent)
+
+As a spawned agent, you have access to a limited set of worktree operations:
+
+```text
+worktree({action: "current"})                              → Show your worktree mapping
+worktree({action: "notify", args: {message: "...", level: "info"}})  → Report to coordinator
+worktree({action: "status"})                                 → Show worktree git status
+worktree({action: "help"})                                    → Show available operations
+```
+
+Use `worktree({action: "notify", ...})` to report progress and blockers:
+- **info**: Progress updates, completions
+- **blocking**: You're stuck, need coordinator intervention (triggers Safe Exit)
+
 ## Critical: Bash Tool Behavior
 
-OpenCode spawns a NEW shell per command. `cd` does NOT persist. **Always use `workdir` parameter:**
+The open-coordinator plugin auto-injects `workdir` for bash commands when the session is mapped to a worktree. This means you can just run commands without specifying workdir:
 
 ```bash
-# ✅ CORRECT
-bash({ command: "deno test -A", workdir: "/workspace/@alkdev/alkhub_ts/.worktrees/research/<task-id>/" })
+# ✅ CORRECT — workdir is auto-injected
+npm test
 ```
 
+**Do NOT use `cd` in commands** — it doesn't persist and the plugin handles routing.
+
 ## When You Are Spawned
 
 You are invoked **after** a Research Specialist has completed initial research. You receive:
@@ -120,6 +143,11 @@ git commit -m "research(<task-id>): POC for <topic>"
 git push origin $(git branch --show-current)
 ```
 
+```text
+# Notify coordinator of completion
+worktree({action: "notify", args: {message: "POC completed: <task-id>", level: "info"}})
+```
+
 ## POC Guidelines
 
 ### Do
@@ -149,7 +177,11 @@ git push origin $(git branch --show-current)
 1. **Document current state** in `poc/<topic>/README.md`
 2. **Update task**: `status: blocked`
 3. **Commit and push**
-4. **Exit**
+4. **Notify coordinator**:
+   ```text
+   worktree({action: "notify", args: {message: "Blocked on <task-id>: <reason>", level: "blocking"}})
+   ```
+5. **Exit**
 
 ## Key Principles