The browser walk introduced last time had to be started by hand. That made it something you reached for when you already suspected a problem — which is the opposite of when a smoke test earns its keep. In practice it would have been skipped on exactly the changes that most needed it.

It now starts on its own. As soon as a change’s preview is built, the walk signs in as each of the six roles, lands on that role’s home, and visits every page their sidebar offers. The result arrives as a single check next to the others, and the video, screenshots and full trace of every walk are kept for a fortnight — long enough to still be there when someone comes back to a review.

What turns the check red is unchanged and deliberately narrow: a sign-in that does not arrive where it should, a page that errors, a page that comes back empty. It still says nothing about whether a page looks right. And it still only ever reads — it opens pages and looks at them, and changes nothing in the tenant it walks, so two changes being reviewed at once cannot interfere with each other.

A few things it will not do. A change that is still a draft has no preview yet, so nothing runs and nothing is reported — an empty result rather than a quiet pass. The same is true when a change does not touch the part of the platform being walked.

The check is advice for now, not a barrier: it appears on every change and is read alongside the rest, but it does not yet stop anything from being merged. Making it a hard gate is a separate, deliberate step, and it should wait until the walk has a few real runs behind it.