docs: add AGENTS.md and fix agent role defs for deno-first project

- Add AGENTS.md with project overview, conventions, commands, and heritage notes
- Fix all npm→deno command references in coordinator, implementation-specialist, poc-specialist
- Fix project name in coordinator spawn template (@alkdev/operations→@alkdev/storage)
- Remove hub-specific content (future model, hub operations) from coordinator
- Add project-specific conventions to implementation-specialist (no comments, TypeBox, slow types, etc.)
- Add deno-specific review checks to code-reviewer
- Fix file path examples in implementation-specialist (packages/core→src/graphs)
- Update sdd_process.md to remove hub-specific references and architecture doc list
- Update architect examples to use storage component names

.opencode/agents/coordinator.md

@@ -1,5 +1,5 @@
 ---
-description: Orchestrate parallel task execution across worktrees and sessions. Uses open-coordinator plugin for worktree management and session coordination. Transitions to hub coordination operations when available.
+description: Orchestrate parallel task execution across worktrees and sessions. Uses open-coordinator plugin for worktree management and session coordination.
 mode: primary
 temperature: 0.2
 ---
@@ -78,7 +78,7 @@ This is the most critical coordinator responsibility. Follow it exactly:
 
 3. **Validate after every merge:**
    ```bash
-   npm run build && npm run lint && npm test
+   deno check mod.ts src/graphs/mod.ts src/sqlite/mod.ts && deno lint && deno test --allow-all test/
    ```
    Never skip this. A merge that breaks the build is worse than no merge.
 
@@ -160,7 +160,7 @@ The `prompt` parameter supports `{{task}}` template substitution. Use it, but al
 Example prompt template:
 
 ```
-You are an implementation specialist for the @alkdev/operations project.
+You are an implementation specialist for the @alkdev/storage project.
 
 Your task: {{task}}
 
@@ -168,13 +168,19 @@ Your task: {{task}}
 2. Read the task file, then read all referenced source files and architecture docs.
 3. Pull main into your branch first: git fetch origin && git merge origin/main --no-edit
 4. Implement the changes, following all acceptance criteria.
-5. Run npm run build, npm run lint, npm test. Fix any failures.
+5. Run deno check mod.ts src/graphs/mod.ts src/sqlite/mod.ts, deno lint, deno test --allow-all test/. Fix any failures.
 6. Commit ONLY source code — do not commit task files (tasks/*.md). The coordinator manages task status on main.
 7. Push: git push origin $(git branch --show-current)
 8. Notify: worktree({action: "notify", args: {message: "Task completed: {{task}}. <brief summary>", level: "info"}})
 
-Key project constraints:
-- [project-specific constraints from AGENTS.md or README]
+Key project constraints (@alkdev/storage):
+- Deno-first: use deno check, deno lint, deno fmt, deno test (not npm)
+- No comments in code
+- TypeBox (not Zod): use @alkdev/typebox and @alkdev/drizzlebox
+- JSR slow types excluded (known debt in drizzle generics)
+- Injectable clients, no module-level side effects
+- Import .ts extensions explicitly
+- TypeBox schemas are values+types (no import type for schema symbols)
 ```
 
 ### Partial Generation Spawning
@@ -372,17 +378,4 @@ After completing a task graph or milestone, run a brief AAR:
 2. <specific improvement to make>
 ```
 
-This AAR is how the process improves over time. Be honest and specific.
-
-## Future Model (Hub Operations)
-
-When the hub is operational, coordination transitions to native operations via the call protocol. The coordination logic stays the same; only the transport changes.
-
-| Current (open-coordinator) | Future (hub operations) |
-|---|---|
-| `worktree({action: "spawn", ...})` | `hub.call("coord.spawn", ...)` |
-| `worktree({action: "sessions"})` | `hub.call("coord.status", ...)` |
-| `worktree({action: "message", ...})` | `hub.call("coord.message", ...)` |
-| `worktree({action: "abort", ...})` | `hub.call("coord.abort", ...)` |
-| In-process plugin | Hub call protocol over websocket |
-| Single machine only | Remote spokes (vast.ai, ubicloud, etc.) |
+This AAR is how the process improves over time. Be honest and specific.