4612ee9464
Every other content-returning browser tool entry point (browser_snapshot/vision/console/eval, and click/type/press via _blocked_private_page_action) re-checks window.location.href against the private/internal/cloud-metadata floor after the page could have changed -- because a redirect chain or client-side navigation can land on an address the initial browser_navigate preflight never saw. browser_back was the one navigation-triggering entry point missing this: it called _run_browser_command(..., "back", []) and returned the resulting URL straight to the model with no re-check. On a cloud/CDP (non-local) backend, if browser history contains a private/internal address (e.g. a prior redirect touched an internal host), browser_back would navigate the live browser there and hand the URL back to the model with no guard -- the exact class of gap the private-page guard exists to close, just on the one entry point it hadn't reached yet. Re-check happens after the navigation succeeds (not before, unlike click/type/press) since it's the resulting page -- not the one being left -- whose safety matters. A failed back navigation (no history) skips the check entirely since nothing changed. Verified live: the new regression test fails (returns the private URL instead of a blocked payload) on the pre-fix code and passes after.