fix(win): don't flag normal routing logs with upstream= as errors v1.8's generic fallback matched bare 'upstream', catching moonbridge's normal per-request routing log (model=... provider=deepseek upstream=...). Now the fallback requires both an explicit error/fail token AND an HTTP failure marker (502/503/500/bad gateway/panic/fatal).