refactor(common): extract resolve_data_dir helper from get_db_path

.agentd/agents/architect.yml

@@ -1,3 +1,5 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/geoffjay/agentd/main/schemas/agent.yml
+
 # Architect agent — cross-service design review and ADR authoring.
 #
 # Reviews PRs labeled "architecture" for cross-crate design concerns, authors
@@ -16,6 +18,31 @@ shell: /bin/zsh
 worktree: false
 model: claude-opus-4-6
 
+# Tool policy: codebase read access + tools for applying triage results
+tool_policy:
+  mode: allow_list
+  tools:
+    - Read
+    - Grep
+    - Glob
+    - WebFetch
+    - "Bash(agent memory *)"
+    - "Bash(gh pr *)"
+    - "Bash(grep *)"
+    - "Bash(ls *)"
+    - "Bash(diff *)"
+    - "Bash(gh issue create *)"
+    - "Bash(gh issue edit *)"
+    - "Bash(gh issue view *)"
+    - "Bash(gh issue list *)"
+    - "Bash(gh issue comment *)"
+    - "Bash(gh label list *)"
+  sandbox_bypass:
+    - "Bash(agent *)"
+    - "Bash(git-spice branch submit *)"
+    - "Bash(git-spice repo sync*)"
+    - "Bash(gh pr create *)"
+
 rooms:
   - engineering
   - name: announcements
@@ -29,6 +56,7 @@ env:
   AGENTD_WRAP_SERVICE_URL: http://localhost:7005
   AGENTD_ORCHESTRATOR_SERVICE_URL: http://localhost:7006
   AGENTD_MEMORY_SERVICE_URL: http://localhost:7008
+  AGENTD_INDEX_SERVICE_URL: http://localhost:7012
   AGENTD_COMMUNICATE_SERVICE_URL: http://localhost:7010
 
 system_prompt: |
@@ -329,3 +357,31 @@ system_prompt: |
   - PR-specific feedback already posted as GitHub comments
   - ADR content already written to `docs/planning/decisions/`
   - Standard Rust patterns (use Rust docs for those)
+
+  ## Code Index Protocol
+
+  You have access to a semantic code search service via the `agent index` CLI.
+  Use it for cross-crate analysis and service boundary verification. The index
+  complements memory: memory stores human knowledge and decisions; index searches
+  actual source code. If the index service is unavailable, fall back to `grep -r`.
+
+  ### During Architecture Reviews
+  1. Find all implementations of a trait across crates:
+     agent index search "<TraitName>" --mode keyword --hierarchy symbol --limit 20 --json
+  2. Check for cross-crate type usage (potential boundary violations):
+     agent index search "use agentd_<crate>" --mode keyword --limit 20 --json
+  3. Find all API route definitions to check pattern compliance:
+     agent index search "Router::new route" --mode hybrid --file-pattern "crates/*/src/api*" --limit 20 --json
+  4. Search for duplicate type definitions across crates:
+     agent index search "<TypeName>" --mode keyword --hierarchy symbol --limit 20 --json
+
+  ### ADR Research
+  When assessing whether an ADR is needed, search for existing patterns:
+    agent index search "<proposed pattern or technology>" --mode vector --language rust --limit 10 --json
+
+  ### Search Mode Guide
+  - Use `--mode keyword` for precise cross-crate import analysis
+  - Use `--mode hybrid` for architectural pattern searches
+  - Use `--mode vector` for conceptual queries about design approaches
+  - Add `--hierarchy symbol` for trait/struct/enum discovery
+  - Add `--hierarchy directory` for module-level architectural overview

.agentd/agents/conductor.yml

@@ -1,3 +1,5 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/geoffjay/agentd/main/schemas/agent.yml
+
 # Conductor agent — pipeline orchestration and merge queue management.
 #
 # The conductor owns the end-to-end issue lifecycle: dispatching work,
@@ -50,6 +52,7 @@ env:
   AGENTD_WRAP_SERVICE_URL: http://localhost:7005
   AGENTD_ORCHESTRATOR_SERVICE_URL: http://localhost:7006
   AGENTD_MEMORY_SERVICE_URL: http://localhost:7008
+  AGENTD_INDEX_SERVICE_URL: http://localhost:7012
   AGENTD_COMMUNICATE_SERVICE_URL: http://localhost:7010
 
 system_prompt: |

.agentd/agents/designer.yml

@@ -1,3 +1,5 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/geoffjay/agentd/main/schemas/agent.yml
+
 # Designer agent — maintains UI design, design system, and visual consistency.
 #
 # Usage:
@@ -38,6 +40,7 @@ env:
   AGENTD_WRAP_SERVICE_URL: http://localhost:7005
   AGENTD_ORCHESTRATOR_SERVICE_URL: http://localhost:7006
   AGENTD_MEMORY_SERVICE_URL: http://localhost:7008
+  AGENTD_INDEX_SERVICE_URL: http://localhost:7012
   AGENTD_COMMUNICATE_SERVICE_URL: http://localhost:7010
 
 system_prompt: |

.agentd/agents/documenter.yml

@@ -1,3 +1,5 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/geoffjay/agentd/main/schemas/agent.yml
+
 # Documentation agent — maintains and improves project documentation.
 #
 # Usage:
@@ -34,6 +36,7 @@ env:
   AGENTD_WRAP_SERVICE_URL: http://localhost:7005
   AGENTD_ORCHESTRATOR_SERVICE_URL: http://localhost:7006
   AGENTD_MEMORY_SERVICE_URL: http://localhost:7008
+  AGENTD_INDEX_SERVICE_URL: http://localhost:7012
   AGENTD_COMMUNICATE_SERVICE_URL: http://localhost:7010
 
 system_prompt: |

.agentd/agents/enricher.yml

@@ -1,3 +1,5 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/geoffjay/agentd/main/schemas/agent.yml
+
 # Enricher agent — improves issue quality before worker implementation.
 #
 # Triggered when an issue is labeled with "enrich-agent". Reads the issue,
@@ -27,6 +29,7 @@ env:
   AGENTD_WRAP_SERVICE_URL: http://localhost:7005
   AGENTD_ORCHESTRATOR_SERVICE_URL: http://localhost:7006
   AGENTD_MEMORY_SERVICE_URL: http://localhost:7008
+  AGENTD_INDEX_SERVICE_URL: http://localhost:7012
   AGENTD_COMMUNICATE_SERVICE_URL: http://localhost:7010
 
 system_prompt: |
@@ -193,3 +196,31 @@ system_prompt: |
   ### What NOT to Remember
   - Issue-specific content already captured in GitHub comments
   - File paths and type names already in the source code
+
+  ## Code Index Protocol
+
+  You have access to a semantic code search service via the `agent index` CLI.
+  Use it instead of grep to find relevant code when enriching issues. The index
+  provides semantic understanding, not just text matching. The index complements
+  memory: memory stores human knowledge and decisions; index searches actual source
+  code. If the index service is unavailable, fall back to `grep -r`.
+
+  ### During Enrichment
+  1. Search for code related to the issue topic:
+     agent index search "<issue topic or feature area>" --mode vector --language rust --limit 10 --json
+  2. Find specific types, functions, or modules mentioned in the issue:
+     agent index search "<TypeName or function_name>" --mode keyword --hierarchy symbol --limit 5 --json
+  3. Find test patterns for the affected area:
+     agent index search "<feature area> test" --mode hybrid --file-pattern "crates/*/src/**" --limit 5 --json
+
+  ### Enrichment-Specific Uses
+  - When listing "Relevant Files": use index search results instead of guessing
+  - When writing "Implementation Hints": search for existing patterns the implementer should follow
+  - When suggesting "Test Cases": search for existing test patterns in the affected crate
+  - When assessing scope: search to understand how many files touch the affected area
+
+  ### Search Mode Guide
+  - Use `--mode vector` for mapping issue descriptions to relevant code
+  - Use `--mode keyword` for specific identifier lookups
+  - Use `--mode hybrid` when the issue mentions both concepts and specific names
+  - Add `--hierarchy symbol` to find the exact functions/structs an implementer needs

.agentd/agents/planner.yml

@@ -1,3 +1,5 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/geoffjay/agentd/main/schemas/agent.yml
+
 # Planning agent — analyzes the agentd codebase and proposes GitHub issues.
 #
 # Usage:
@@ -9,6 +11,27 @@ shell: /bin/zsh
 worktree: false
 model: claude-opus-4-6
 
+# Tool policy: codebase read access + tools for applying triage results
+tool_policy:
+  mode: allow_list
+  tools:
+    - Read
+    - Grep
+    - Glob
+    - WebFetch
+    - "Bash(gh issue create *)"
+    - "Bash(gh issue edit *)"
+    - "Bash(gh issue view *)"
+    - "Bash(gh issue list *)"
+    - "Bash(gh issue comment *)"
+    - "Bash(gh label list *)"
+    - "Bash(agent memory *)"
+  sandbox_bypass:
+    - "Bash(agent *)"
+    - "Bash(git-spice branch submit *)"
+    - "Bash(git-spice repo sync*)"
+    - "Bash(gh pr create *)"
+
 rooms:
   - engineering
   - name: announcements
@@ -22,6 +45,7 @@ env:
   AGENTD_WRAP_SERVICE_URL: http://localhost:7005
   AGENTD_ORCHESTRATOR_SERVICE_URL: http://localhost:7006
   AGENTD_MEMORY_SERVICE_URL: http://localhost:7008
+  AGENTD_INDEX_SERVICE_URL: http://localhost:7012
   AGENTD_COMMUNICATE_SERVICE_URL: http://localhost:7010
 
 system_prompt: |
@@ -148,3 +172,22 @@ system_prompt: |
   ### What NOT to Remember
   - Issue contents already captured in GitHub
   - Information already in code, comments, or git history
+
+  ## Code Index Protocol
+
+  You have access to a semantic code search service via the `agent index` CLI.
+  Use it to understand codebase structure when planning work. If the index
+  service is unavailable, skip this step.
+
+  ### During Planning
+  1. Survey existing implementations before proposing new work:
+     agent index search "<feature area>" --mode vector --language rust --limit 10 --json
+  2. Verify assumptions about what exists:
+     agent index search "<type or function assumed to exist>" --mode keyword --hierarchy symbol --limit 5 --json
+  3. When estimating scope, search to understand the affected code surface:
+     agent index search "<expected pattern>" --mode hybrid --limit 10 --json
+
+  ### Planning-Specific Uses
+  - Before proposing an issue: search to verify the feature does not already exist
+  - When defining dependencies between issues: search to understand which crates share types
+  - Add `--hierarchy directory` for module-level overviews

.agentd/agents/refactor.yml

@@ -1,3 +1,5 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/geoffjay/agentd/main/schemas/agent.yml
+
 # Refactor agent — identifies and implements code improvement opportunities.
 #
 # Operates in two modes:
@@ -30,6 +32,11 @@ tool_policy:
     - "Edit(docs/**)"
     - "Write(CLAUDE.md)"
     - "Edit(CLAUDE.md)"
+  sandbox_bypass:
+    - "Bash(agent *)"
+    - "Bash(git-spice branch submit *)"
+    - "Bash(git-spice repo sync*)"
+    - "Bash(gh pr create *)"
 
 rooms:
   - engineering
@@ -44,6 +51,7 @@ env:
   AGENTD_WRAP_SERVICE_URL: http://localhost:7005
   AGENTD_ORCHESTRATOR_SERVICE_URL: http://localhost:7006
   AGENTD_MEMORY_SERVICE_URL: http://localhost:7008
+  AGENTD_INDEX_SERVICE_URL: http://localhost:7012
   AGENTD_COMMUNICATE_SERVICE_URL: http://localhost:7010
 
 system_prompt: |
@@ -361,3 +369,23 @@ system_prompt: |
   ### What NOT to Remember
   - Issue contents already captured in GitHub
   - Standard Rust idioms (use clippy for those)
+
+  ## Code Index Protocol
+
+  You have access to a semantic code search service via the `agent index` CLI.
+  Use it to find all call sites and usages before refactoring. The index
+  complements memory: memory stores human knowledge and decisions; index searches
+  actual source code. If the index service is unavailable, fall back to `grep -r`.
+
+  ### Before Each Refactor
+  1. Find all usages of the type/function being refactored:
+     agent index search "<name being refactored>" --mode keyword --hierarchy symbol --limit 20 --json
+  2. Find all callers across crates:
+     agent index search "<function or method name>" --mode keyword --limit 20 --json
+  3. Search for similar patterns that should be refactored consistently:
+     agent index search "<pattern being changed>" --mode hybrid --language rust --limit 10 --json
+
+  ### Search Mode Guide
+  - Use `--mode keyword` for precise call-site discovery
+  - Use `--mode hybrid` for finding similar patterns across the codebase
+  - Add `--hierarchy symbol` for function/struct/trait lookups

.agentd/agents/release-manager.yml

@@ -1,3 +1,5 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/geoffjay/agentd/main/schemas/agent.yml
+
 # Release manager agent — changelog generation, version bumping, and GitHub releases.
 #
 # Manually triggered via the "release" label on a release issue. The issue
@@ -30,6 +32,7 @@ env:
   AGENTD_WRAP_SERVICE_URL: http://localhost:7005
   AGENTD_ORCHESTRATOR_SERVICE_URL: http://localhost:7006
   AGENTD_MEMORY_SERVICE_URL: http://localhost:7008
+  AGENTD_INDEX_SERVICE_URL: http://localhost:7012
   AGENTD_COMMUNICATE_SERVICE_URL: http://localhost:7010
 
 system_prompt: |

.agentd/agents/research.yml

@@ -1,3 +1,5 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/geoffjay/agentd/main/schemas/agent.yml
+
 # Research agent — technology investigation and architectural analysis.
 #
 # Investigates crate ecosystems, protocols, design patterns, and architectural
@@ -36,6 +38,7 @@ env:
   AGENTD_WRAP_SERVICE_URL: http://localhost:7005
   AGENTD_ORCHESTRATOR_SERVICE_URL: http://localhost:7006
   AGENTD_MEMORY_SERVICE_URL: http://localhost:7008
+  AGENTD_INDEX_SERVICE_URL: http://localhost:7012
   AGENTD_COMMUNICATE_SERVICE_URL: http://localhost:7010
 
 system_prompt: |
@@ -322,3 +325,20 @@ system_prompt: |
   - Research findings already posted as issue comments (already in GitHub)
   - Information already captured in source code or documentation
   - Ephemeral findings that depend on a specific version and will likely change
+
+  ## Code Index Protocol
+
+  You have access to a semantic code search service via the `agent index` CLI.
+  Use it to investigate codebase patterns during research. If the index service
+  is unavailable, fall back to `grep -r`.
+
+  ### During Research
+  1. Search for existing implementations of the pattern being researched:
+     agent index search "<research topic>" --mode vector --language rust --limit 10 --json
+  2. Find all usages of a specific library or crate:
+     agent index search "<crate or library name>" --mode keyword --limit 10 --json
+
+  ### Search Mode Guide
+  - Use `--mode vector` for broad exploratory searches
+  - Use `--mode keyword` for precise identifier lookups
+  - Use `--mode hybrid` for mixed queries

.agentd/agents/reviewer.yml

@@ -1,3 +1,5 @@
+# yaml-language-server: $schema=https://raw.githubusercontent.com/geoffjay/agentd/main/schemas/agent.yml
+
 # PR reviewer agent — performs autonomous code reviews on pull requests.
 #
 # Usage:
@@ -23,6 +25,7 @@ env:
   AGENTD_WRAP_SERVICE_URL: http://localhost:7005
   AGENTD_ORCHESTRATOR_SERVICE_URL: http://localhost:7006
   AGENTD_MEMORY_SERVICE_URL: http://localhost:7008
+  AGENTD_INDEX_SERVICE_URL: http://localhost:7012
   AGENTD_COMMUNICATE_SERVICE_URL: http://localhost:7010
 
 system_prompt: |
@@ -122,3 +125,33 @@ system_prompt: |
   ### What NOT to Remember
   - PR-specific feedback already captured in GitHub comments
   - Information already in code, comments, or git history
+
+  ## Code Index Protocol
+
+  You have access to a semantic code search service via the `agent index` CLI.
+  Use it to understand the broader context of code changes during reviews. The
+  index complements memory: memory stores human knowledge and decisions; index
+  searches actual source code. If the index service is unavailable, fall back
+  to `grep -r`.
+
+  ### Before Each Review
+  After reading the PR diff, use the index to understand context:
+  1. For each changed function or type, search for related code:
+     agent index search "<changed function or type name>" --mode keyword --hierarchy symbol --limit 5 --json
+  2. Find callers and dependents of changed interfaces:
+     agent index search "<function or trait being modified>" --mode hybrid --language rust --limit 10 --json
+  3. Check if the PR's patterns are consistent with existing code:
+     agent index search "<pattern or approach used in the PR>" --mode vector --limit 5 --json
+
+  ### Review-Specific Uses
+  - When a PR adds a new function: search for similar existing functions to check naming consistency
+  - When a PR changes a public API: search for all callers to assess impact
+  - When a PR adds error handling: search for the project's error handling patterns
+  - When a PR touches shared types: search for all usages across crates
+  - Before approving API changes: verify all callers are covered by the PR or its tests
+
+  ### Search Mode Guide
+  - Use `--mode keyword` for exact symbol lookups from the diff
+  - Use `--mode hybrid` for finding related code patterns
+  - Add `--hierarchy symbol` to find specific functions/structs/traits
+  - Add `--file-pattern "crates/<crate>/src/**"` to scope to a specific crate