Canary: use a given endpoint on a fresh Russian session; fix the run check crash

[jehrr]

The daily canary had never completed a live scrape. Two things stood in the way:

1. Endpoint. Building one from AVITO_BROWSER_ACCOUNT_ID with a customProxy gave an endpoint that answered 500 on connect. With the owner's ready endpoint (secret AVITO_CDP_ENDPOINT) the browser connected but, on its own exit, did not clear the firewall's proof-of-work (exit 3). Now, when that secret is set, the job re-points it at a Russian exit — country-ru plus a -proxy-<base64url> segment carrying a session freshly minted on AVITO_PROXY (the format in the Browser API docs) — and gives the captcha solver that same session. Without the secret the old build path is unchanged. Nothing is echoed; .env is 0600 and removed at the end.
2. Run check. ci_checks.py run_check printed {named}, a seller count whose computation had been removed, so the first good run (150 rows) died with a NameError. Fixed, and smoke_test.py now executes run_check on a synthetic good run and a broken one; the old code fails that check (planted-fault control).

Evidence: canary on this branch, run 38890250626 (head 20d2d52): 148 rows, 148 priced, status=complete, stop_reason=completed, exit 0. The rewrite was tested offline with fake values (country replaced, stale -proxy- replaced, endpoint and solver proxy identical, password intact). Offline: smoke_test 686/0, pytest 95, ci_checks --all clean.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CKsd7q25N19WzUZjrAdzx8