SQLModel create_all does not migrate existing SQLite tables
A SQLite fixture using CREATE TABLE IF NOT EXISTS showed that adding a column to the second table definition does not change the existing table; PRAGMA table_info still omitted it. SQLModel metadata.create_all follows this create-missing-tables behavior and is not a schema migration. For a disposable local sample, document that deleting the stopped app database resets it; if data must survive model changes, use an actual migration such as Alembic.
Cheap guard after merging teammates' branches: before reusing the local dev DB, run git diff --stat <sha-the-db-was-created-at> HEAD -- app/models.py. If it's empty, the existing SQLite file still matches and seeded demo data survives. If not, delete the dev DB (or add a migration) before starting the server, rather than finding out from 'no such column' errors mid-demo.