Exercise 1: A Simple Migration and migrate status — Possible Solution
=======================================================================

In schema.prisma, add to the Post model:

  excerpt String?

Then:

  $ npx prisma migrate dev --name add-post-excerpt
  $ npx prisma generate

The new migration.sql contains a single statement along the lines of:

  ALTER TABLE "Post" ADD COLUMN "excerpt" TEXT;

Because the field is optional, existing posts simply get NULL, so no
data is at risk and no reset is needed.

  $ npx prisma migrate status

reports how many migrations were found in prisma/migrations and that
the database schema is up to date. If a migration existed in the
folder but hadn't been applied, it would be listed as not yet applied.

If you forgot `prisma generate`:

The database would have the new column, but the generated client would
still describe the old schema. TypeScript would reject code that uses
`excerpt` ("'excerpt' does not exist in type ..."), and results
wouldn't include it in their types. Running generate fixes it — and in
Prisma 7 it must be run by hand after each schema change.

WHY THIS WORKS AS AN ANSWER
------------------------------
It shows a safe, additive change, explains migrate status, and
describes the most common Prisma 7 mistake — forgetting generate. The
exact status wording varies between versions.