Every screen checked before you hand back the keys

Text anti-aliasing shifts by a pixel between machines. A shadow renders a shade lighter. Most screenshot tools flag all of it, and the team learns to click Approve without looking.

Walkaround renders both sides on the same browser build, then ignores changes thinner than the clear coat. You never see them, so you keep looking at the marks you do see.

On the Home screen: 1,204 pixels in the banner headline moved by one pixel. Buffed out, not reported.

Someone renamed a design token and the Add to cart button went from blue to violet on one screen only. Nobody broke anything, but nobody meant it either.

Walkaround circles it, names the property that moved, and asks one question. If you meant it, sign it off and it becomes the new paint. If not, it goes on the pull request as a comment.

A longer product name pushed the price onto a second line, and the Remove link slid under it. It only happens at 390 wide, on the one screen with the longest name.

Primer marks are layout: spacing, wrapping, alignment. Walkaround tells you how far the thing moved and at which widths, so you can see it is a phone problem before you open a phone.

On Checkout at 390 wide, the Pay button is gone. A new sticky chat bar landed on top of it. This is the mark that costs money.

Bare steel stops the build. Walkaround posts the before and after on the pull request, fails the check, and will not let it merge until the panel is fixed or someone with the keys signs it off by name.

Every team draws the line somewhere else. A design system team wants to hear about a color. A team shipping hourly only wants bare steel. Set the gauge once per project, and marks above the line are logged but never block a merge.

Flip the key tag to Return, then move the gauge.