internal/

Package advisor analyzes a SQLite database for performance problems that hurt in production — especially the ones AI-generated schemas ship by default: foreign keys with no index (a full scan on every join), redundant indexes, and, when queries are supplied, full table scans via EXPLAIN QUERY PLAN.

Package audit records an append-only, local-first history of every operation that changes a database — migrations, fleet convergence/recovery, SQL writes, and inline row edits.

Package autopilot is the DBA self-driving moat: it derives a set of safe maintenance and optimization actions for a SQLite database, explains each in plain language, and applies the safe ones automatically (snapshotting first).

Package connector provides a unified interface for loading SQLite schemas from local files or remote sources (Turso, Cloudflare D1).

Package d1sync implements full schema+data sync between a Cloudflare D1 database and a local SQLite file.

Package dashboard serves a local, self-hosted web view of a Litescope fleet.

Package dump produces a portable SQL dump of a local SQLite database — the schema as CREATE statements plus the data as INSERTs — equivalent to the sqlite3 shell's ".dump" command.

Package exporter is the data-out half of Litescope: it streams the result of a read-only query (or a whole table) to CSV / TSV / JSON.

Package fleet manages many SQLite databases as a single unit: discovery from Turso orgs and Cloudflare D1 accounts, baseline capture, and parallel drift detection across the whole fleet.

Package health inspects a SQLite database for operational faults a storage engineer cares about during an incident: corruption, WAL bloat from a starved checkpoint, fragmentation/space waste, and basic reachability.

Package importer ingests tabular data (CSV / TSV / JSON) into a SQLite table, inferring column types from the data.

Package license handles Pro feature gating.

Package lint flags SQLite schema *design* anti-patterns — the structural mistakes that ship by default, especially in hand-written or AI-generated schemas.

Package locks diagnoses SQLite locking and writer-starvation issues.

Package mcp exposes Litescope as a Model Context Protocol server over stdio, so an LLM agent (Claude Desktop, Claude Code, or any MCP client) can call Litescope operations as tools.

Package metrics renders fleet health and schema-fingerprint state as Prometheus / OpenMetrics text exposition, so a Litescope fleet drops straight into Grafana / Alertmanager without a bespoke integration.

Package migrate generates SQLite migration SQL from a diff result.

Package policy enforces local-first guardrails on operations that change a database.

Package report renders litescope results as standalone, shareable HTML — a single self-contained file (inline CSS, no assets) that can be attached to a PR, emailed, or committed as a build artifact.

Package safewrite wraps mutating SQL with agent-grade guardrails: it runs every write as a dry-run first, reports the exact blast radius (rows affected), snapshots the database before applying, and turns lock failures into structured remediation an agent can act on instead of a raw error.

Package snapshot provides point-in-time backups for local SQLite files — the file-superpower moat extended beyond D1 Time Travel.

Package team adds person-scoped, local-first access control on top of the audit operator.