chore(database): delete the migrations nothing applies

[Artmann]

Closes #104.

drizzle/ held one generated migration and its snapshot, and drizzle.config.ts told drizzle-kit where to write the next one. Nothing has ever run either — tables are created at boot by createTables in src/database/tables.ts and then reconciled column by column by reconcileColumns, and no module under src imports drizzle's migrator.

Nine months of that is visible in the drift, and it is total. The committed SQL creates chats, messages, and providers: three tables that exist nowhere else in the repository, left over from an API that was added the same week and has since gone. It creates none of the five that are real — databases, queries, settings, spans, worksheets. There is no overlap at all. Anyone reading drizzle/0000_graceful_whizzer.sql for the schema learns nothing true.

CONTRIBUTING.md sent them there: its "Database Migrations" section said to run npx drizzle-kit generate after a schema change, so following the documented process moved the tree further from the truth than ignoring it did. That section is struck rather than rewritten — CLAUDE.md already describes how DDL actually works, and #69 tracks saying so in CONTRIBUTING.md.

Deleted: drizzle.config.ts, drizzle/0000_graceful_whizzer.sql, drizzle/meta/0000_snapshot.json, drizzle/meta/_journal.json, and the drizzle-kit devDependency that existed only to write them. drizzle-orm stays — it is the query builder the whole backend runs on, and deleting the generator is not deleting the ORM. Three comments that named the deleted files are corrected (src/database/path.ts, CLAUDE.md's DDL paragraph, scripts/seed-config.ts).

The guard

unappliedMigrationTooling in src/database/migration-tooling.ts answers one question: which artifacts and generator packages are kept with nothing that applies them. A migration system is fine and no migration tooling is fine; one half without the other is the defect, so that is the only shape it fails on. The repository case feeds it what it finds in the tree rather than a list written today — tracked paths whose components match migrationPatterns.artifact, manifest entries matching .generator, source files importing .migrator.

Artifacts are recognised at any depth, because drizzle-kit writes where its config's out points it and that is routinely somewhere under src. A folder whose name says nothing about drizzle — out: './migrations' — stays invisible, deliberately: reading every .sql file in the repository to guess whether it was generated is worse than the gap, and the pair is caught anyway, because nothing generates into that folder without a drizzle.config.*.

The three patterns live in the module rather than inline in the test, because they decide whether the guard ever fires and the guard cannot check them. On a tree with nothing left to find, a pattern that recognises too much and one that recognises too little produce the same empty, passing answer. So they are checked against the lines they have to tell apart: drizzle.config.ts is an artifact and src is not, drizzle-kit is a generator and drizzle-orm is not, an import or require of drizzle-orm/libsql/migrator is an applier and migrateRows is not — and neither is a comment that merely names the path.

What review changed

The first commit's message claimed "14 mutants, no survivors". That was wrong, and the second commit says so. A fresh-context review reproduced four survivors, and one of them made the guard inert against exactly what it exists to catch:

• The applier pattern matched prose. It was the bare path, so any line mentioning drizzle-orm/libsql/migrator counted as something that runs one — and an applier excuses every artifact in the tree. A comment in src/database/index.ts reading "nothing here runs drizzle-orm/libsql/migrator", or a sentence in the guard module's own documentation explaining what an applier looks like, switched the check off for the whole repository. The pattern now requires from or require( and a quoted specifier.
• Nothing asserted that there was no applier. An empty answer has two causes and only one of them is this repository's. The precondition is its own case now, so anything that registers as an applier fails loudly instead of quietly satisfying the check below it.
• Artifacts were only recognised at the top of the tree, so a folder generated under src was invisible. migrationArtifactPath is a named, tested function now.
• The non-vacuity check asserted a filename, not a property. leavesItsOwnFixtureOut named this one test file, so narrowing the exclusion to it alone survived. It is leavesEveryTestFileOut now, and both halves of that case read one tracked-file list rather than walking twice.

That last shape is why the caution is here at all: the very first version of this test quoted 'drizzle-orm/libsql/migrator' as a fixture while sitting under src, so the guard's own test was the applier that excused every artifact in the tree — it passed with the whole drizzle/ folder restored.

Mutation testing after the fixes: 22 mutants, no survivors — restoring each artifact, restoring the devDependency, committing a generated folder under src/database/, ignoring the appliers, returning either half of the answer alone, returning it unsorted, widening or narrowing each of the three patterns, flattening migrationArtifactPath to the top of the tree or to nothing, emptying each of the three walks, and four compound ones that restore the config while switching the applier scan off.

Two things the review raised that are deliberately not here

• todo.md:115 names the deleted config. It is a checked-off item whose "Fixed:" line already records what actually happened; editing it rewrites a record of the past rather than correcting a live instruction.
• .claude/settings.local.json holds a drizzle-kit permission entry. It is a local, gitignored-by-intent allowlist belonging to whoever's checkout it is, not repository state.

Two NITs are noted and not taken: the collection-error message wording, and whether this file belongs in the backend (node) project rather than renderer (jsdom) given it shells out to git.

Gates

Gate	Result
tsc -p tsconfig.backend.json	exit 0
tsc -p tsconfig.renderer.json	exit 0
prettier --check	clean
eslint	0 errors, 0 warnings on touched files
vitest	1435 passed, 1 failed — sqlite-adapter.test.ts Windows path, pre-existing on main

[github-actions]

React Doctor found no new issues. 🎉

_{Reviewed by React Doctor for commit 45c1c49.}