Exercise 1: The Feature Behind the Compound where Clause — Possible Solution
====================================================================

WHY update() ORDINARILY CAN'T FILTER ON status
------------------------------
Prisma's update() method normally requires its where clause to
uniquely identify exactly one record - only fields marked @id,
@unique, or part of a compound @@unique/@@id constraint are accepted.
status is a plain, non-unique field, so on its own it isn't a valid
where condition for update() at all.

THE FEATURE THAT MAKES where: { id, status: "active" } WORK
------------------------------
Combining a non-unique field (status) alongside the actual unique
identifier (id) in the same where clause is a specific, named Prisma
capability. It began life as a preview feature called
extendedWhereUnique, introduced in Prisma 4.5.0, and was promoted to
stable - no preview flag required - as of Prisma 5.0.0. Since this
course is built against a current Prisma release, well past version 5,
this works directly with no feature flag needed in the schema.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies that this isn't ordinary update() behavior but
a specific, named, versioned Prisma feature, and it correctly states
which version made it stable - rather than describing the compound
where clause as if it were simply how update() always worked.