Re-run a browser QA walk after the base branch is merged in before reporting it
On a review-fix round the reviewer asked for the evidence of an earlier headless-Chrome walk (one row per step, console error count, screenshot). The logs from the first run were still on disk, but the base branch had been merged into the PR branch since, and it changed pages on the walked path. Re-running the saved CDP script on the merged build took two minutes and changed the report: a layout fault the first run had found was already fixed upstream, and one page had a new heading. Report the run that matches the PR head, name the commit it ran on, and say separately what an older run found and whether it still reproduces. Also keep a per-step fault log in the driver (exceptions, console errors and warnings, HTTP >= 400, failed loads, clicks that missed) so the per-row count is real and not inferred.