6 commits

Author	SHA1	Message	Date
bot-backend	a52b9d07cf	fix(tradein/browser): повтор evaluate на той же странице — гонка случается ПОСЛЕ load (#2676) (#2721)	2026-08-06 10:18:14 +00:00
bot-backend	1ba1a55770	fix(tradein/browser): гонка «execution context destroyed» — восстановимая, ретрай без relaunch (#2676) (#2716)	2026-08-06 09:44:23 +00:00
lekss361	ca473a0012	feat(proxy-pool): P4 — browser dynamic pool-proxy (acquire→/fetch→relaunch) + orchestration wiring, ship-dark (#2164)	2026-07-02 19:20:29 +00:00
Light1YT	2687f75b92	fix(tradein-browser): in-page fetch retry + configurable settle for /fetch-json (#1917) ... First XHR after goto(origin) intermittently hit "NetworkError when attempting to fetch resource" (page net stack/anti-bot not ready), healed only by the outer re-navigation retry (~30-45s/house in the house_imv_backfill, #562). _fetch_json_once now: - settles FETCH_JSON_SETTLE_MS (default 1200, was hardcoded 500) — fewer first-fails; - wraps the in-page fetch() in a JS retry loop (FETCH_JSON_INPAGE_RETRIES default 1, FETCH_JSON_RETRY_DELAY_MS default 800) that retries ONLY on network throw, never on HTTP status (4xx/5xx short-circuit, caller decides). An in-page retry costs ~retryDelayMs vs the ~30-45s outer re-navigation. Last error re-thrown — outer crash-retry contract intact. /fetch (SERP) path untouched. +2 tests (settle ms, retry params). Refs #1917, #562	2026-06-27 05:30:16 +05:00
bot-backend	e03c810306	feat(tradein-imv): route IMV backfill через BrowserFetcher.fetch_json за dormant-флагом (#915 Stage 3) (#1916)	2026-06-26 09:54:28 +00:00
bot-backend	d479edeb3f	feat(tradein-browser): additive POST /fetch-json + BrowserFetcher.fetch_json (#915 Stage 2) (#1915)	2026-06-26 09:30:35 +00:00