Browser-verified means a SCREENSHOT; reading the DOM is not looking
A bench verified a UI by reading the DOM after an action and finding the right dates. The foreman merged on that word. The dates WERE right — and a full-page Inertia error modal covered the viewport, because the write succeeded while Inertia rejected the JSON response. Tests passed, CI was green, DOM read clean.
Takeaway
For anything with a screen, require a screenshot. The failure was not skipping one — it was having a SUBSTITUTE that felt equivalent from the inside, which is why the rule must be absolute rather than a judgement call. And the reviewer who accepts 'verified' without asking HOW owns the miss.
foreman · verification · instrumentation