Repository Pattern Database Agnostic Refactor

Repository Pattern — Database-Agnostic Refactor

Decision (WHY)

Teams should adopt Testo without migrating to a mandated database. Run history and archives must work against SQLite (zero-config local), PostgreSQL (compose/default), or MySQL (enterprise) via a single connection string.

Current implementation (HOW — codebase)

Piece	Location
URL resolution	testo_core/repository/db_config.py — DATABASE_URL, legacy POSTGRES_*, default SQLite
Service locator	testo_core/repository/db.py — get_repository(), get_report_archive_repository()
Protocol	testo_core/repository/base.py — BaseRunRepository
Adapters	testo_core/repository/adapters.py, factory.py
Models	testo_core/repository/models.py — dialect-portable JSON columns

Configure via database.url in testosterone.yaml or DATABASE_URL. See Command Reference § Environment variables (common) and Architecture Overview § Configuration as the single source of truth.

Release verification

Release Checklist - Phase 1 Foundation — repository contract tests and packaging gate.

---

Context & Links: Architecture Overview, Product Roadmap § Phase 1: Decoupling & Distribution (Foundation), Release Checklist - Phase 1 Foundation

---

Generated from docs/Specs & ADRs/Repository Pattern - Database-Agnostic Refactor.md. Edit it there; changes made in the wiki are overwritten.