What this test proves
The read-query benchmark compares mailbox query lanes against their reviewed baseline and preserves the campaign's lane-level verdicts and durability observations.
Evidence layout
The runner writes immutable evidence for read-query-benchmark beneath site/reports/. The JSON payload is the source for case or worker outcomes; the rendered report and envelope provide the public navigation entry.
Changes
The revision sections below are the retained runner-history backfill. Each section records the source revision and its own ordered procedure description.
Flow
Steps
| step | action | observable | evidence |
|---|---|---|---|
| 1 | Execute `baseline` | The named check reports PASS or FAIL at revision `3b61103b` | campaign worker/family evidence |
| 2 | Execute `UDS lane` | The named check reports PASS or FAIL at revision `3b61103b` | campaign worker/family evidence |
| 3 | Execute `TCP lane` | The named check reports PASS or FAIL at revision `3b61103b` | campaign worker/family evidence |
| 4 | Execute `mTLS lane` | The named check reports PASS or FAIL at revision `3b61103b` | campaign worker/family evidence |
| 5 | Execute `durability` | The named check reports PASS or FAIL at revision `3b61103b` | campaign worker/family evidence |