Add SQLite support

[oyvindberg]

Summary

• Wires SQLite into typr as a first-class dialect alongside PostgreSQL, MariaDB, DuckDB, Oracle, SQL Server, and DB2 — using the xerial sqlite-jdbc driver and foundations-jdbc's SqliteTypes/SqliteConfig.
• New db.SqliteType ADT, SqliteAdapter codegen, internal/sqlite/ metadata package (sqlite_master + PRAGMAs), CLI plumbing end-to-end (ParsedSource, ConfigToOptions, Generate, MetaDbFetch, ConnectionTest, TUI screens), config schema entry, and three new tester projects.
• New contributing guide at site/docs-typr/contributing-add-a-dialect.md distilling the touch-point checklist learned from this work — so the next dialect is faster.

Why

SQLite is the most-deployed database on earth and an obvious target for an embedded-DB code generator. foundations-jdbc RC6 now ships the full SqliteTypes catalogue, codecs, and SqliteConfig (in-memory + file-backed); the typr work is to wire it through the codegen.

What changed

Core

• typr-dsl: Dialect.SQLITE (double-quote idents, IS / IS NOT null-safe equality, standard LIMIT/OFFSET, CAST()).
• db.SqliteType ADT covering every concrete type SqliteTypes exposes.
• DbType.SQLite + product/driver detection + TypoDataSource.hikariSqlite{,InMemory,File}.
• SqliteAdapter (codegen layers 1–5): supportsReturning=true, ON CONFLICT upserts, no native arrays, no schemas.
• internal/sqlite/: SqliteJdbcMetadata, SqliteMetaDb (raw JDBC against sqlite_master + PRAGMA table_info/pragma_foreign_key_list/pragma_index_list), SqliteSqlFileMetadata (sqlglot bridge), SqliteTypeMapperDb.
• Dispatch arms in MetaDb, InstanceRequirements, generate (incl. precise-types), DbLibFoundations, TypeMapperJvmNew, TypeMatcher, TypeCompatibilityChecker, ComputedTestInserts, SqlFileReader, TypeSuggester.

CLI / TUI

• ParsedBoundary/Source.Sqlite, convertSqliteBoundary, fetchSqliteBoundary, generateSqliteForOutput (with a small ;-aware splitter — see "Subtleties" below).
• MetaDbFetch, ConnectionTest, LoadedSource, plus the TUI screens (SchemaPicker, SourceForm, SourceList, MainMenu).

Config

• typr-config.schema.json: added sqlite to the boundary type enum, added sqliteBoundary $def.
• Regenerated SqliteBoundary.scala via bleep run generate-config-types.

Test infrastructure

• sql-init/sqlite/00-schema.sql exercises every affinity, plus composite PK, composite FK, UNIQUE, views, precision_types[_null].
• sql-scripts/sqlite/*.sql: five parameterised queries.
• testers/sqlite/{java,kotlin,scala}/ with SqliteTestHelper and BasicCrudTest. All 10 tests pass (4 Java / 3 Kotlin / 3 Scala).
• bleep.yaml: three tester project entries + org.xerial:sqlite-jdbc:3.46.1.3 added to typr-codegen.
• typr.yaml: new sqlite boundary + sqlite-java / sqlite-kotlin / sqlite-scala outputs.

Docs

• site/docs-typr/contributing-add-a-dialect.md: walkthrough of every file you need to touch to add a new dialect, in roughly the order to touch them.

Subtleties worth knowing

• Multi-statement loading: xerial sqlite-jdbc's Statement.execute() runs only the first statement of a multi-statement string, so foundations' connectionInitSql doesn't load the whole schema. The typr CLI and the test helpers each split on ; (outside '...' literals, ignoring -- ... comments) before executing.
• No schemas: SQLite has one namespace per database. convertSqliteBoundary forces SchemaMode.SingleSchema("main"); the adapter's DDL helpers return SQL comments instead of CREATE/DROP SCHEMA.
• Type affinity vs declared type: SQLite stores any value in any column. The type mapper combines (a) exact aliases from SqliteTypes (BIGINT/INT8/VARCHAR/CLOB/...) and (b) SQLite's affinity-substring fallback so VARYING CHARACTER / DOUBLE PRECISION etc. still resolve sensibly.

Test plan

• bleep compile — full tree green
• bleep fmt — no churn
• bleep run typr -- generate --source sqlite — generates all three language outputs from :memory: SQLite
• bleep test testers/sqlite — 10/10 pass (Java: BasicCrudTest 4 ✓, Kotlin: BasicCrudTest 3 ✓, Scala: BasicCrudTest 3 ✓)
• Reviewer to spot-check SqliteAdapter vs DuckDbAdapter to confirm the affinity/CAST/upsert mapping is what we want
• Reviewer to confirm the ;-splitter in Generate.scala/MetaDbFetch.scala/test helpers is acceptable, or wants a foundations-side fix instead

🤖 Generated with Claude Code