Keeping the automated persona checks trustworthy

Every change to the platform is now checked by an automated browser that signs in as each of the six roles and opens their dashboard. That check is only worth having while it keeps up: rename a page or move a menu entry, and it starts failing for reasons that have nothing to do with whether the product works.

Repairing it used to mean guessing at what a deployment looked like. It no longer does. The check can now be repaired by opening the deployment in a real browser, signing in as each role, looking at the pages, and correcting the check from what was actually on screen — in one pass, against the same environment the check runs against.

The check itself is unchanged, and it stays the thing that decides whether a change is safe. Looking at a deployment is how the check gets fixed; it is never how a change gets approved.