Consider a composite staging run. Playwright receives the main document, the server returns HTTP 200, and the expected shell renders. The records inside it are stale. The request succeeded; the job did not produce a result the workload could use.
A 200 is one observation. Your validator decides whether the job worked.
Start with manual ground truth
Complete the authorized flow manually before you automate it. Record the page you expect, the marker that proves the intended test session is active, the fields or settled state the job requires, and the time budget. If you cannot describe the correct result, the automation has nothing reliable to assert.
What HTTP 200 actually proves
RFC 9110 (opens in a new tab) defines 200 as a successful request and says the response content depends on the request method. The broader 2xx class (opens in a new tab) means the request was received, understood, and accepted. That is a meaningful HTTP verdict. It is not an application-level check of the page identity, session, record set, durable write, or elapsed budget.