claude-flow-novice 2.18.40 → 2.19.0

package/.claude/agents/cfn-dev-team/documentation/pseudocode.md

@@ -1,7 +1,7 @@
 ---
 name: pseudocode
 description: MUST BE USED for algorithm design, logic planning, code outline creation. Use PROACTIVELY for problem decomposition, planning. Keywords - pseudocode, algorithm, logic, planning
-model: haiku
+model: opus
 color: indigo
 type: specialist
 capabilities:

package/.claude/agents/cfn-dev-team/documentation/specification-agent.md

@@ -2,7 +2,7 @@
 name: specification-agent
 description: MUST BE USED when defining requirements, specifications, or problem analysis in SPARC methodology. Use PROACTIVELY for requirements gathering, constraint identification, acceptance criteria definition, scope analysis, stakeholder requirements, domain analysis, use case documentation.
 type: specialist
-model: haiku
+model: opus
 capabilities:
   - requirements_gathering
   - constraint_analysis

package/.claude/agents/cfn-dev-team/testers/tester.md

@@ -29,6 +29,41 @@ validation_hooks:
 
 # Comprehensive Tester Agent Profile
 
+## ⚠️ TEST FRAMEWORK ALIGNMENT (MANDATORY)
+
+**Before writing ANY tests, you MUST detect and align with the existing test framework.**
+
+```bash
+# Detect existing test framework
+if grep -q "vitest" package.json 2>/dev/null; then
+  FRAMEWORK="vitest"
+elif grep -q "jest" package.json 2>/dev/null; then
+  FRAMEWORK="jest"
+elif ls *.test.ts *.spec.ts 2>/dev/null | head -1 | xargs grep -l "vitest\|vi\." 2>/dev/null; then
+  FRAMEWORK="vitest"
+elif ls *.test.ts *.spec.ts 2>/dev/null | head -1 | xargs grep -l "jest\|expect(" 2>/dev/null; then
+  FRAMEWORK="jest"
+fi
+```
+
+| Check | Action |
+|-------|--------|
+| `vitest` in package.json | Use vitest patterns: `vi.fn()`, `vi.mock()` |
+| `jest` in package.json | Use jest patterns: `jest.fn()`, `jest.mock()` |
+| Existing `*.test.ts` files | Match their import style exactly |
+| `vitest.config.ts` exists | Use vitest |
+| `jest.config.js` exists | Use jest |
+
+**NEVER mix frameworks. If project uses vitest, do NOT import from jest. If project uses jest, do NOT import from vitest.**
+
+**Common mistakes to avoid:**
+- ❌ `import { jest } from '@jest/globals'` in a vitest project
+- ❌ `import { vi } from 'vitest'` in a jest project
+- ❌ Using `jest.fn()` when project uses `vi.fn()`
+- ❌ Creating `jest.config.js` when `vitest.config.ts` exists
+
+---
+
 ## Success Criteria Awareness (REQUIRED - Phase 2 TDD)
 
 → See: `.claude/skills/cfn-test-execution/SKILL.md` for test execution framework

package/.claude/commands/{cfn-ruvector → cfn-codesearch}/cfn-codebase-reindex.md

@@ -17,7 +17,7 @@ Add `--force` flag for complete reindex:
 - Major restructuring
 - Index issues
 
-**Log file:** `/tmp/ruvector-index.log` - tail this for progress monitoring.
+**Log file:** `/tmp/codesearch-index.log` - tail this for progress monitoring.
 
 ---
 
@@ -40,9 +40,9 @@ fi
 echo "✅ OpenAI key: ${OPENAI_API_KEY:0:12}..."
 
 # --- Setup ---
-RUVECTOR_BIN="${HOME}/.local/bin/local-ruvector"
-[ ! -f "$RUVECTOR_BIN" ] && RUVECTOR_BIN="./.claude/skills/cfn-local-ruvector-accelerator/target/release/local-ruvector"
-LOG_FILE="/tmp/ruvector-index.log"
+RUVECTOR_BIN="${HOME}/.local/bin/local-codesearch"
+[ ! -f "$RUVECTOR_BIN" ] && RUVECTOR_BIN="./.claude/skills/cfn-local-codesearch-accelerator/target/release/local-codesearch"
+LOG_FILE="/tmp/codesearch-index.log"
 
 echo "📝 Logging to: $LOG_FILE"
 echo "   Monitor with: tail -f $LOG_FILE"

package/.claude/commands/{cfn-ruvector → cfn-codesearch}/cfn-codebase-search.md

@@ -1,5 +1,5 @@
 ---
-description: Search codebase using RuVector semantic index (400x faster than grep)
+description: Search codebase using CodeSearch semantic index (400x faster than grep)
 arguments:
   query:
     description: Natural language search query
@@ -11,12 +11,12 @@ arguments:
 
 # Codebase Search Command
 
-Search your indexed codebase using RuVector. Uses SQLite index for fast lookups.
+Search your indexed codebase using CodeSearch. Uses SQLite index for fast lookups.
 
 **Examples:**
-- `/cfn-ruvector:cfn-codebase-search authentication logic`
-- `/cfn-ruvector:cfn-codebase-search React components --top 20`
-- `/cfn-ruvector:cfn-codebase-search database migration`
+- `/cfn-codesearch:cfn-codebase-search authentication logic`
+- `/cfn-codesearch:cfn-codebase-search React components --top 20`
+- `/cfn-codesearch:cfn-codebase-search database migration`
 
 **Prerequisites:**
 - Codebase must be indexed: `/cfn-codebase-reindex`
@@ -33,8 +33,8 @@ if [[ ! "$OPENAI_API_KEY" =~ ^sk- ]] && [[ -f ".env" ]]; then
 fi
 [[ ! "$OPENAI_API_KEY" =~ ^sk- ]] && { echo "❌ OPENAI_API_KEY invalid. Add to .env" >&2; exit 1; }
 
-RUVECTOR_BIN="${HOME}/.local/bin/local-ruvector"
-[ ! -f "$RUVECTOR_BIN" ] && RUVECTOR_BIN="./.claude/skills/cfn-local-ruvector-accelerator/target/release/local-ruvector"
+RUVECTOR_BIN="${HOME}/.local/bin/local-codesearch"
+[ ! -f "$RUVECTOR_BIN" ] && RUVECTOR_BIN="./.claude/skills/cfn-local-codesearch-accelerator/target/release/local-codesearch"
 
 # Use threshold 0.1 for better results (default 0.3 is too strict)
 "$RUVECTOR_BIN" query "{{query}}" --max-results {{#if top}}{{top}}{{else}}10{{/if}} --threshold 0.1

package/.claude/commands/{cfn-ruvector → cfn-codesearch}/cfn-detect-stale-docs.md

@@ -1,5 +1,5 @@
 ---
-description: Detect stale and legacy documentation using RuVector semantic analysis
+description: Detect stale and legacy documentation using CodeSearch semantic analysis
 ---
 
 # Detect Stale Documentation
@@ -38,7 +38,7 @@ Analyzes all `.md` files in the codebase to detect legacy/outdated documentation
 
 ```bash
 # Find docs older than 90 days with no recent code references
-sqlite3 ~/.local/share/ruvector/index_v2.db "
+sqlite3 ~/.local/share/codesearch/index_v2.db "
 SELECT e.file_path, e.name,
        datetime(e.created_at, 'unixepoch') as indexed_at
 FROM entities e
@@ -48,7 +48,7 @@ WHERE e.file_path LIKE '%.md'
 LIMIT 20;"
 
 # Find orphan docs (no references)
-sqlite3 ~/.local/share/ruvector/index_v2.db "
+sqlite3 ~/.local/share/codesearch/index_v2.db "
 SELECT DISTINCT e.file_path
 FROM entities e
 LEFT JOIN refs r ON e.id = r.source_entity_id OR e.id = r.target_entity_id

package/.claude/commands/{cfn-ruvector-search.md → cfn-codesearch-search.md}

@@ -1,17 +1,17 @@
 ---
-description: "Semantic code search with RuVector (400x faster than grep)"
+description: "Semantic code search with CodeSearch (400x faster than grep)"
 argument-hint: "<query>"
 ---
 
-# RuVector Search
+# CodeSearch Search
 
 Quick semantic search through your indexed codebase.
 
 ## Usage
 
 ```
-/cfn-ruvector-search "authentication middleware"
-/cfn-ruvector-search "error handling pattern"
+/cfn-codesearch-search "authentication middleware"
+/cfn-codesearch-search "error handling pattern"
 ```
 
 ## What it does
@@ -23,14 +23,14 @@ Quick semantic search through your indexed codebase.
 ## Prerequisites
 
 - Project must be indexed first
-- Run: `./local-ruvector index --path . --force`
+- Run: `./local-codesearch index --path . --force`
 
 ---
 
 Execute search:
 
 ```bash
-RUVECTOR_BIN="${HOME}/.local/bin/local-ruvector"
-[ ! -f "$RUVECTOR_BIN" ] && RUVECTOR_BIN="./.claude/skills/cfn-local-ruvector-accelerator/target/release/local-ruvector"
+RUVECTOR_BIN="${HOME}/.local/bin/local-codesearch"
+[ ! -f "$RUVECTOR_BIN" ] && RUVECTOR_BIN="./.claude/skills/cfn-local-codesearch-accelerator/target/release/local-codesearch"
 "$RUVECTOR_BIN" query "$ARGUMENTS" --max-results 10
 ```

package/.claude/commands/cfn-fix-errors.md

@@ -124,7 +124,7 @@ Task("typescript-specialist" /* or "rust-developer" */,
 ```typescript
 Task("typescript-specialist" /* or "rust-developer" */,
   `# FORBIDDEN: Do NOT run npx tsc, npm run typecheck, or cargo check
-  # Use ruvector skills in place of 'search' or 'find' 
+  # Use codesearch skills in place of 'search' or 'find' 
   # REQUIRED: Use CFN hooks for validation
 
   ## MANDATORY WORKFLOW:

package/.claude/commands/cfn-loop-task.md

@@ -10,6 +10,47 @@ allowed-tools: ["Task", "TodoWrite", "Read", "Bash", "Grep", "Glob"]
 
 ---
 
+## ⚡ AUTONOMOUS PROGRESSION (CRITICAL)
+
+**DO NOT stop to ask questions. Keep progressing by launching agents for next steps.**
+
+| Stop For | Keep Going For |
+|----------|----------------|
+| Major regression (tests went from passing to failing) | Minor test failures (iterate to fix) |
+| Structural mismatch (wrong architecture/framework) | Missing files (create them) |
+| Security vulnerability found | Code style issues |
+| Corrupted state requiring manual recovery | Ambiguous implementation details |
+| Unclear requirements (feedback for epic improvement) | |
+
+**Rules:**
+- If uncertain about approach, pick the simpler option and iterate
+- Spawn agents to investigate unknowns instead of asking user
+- Only escalate to user for irreversible decisions or access issues
+- Test failures are expected - that's why we iterate
+
+---
+
+## 🎯 0/0 POLICY (EXIT CRITERIA)
+
+**Before PROCEED decision, verify:**
+
+| Metric | Requirement |
+|--------|-------------|
+| Compilation errors (scoped work) | **0** |
+| Compilation errors (scoped tests) | **0** |
+| Todos remaining (scoped work) | **0** |
+
+```bash
+# Verify 0/0 before PROCEED
+npm run typecheck 2>&1 | grep -c "error" || echo "0"  # Must be 0
+npm run build 2>&1 | grep -c "error" || echo "0"      # Must be 0
+# Review TodoWrite - all scoped items must be completed
+```
+
+**If not 0/0:** ITERATE, do not PROCEED. Fix errors before next gate check.
+
+---
+
 ## MANDATORY: Initialize State Tracking
 
 **IMMEDIATELY create this todo list using TodoWrite:**
@@ -184,6 +225,7 @@ CONTEXT:
 - Mode: ${MODE}
 - Iteration: ${ITERATION}
 - Gate pass rate: ${PASS_RATE}
+- Epic file: ${EPIC_FILE_PATH} (if applicable)
 
 VALIDATOR FEEDBACK:
 ${VALIDATOR_1_FEEDBACK}
@@ -194,6 +236,13 @@ YOUR RESPONSIBILITIES:
 2. Classify each finding as IN-SCOPE or OUT-OF-SCOPE
 3. OUT-OF-SCOPE items: Log for backlog, do NOT require iteration
 4. IN-SCOPE items: Determine if they block PROCEED
+5. **EPIC CONSISTENCY CHECK**: Identify naming/reference mismatches in epic document
+
+EPIC CONSISTENCY CHECK:
+- Compare implemented names (files, modules, functions) against epic references
+- Flag mismatches (e.g., phase 1 creates "AuthService" but phase 3 references "AuthenticationService")
+- If mismatches found: Update epic document to match implementation
+- Document all corrections in epic_corrections field
 
 DECISION CRITERIA:
 - PROCEED: All in-scope requirements met, tests pass, no blocking issues
@@ -206,12 +255,17 @@ RETURN FORMAT:
   "in_scope_findings": [...],
   "out_of_scope_findings": [...],
   "reasoning": "...",
-  "iteration_guidance": "..." (if ITERATE)
+  "iteration_guidance": "..." (if ITERATE),
+  "epic_corrections": [
+    {"location": "Phase 3, step 2", "was": "XY", "now": "X", "reason": "Match phase 1 implementation"}
+  ]
 }
 
 AGENT_ID: product-owner-${TASK_ID}-iter${ITERATION}
 ```
 
+**If epic_corrections returned:** Update the epic file to fix inconsistencies before next iteration.
+
 **WAIT for Product Owner agent to return decision.**
 
 **Handle Decision:**
@@ -276,6 +330,7 @@ Task(subagent_type="root-cause-analyst", prompt="Analyze repeated failures...")
 - OUT-OF-SCOPE items go to backlog, don't block PROCEED
 - Only IN-SCOPE issues can trigger ITERATE
 - ABORT is rare (corruption, security, dead-end architecture)
+- **Epic consistency**: Fixes naming mismatches between phases (e.g., "X" vs "XY")
 
 ---
 
@@ -286,10 +341,19 @@ Task(subagent_type="root-cause-analyst", prompt="Analyze repeated failures...")
 - **DO NOT skip Product Owner** - Only PO can approve PROCEED
 - **DO NOT iterate on out-of-scope items** - PO filters these to backlog
 - **DO NOT stop on test failures** - That's what iteration fixes
+- **DO NOT ask the user questions** - Make reasonable assumptions and iterate
 - **DO update todos** - This tracks your state as coordinator
 - **DO pass validator feedback to PO** - PO needs full context to decide
 - **DO inject PO guidance into next iteration** - Use iteration_guidance from PO
+- **DO spawn agents to investigate unknowns** - Instead of asking user
+
+**When to escalate to user (ONLY these cases):**
+- Access denied / permission errors
+- Irreversible destructive action needed
+- Major regression detected (tests were passing, now failing)
+- Structural mismatch with existing codebase
+- Unclear requirements (helps improve epic creation process)
 
 ---
 
-**Version:** 2.0.0 | **Date:** 2026-01-09 | Restructured with enforced state tracking + Product Owner scope filtering
+**Version:** 2.2.0 | **Date:** 2026-01-13 | Added 0/0 policy, epic consistency check, autonomous progression

package/.claude/skills/{bulk-add-ruvector-instructions.sh → bulk-add-codesearch-instructions.sh}

@@ -1,30 +1,30 @@
 #!/bin/bash
 set -eu
 
-# Add RuVector instructions to all agent profiles with Post-Edit Pipeline
+# Add CodeSearch instructions to all agent profiles with Post-Edit Pipeline
 
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 AGENT_DIR="${SCRIPT_DIR}/../agents/cfn-dev-team"
 
-# RuVector instruction block to add
+# CodeSearch instruction block to add
 RUVECTOR_BLOCK='
-# IMPORTANT: RuVector Semantic Search (Before Making Changes)
+# IMPORTANT: CodeSearch Semantic Search (Before Making Changes)
 # Before implementing any changes, ALWAYS query the codebase for similar patterns:
 #   /codebase-search "relevant search terms for your task" --top 5
 #   /codebase-search "error pattern or issue you'\''re fixing" --top 3
 # Also query past errors and learnings:
-#   ./.claude/skills/cfn-ruvector-codebase-index/query-error-patterns.sh --task-description "Your task description"
-#   ./.claude/skills/cfn-ruvector-codebase-index/query-learnings.sh --task-description "Your task description" --category PATTERN
+#   ./.claude/skills/cfn-codesearch-codebase-index/query-error-patterns.sh --task-description "Your task description"
+#   ./.claude/skills/cfn-codesearch-codebase-index/query-learnings.sh --task-description "Your task description" --category PATTERN
 # This prevents duplicated work and leverages existing solutions.'
 
 # Function to add instructions after post-edit pipeline section
-add_ruvector_instructions() {
+add_codesearch_instructions() {
     local file="$1"
     local temp_file=$(mktemp)
 
-    # Check if file already has RuVector instructions
-    if grep -q "RuVector Semantic Search" "$file"; then
-        echo "⚠️  $(basename "$file") already has RuVector instructions"
+    # Check if file already has CodeSearch instructions
+    if grep -q "CodeSearch Semantic Search" "$file"; then
+        echo "⚠️  $(basename "$file") already has CodeSearch instructions"
         rm -f "$temp_file"
         return 0
     fi
@@ -41,7 +41,7 @@ add_ruvector_instructions() {
         {print}
         ' "$file" > "$temp_file"
         mv "$temp_file" "$file"
-        echo "✅ Added RuVector to $(basename "$file")"
+        echo "✅ Added CodeSearch to $(basename "$file")"
         return 1
     else
         rm -f "$temp_file"
@@ -50,7 +50,7 @@ add_ruvector_instructions() {
 }
 
 # Process all agent files recursively
-echo "🔄 Adding RuVector instructions to agent profiles..."
+echo "🔄 Adding CodeSearch instructions to agent profiles..."
 echo ""
 
 updated=0
@@ -64,7 +64,7 @@ while IFS= read -r -d '' agent_file; do
         continue
     fi
 
-    if add_ruvector_instructions "$agent_file"; then
+    if add_codesearch_instructions "$agent_file"; then
         ((skipped++)) || true
     else
         ((updated++)) || true

package/.claude/skills/{cfn-local-ruvector-accelerator → cfn-codesearch}/AGENT_INTEGRATION_PATTERNS.md

@@ -1,10 +1,10 @@
-# Agent Integration Patterns for AST-Aware RuVector
+# Agent Integration Patterns for AST-Aware CodeSearch
 
-This document describes how agents can integrate with the AST-aware RuVector indexer to achieve sub-50ms query performance for code intelligence tasks.
+This document describes how agents can integrate with the AST-aware CodeSearch indexer to achieve sub-50ms query performance for code intelligence tasks.
 
 ## Overview
 
-The AST-Aware RuVector Accelerator provides:
+The AST-Aware CodeSearch Accelerator provides:
 - Entity-based indexing (functions, structs, traits, etc.)
 - Reference tracking (calls, imports, type usage)
 - Vector embeddings for semantic search
@@ -15,11 +15,11 @@ The AST-Aware RuVector Accelerator provides:
 ### 1. Agent Setup
 
 ```bash
-# Initialize RuVector in the project
-./target/release/local-ruvector init
+# Initialize CodeSearch in the project
+./target/release/local-codesearch init
 
 # Index the codebase
-./target/release/local-ruvector index --path . --types rs,ts,tsx,js,jsx --force
+./target/release/local-codesearch index --path . --types rs,ts,tsx,js,jsx --force
 ```
 
 ### 2. Query Patterns
@@ -28,7 +28,7 @@ The AST-Aware RuVector Accelerator provides:
 
 ```bash
 # Find all functions that use the `Album` type
-./target/release/local-ruvector find --kind function --uses-type Album
+./target/release/local-codesearch find --kind function --uses-type Album
 
 # Example SQL query behind the scenes:
 SELECT e.* FROM entities e
@@ -40,10 +40,10 @@ WHERE e.kind = 'function' AND tu.type_name = 'Album';
 
 ```bash
 # Find all functions that call `create_album`
-./target/release/local-ruvector refs --target create_album --kind calls
+./target/release/local-codesearch refs --target create_album --kind calls
 
 # Exclude calls within the same module
-./target/release/local-ruvector refs --target create_album --kind calls --exclude-module src/album/
+./target/release/local-codesearch refs --target create_album --kind calls --exclude-module src/album/
 
 # Example SQL query:
 SELECT r.* FROM refs r
@@ -56,16 +56,16 @@ WHERE e.name = 'create_album' AND r.ref_kind = 'call'
 
 ```bash
 # Step 1: Find all references to a function
-./target/release/local-ruvector refs --target function_name
+./target/release/local-codesearch refs --target function_name
 
 # Step 2: Find all implementations of a trait
-./target/release/local-ruvector find --kind impl --implements Trait
+./target/release/local-codesearch find --kind impl --implements Trait
 
 # Step 3: Find types used in a module
-./target/release/local-ruvector find --file-path src/module/ --kind struct
+./target/release/local-codesearch find --file-path src/module/ --kind struct
 
 # Step 4: Verify no breaks after refactoring
-./target/release/local-ruvector query "broken reference error" --threshold 0.9
+./target/release/local-codesearch query "broken reference error" --threshold 0.9
 ```
 
 ### 3. Programmatic Integration
@@ -73,8 +73,8 @@ WHERE e.name = 'create_album' AND r.ref_kind = 'call'
 Agents can integrate using the Rust API directly:
 
 ```rust
-use local_ruvector::store_v2::StoreV2;
-use local_ruvector::query_api::QueryEngine;
+use local_codesearch::store_v2::StoreV2;
+use local_codesearch::query_api::QueryEngine;
 
 let store = StoreV2::new(&db_path)?;
 let query_engine = QueryEngine::new(store);
@@ -238,18 +238,18 @@ Based on the current implementation:
 
 ```bash
 # Check database health
-./target/release/local-ruvector stats --detailed
+./target/release/local-codesearch stats --detailed
 
 # Rebuild index
-./target/release/local-ruvector index --force
+./target/release/local-codesearch index --force
 
 # Query optimization
-sqlite3 .ruvector/index.db "EXPLAIN QUERY PLAN SELECT ..."
+sqlite3 .codesearch/index.db "EXPLAIN QUERY PLAN SELECT ..."
 
 # Check embeddings
-./target/release/local-ruvector query "test query" --format json
+./target/release/local-codesearch query "test query" --format json
 ```
 
 ## Conclusion
 
-The AST-Aware RuVector Accelerator provides a powerful foundation for agent-driven code intelligence. By leveraging entity-based indexing and structured queries, agents can achieve sub-50ms response times for complex code analysis tasks.
+The AST-Aware CodeSearch Accelerator provides a powerful foundation for agent-driven code intelligence. By leveraging entity-based indexing and structured queries, agents can achieve sub-50ms response times for complex code analysis tasks.

package/.claude/skills/{cfn-local-ruvector-accelerator → cfn-codesearch}/AGENT_LIFECYCLE_INTEGRATION.md

@@ -1,8 +1,8 @@
-# RuVector Agent Lifecycle Integration
+# CodeSearch Agent Lifecycle Integration
 
 ## Overview
 
-The RuVector Agent Lifecycle Integration automatically captures and indexes agent execution data, enabling semantic search over historical agent decisions, tool usage patterns, and failure recovery strategies.
+The CodeSearch Agent Lifecycle Integration automatically captures and indexes agent execution data, enabling semantic search over historical agent decisions, tool usage patterns, and failure recovery strategies.
 
 ## Architecture
 
@@ -108,7 +108,7 @@ Search historical agent data for guidance on current tasks.
 
 ## Integration with cfn-subagent-stop.sh
 
-The subagent stop hook automatically triggers RuVector ingestion:
+The subagent stop hook automatically triggers CodeSearch ingestion:
 
 ```bash
 # cfn-subagent-stop.sh (excerpt)
@@ -121,8 +121,8 @@ if awk "BEGIN {exit !($AGENT_CONFIDENCE < 0.70)}"; then
     AGENT_SUCCESS="false"
 fi
 
-# Call RuVector ingestion
-./.claude/skills/cfn-local-ruvector-accelerator/ingest-agent-transcript.sh \
+# Call CodeSearch ingestion
+./.claude/skills/cfn-local-codesearch-accelerator/ingest-agent-transcript.sh \
     --transcript "$TRANSCRIPT_ARCHIVE" \
     --agent-id "$AGENT_ID" \
     --agent-type "$AGENT_TYPE" \
@@ -283,9 +283,9 @@ sqlite3 "$DB_PATH" "DELETE FROM agent_failure_patterns WHERE occurrence_count <
 
 ### Log Management
 
-RuVector ingestion logs are written to:
-- `.artifacts/logs/ruvector-ingestion.log` - Transcript ingestion events
-- `.artifacts/logs/ruvector-failure-analysis.log` - Failure pattern analysis
+CodeSearch ingestion logs are written to:
+- `.artifacts/logs/codesearch-ingestion.log` - Transcript ingestion events
+- `.artifacts/logs/codesearch-failure-analysis.log` - Failure pattern analysis
 - `.artifacts/logs/subagent-lifecycle.log` - Hook execution logs
 
 Rotate logs periodically:
@@ -305,14 +305,14 @@ tail -f .artifacts/logs/subagent-lifecycle.log
 
 Verify script exists and is executable:
 ```bash
-ls -l .claude/skills/cfn-local-ruvector-accelerator/ingest-agent-transcript.sh
+ls -l .claude/skills/cfn-local-codesearch-accelerator/ingest-agent-transcript.sh
 ```
 
 ### No patterns found
 
 Run failure analysis manually:
 ```bash
-./.claude/skills/cfn-local-ruvector-accelerator/analyze-agent-failures.sh --days 30
+./.claude/skills/cfn-local-codesearch-accelerator/analyze-agent-failures.sh --days 30
 ```
 
 Check database tables exist:
@@ -337,5 +337,5 @@ Run with broader query:
 
 - Analysis document: `docs/RUVECTOR_INTEGRATION_ANALYSIS.md`
 - Subagent hooks: `.claude/hooks/cfn-subagent-*.sh`
-- RuVector accelerator: `.claude/skills/cfn-local-ruvector-accelerator/`
+- CodeSearch accelerator: `.claude/skills/cfn-local-codesearch-accelerator/`
 - Lifecycle database: `.claude/skills/cfn-redis-coordination/data/cfn-loop.db`

package/.claude/skills/{cfn-local-ruvector-accelerator → cfn-codesearch}/Cargo.toml

@@ -1,18 +1,23 @@
 [package]
-name = "local-ruvector"
-version = "0.1.0"
+name = "codesearch"
+version = "0.2.0"
 edition = "2021"
 
 [dependencies]
-# Database
+# Database - SQLite for metadata (entities, refs, fast SQL queries)
 rusqlite = { version = "0.31", features = ["bundled", "vtab"] }
+# Database - PostgreSQL/pgvector for embeddings (fast vector search)
+tokio-postgres = { version = "0.7", features = ["with-chrono-0_4", "with-serde_json-1"] }
+deadpool-postgres = { version = "0.12" }
+# pgvector type support for postgres
+pgvector = { version = "0.4", features = ["postgres"] }
 # Vector operations
 ndarray = { version = "0.15", features = ["rayon"], default-features = false }
 # Serialization
 serde = { version = "1.0", features = ["derive"] }
 serde_json = "1.0"
 # CLI
-clap = { version = "4.4", features = ["derive"] }
+clap = { version = "4.4", features = ["derive", "env"] }
 anyhow = "1.0"
 # File system
 walkdir = "2.4"

package/.claude/skills/{cfn-local-ruvector-accelerator → cfn-codesearch}/EXTRACTION_EXAMPLES.md

@@ -1,4 +1,4 @@
-# RuVector Extraction Examples
+# CodeSearch Extraction Examples
 
 This document demonstrates what the TypeScript/JavaScript and text-based fallback extractors capture from different file types.
 
@@ -207,7 +207,7 @@ setup_environment
 
 ## Indexing Results
 
-When you run `local-ruvector index`, the system:
+When you run `local-codesearch index`, the system:
 
 1. **Scans** all files in the project
 2. **Routes** files to appropriate extractors based on extension
@@ -279,9 +279,9 @@ Complete project indexing (10,000 files): ~30-50 seconds depending on file types
 
 After indexing:
 
-1. **Query** using `local-ruvector query`
-2. **Export** results using `local-ruvector export`
-3. **Analyze** dependencies using `local-ruvector refs`
-4. **Monitor** with `local-ruvector stats`
+1. **Query** using `local-codesearch query`
+2. **Export** results using `local-codesearch export`
+3. **Analyze** dependencies using `local-codesearch refs`
+4. **Monitor** with `local-codesearch stats`
 
 See the main README for detailed usage instructions.