Proxy toggle can't explain search result changes; compare run inputs first

A developer comparing search datasets considered rerunning with a different proxy setting to explain changed results. The article argues this is a flawed experiment, since every run uses a managed proxy regardless of the proxyConfiguration value, and result rows carry no proxy telemetry. It recommends separating changes in the submitted search, the observed results, and transport assumptions before spending on more runs. A table maps common symptoms, such as market mismatches, query coverage gaps, and result window differences, to the evidence that distinguishes them. It also suggests inspecting archived run manifests and confirming runs succeeded before drawing conclusions.