Verify Backend SOP Against DB

Turn a business SOP into a durable backend interface integration test. Keep the test in the target repository so future changes rerun the same contract.

Establish the contract

Write down exact observable outcomes before editing:

• backend entry point and authenticated tenant context;
• selected record ID and response reason;
• rows inserted, updated, or intentionally unchanged;
• counters, messages, audit records, or state transitions;
• negative branches and state changes requiring revalidation.

Treat these as absolute values. Do not settle for “no error”, non-empty output, or approximate counts.

Build the persistent test