- Status: Accepted
- Date: 2026-01-31
- Motivation:
- Provide API management for tracker category and media-domain Torznab mappings per ERD and ADR 128.
- Expose stored-proc-backed updates with consistent error mapping and audit tracking.
- Design notes:
- Add indexer facade methods for tracker category and media-domain mapping upsert/delete.
- Implement HTTP endpoints that call stored procedures via data-layer wrappers.
- Keep error messages constant; attach error codes/SQLSTATE as structured context.
- Test coverage summary:
- Data-layer tests for invalid key handling and primary mapping switch.
- API E2E coverage for mapping upsert/delete endpoints.
- Observability updates:
- None (existing tracing/logging patterns reused).
- Risk & rollback plan:
- Risk: incorrect mapping updates could affect category resolution.
- Rollback: revert API changes and restore seeded mappings via migrations/seed defaults.
- Dependency rationale: