[thekevinbot]

Fixes #962

A [[table]] entry gains a required name. dirsql stops tokenizing the
CREATE TABLE head of ddl to learn the table name — that was bespoke
SQL-as-text parsing, and SQLite's own catalog answers the question natively.

[[table]]
name    = "messages"
glob    = "sessions/*/messages/*.json"
on-file = "..."
ddl     = "CREATE TABLE messages (session TEXT, idx INT, role TEXT, text TEXT)"

What changed

• Config: name is required on [[table]] (missing → Missing required field 'name' in [[table]] entry; blank → EmptyField). Duplicate-table detection across composed configs compares name keys.
• Every call site that keyed on the parsed name now reads table.name: the build path, compile_matcher, compute_glob_config_hash, and the config merge.
• db::parse_table_name is deleted, along with the strip_keyword_ci / parse_identifier / skip_ws_comments tokenizer behind it and its ~165 lines of unit tests. Db::create_table now takes (name, ddl). validate_identifier stays — name is spliced into format!()-built INSERT/DELETE SQL, so it remains the injection guard.
• Existence check via the catalog: after create_table, table_exists asks pragma_table_list whether name is in main. No row → DirSqlError::TableNotCreated, raised before any file is ingested and carrying the config-entry prefix.
• SDK builders take the name in all three SDKs: Table::new(name, ddl, glob, on_file) (and try_new / strict), Table(name=..., …), TableDef.name. PARITY.md updated.
• TypeScript parseTableName(ddl) is removed — it wrapped the core parser that no longer exists. Its napi export and colocated tests go with it.

Quoted (CREATE TABLE "messages"), schema-qualified (main.messages) and IF NOT EXISTS DDL keep working with a plain name = "messages": SQLite records the bare identifier in its catalog, so nothing has to interpret the DDL text.

Parity: restoring/holding, not drifting — all three SDKs gain the name argument in this PR, so no follow-up issues are needed.

Manual verification

Against the release binary over a real temp dir (data/a.json holding [{"id":"one"},{"id":"two"}]):

$ dirsql query "SELECT id FROM messages ORDER BY id" -c .dirsql.toml
[{"id":"one"},{"id":"two"}]                                          # exit 0

$ # with the `name` key removed
dirsql query: failed to load config: config error: Missing required field 'name' in [[table]] entry   # exit 1

$ # name = "messages" over ddl = "CREATE TABLE notes (id TEXT)"
dirsql query: failed to load config: table 'messages': its `ddl` ran but created no
table called 'messages'. Set `name` to the table the `ddl` creates.   # exit 1

$ # all three forms, each with a plain name = "messages"
CREATE TABLE \"messages\" (id TEXT)        -> [{"n":2}]
CREATE TABLE main.messages (id TEXT)       -> [{"n":2}]
CREATE TABLE IF NOT EXISTS messages (id TEXT) -> [{"n":2}]

Red/green

2c9c3f3 pushed the failing suites alone; Rust CI run 32398345357 went red on exactly their assertions (unknown field \name`, and a nameless entry loading fine), not on anything incidental. 706ed09` turns them green.

E2E Verification

• Ran e2e suites locally for every affected SDK
• Python SDK e2e: pass
• TypeScript SDK e2e: pass
• Rust core e2e (if applicable): pass
• packages/python/e2e-attestation.json refreshed if packages/python changed
• packages/ts/e2e-attestation.json refreshed if packages/ts changed
• Command(s) run:
  • cargo test --manifest-path packages/rust/Cargo.toml --features cli --lib --tests
  • cd packages/python && uv run python -m pytest tests/e2e/ -q
  • cd packages/ts && pnpm test:e2e
• Result summary: Rust 667 lib + all integration/e2e targets pass; Python 108 unit / 26 hermetic / 105 binding / 32 e2e pass; TypeScript 105 unit / 17 hermetic / 95 binding / 16 e2e pass.

Changelog / Migrations

• Changelog fragment added under packages/<pkg>/changelog.d/ for each changed package
• Migration fragment added under packages/<pkg>/migrations.d/ — breaking config + API change, all three packages