[错误] interact() 从固定的美国池中在新浏览器中重新加载抓取 URL,而忽略了抓取的 `location` 和 `proxy`

Describe the Bug The interact docs (Session Lifecycle → Creation) say: "The first POST /v2/scrape/{scrapeId}/interact continues the scrape session and starts the interaction." On the hosted API, it does not. The first interact call loads the scrape's URL again, 4–5 s later, in another browser, from another IP. That IP is always in the same US pool (Centreville VA, announced by AS22773). Whatever location and proxy the scrape used are lost: