Debezium SQLite Source Connector

A new Debezium source connector that captures row-level changes from a SQLite database and streams them as standard Debezium change events.

>_**This issue tracks the SQLite connector as part of GSoC 2026.**_

## Why a SQLite connector
SQLite is the most widely deployed database engine in the world. It runs inside browsers, mobile and desktop apps, and a growing number of edge and IoT devices, and it is increasingly used as a primary application database. Debezium today has connectors for the large server databases like PostgreSQL, MySQL, SQL Server, Oracle,
and MongoDB, but none for SQLite. That leaves a very common source of data with no standard way to stream its changes. This connector closes that gap. It brings Debezium's normal change data capture pipeline, an initial snapshot followed by continuous streaming of inserts, updates, and deletes, to SQLite.

## Scope for v1

- An initial snapshot of existing table data, then continuous streaming of new changes.
- Standard Debezium features: table and column include and exclude filters, the usual event envelope and source metadata, and offset-based resume.
- The `org.xerial:sqlite-jdbc` driver, no external services. Integration tests run against a temporary database file with no Docker.
- The C extension and its prebuilt native binaries for Linux (x86_64, arm64), macOS (x86_64, arm64), and Windows (x86_64).

## Approach

The connector lives in a standalone repository [`debezium-connector-sqlite`](https://github.com/debezium/debezium-connector-sqlite), built out of tree against debezium-core and bootstrapped from the connector archetype. The work is sliced into small phases, each landing as its own sub-issues and pull requests .

The full design can be found in [DDD-44](https://github.com/debezium/debezium-design-documents/pull/49).