test/customers.test.js passes on the baseline schema and fails in all 2 candidate runs. New in every candidate run, absent from the control run: SQLSTATE 23502 (not_null_violation): null value in column "email_address" of relation "customers" violates not-null constraint — statement: INSERT INTO customers (name, email) VALUES ($1, $2) RETURNING id test/orders.test.js passes on the baseline schema and fails in all 2 candidate runs. New in every candidate run, absent from the control run: SQLSTATE 23502 (not_null_violation): null value in column "email_address" of relation "customers" violates not-null constraint — statement: INSERT INTO customers (name, email) VALUES ($1, $2) RETURNING id The previous application version reproducibly fails against the proposed schema, and the failure is linked to a specific schema change. test/customers.test.js: SQLSTATE 23502 (not_null_violation) linked to column_added:customers.email_address by R3 not_null_violation ↔ new NOT NULL requirement. test/orders.test.js: SQLSTATE 23502 (not_null_violation) linked to column_added:customers.email_address by R3 not_null_violation ↔ new NOT NULL requirement.