What problem does it solve? Reviewing scalability in RAGAPPv3 requires knowing where its four SQLite connection pools live, which code paths secretly open extra connections, and how many concurrent users the pools can actually support before exhaustion. ## Core Features & Use Cases - Pool Inventory: Maps all 4 SQLite connection pools (main, MemoryStore, DocumentProcessor fallback, FileWatcher fallback) with sizes and exact file/line locations. - Double-Connection Detection: Identifies the evaluate_policy vs _evaluate_policy pattern where require_vault_permission consumes 2 pool connections per request instead of 1. - Semaphore & Lock Inventory: Catalogs async locks, semaphores, and circuit breakers with capacities and timeouts. - Exhaustion Headroom Calculation: Provides a formula (floor(pool_size / connections_per_request) - concurrent_users) to quantify capacity, plus a load test checklist for 8-10+ concurrent users. - Use Case: Before load-testing a vault-scoped endpoint at 10 concurrent users, load this Skill to predict that the double-connection pattern halves effective capacity and to know exactly which dependency to fix. ## Quick Start Review the scalability of the vault-scoped API routes and calculate connection pool headroom for 10 concurrent users.
