audit-sqlite

What problem does it solve?

Prevents database corruption and runtime failures by ensuring every SQLite access follows a consistent locking and idempotent schema pattern across the backend persistence layer.

Core Features & Use Cases

• Concurrency-safe SQLite access auditing: Checks whether code uses threading.Lock() consistently (including proper with self._lock: usage) to avoid “database is locked” and race conditions.
• Schema idempotency verification: Reviews whether schema operations (e.g., CREATE TABLE ... IF NOT EXISTS, ALTER TABLE patterns) are repeatable and safe.
• GUI write isolation validation: Ensures SQLite writes are not performed directly from GUI paths by comparing modules against the ClassificationDB reference pattern.

Use case: When refactoring or adding features to the contabilidad classifier workflow, audit gestor_contable/core/* SQLite modules to confirm they match the locking strategy used by ClassificationDB.

Quick Start

Ask the AI to run an audit of the SQLite modules in gestor_contable/core/ against the ClassificationDB locking and schema/idempotency pattern and produce the required “AUDITORIA: PERSISTENCIA SQLITE Y LOCKING” report with any real code findings.