fix(providers): read the SSRF Guard toggle from the dashboard, not only env

[datrixlab]

Summary

• "SSRF Guard" (OUTBOUND_SSRF_GUARD_ENABLED) is a toggle on the Feature Flags page, with requiresRestart: false. Its only reader is the legacy escape hatch in arePrivateProviderUrlsAllowed() (src/shared/network/outboundUrlGuardPolicy.ts), and that reads process.env only. The toggle writes a DB override, which nothing reads.
• The two directions:

env OUTBOUND_SSRF_GUARD_ENABLED	dashboard toggle	page shows	guard mode, before	after
unset	OFF	off, source db	block-metadata	none
false	ON	on, source db	none	block-metadata
false	not set	off, source env	none	none
unset	not set	on, source default	block-metadata	block-metadata

The second row is the one that matters. The page reports the guard as on, while provider validation, outbound fetches (getProviderOutboundGuard) and webhooks run with no private-host checks. feature-flags/route.ts has special cases so that "the dashboard never shows a source that doesn't match actual gate behavior"; this flag has none, so it should follow the generic DB-then-env order.

• Fix: read the DB override first and fall back to env when it is unset or empty. This is the same shape step 1 of the same function uses for OMNIROUTE_ALLOW_PRIVATE_PROVIDER_URLS, and the same order as resolveFeatureFlag(). With no DB override the result is identical to before for every env value.

Related Issues

• Same class as fix(providers): let a dashboard OFF for private provider URLs beat the env opt-in #13323 (a dashboard OFF for private provider URLs that the env opt-in overrode) and [BUG] OMNIROUTE_ALLOW_PRIVATE_PROVIDER_URLS feature flag dose nothing when running electron app. #2575 (DB toggle must win over the env captured at boot).

Validation

• Change type: security / provider URL guard
• Focused tests: the new file plus outbound-url-guard-feature-flag, outbound-url-guard-local-flag, rerank-remote-provider-nodes (28/28)
• Wide run: every unit test file that mentions the outbound guard, feature flags or webhooks (78 files). All pass except feature-flags-doc-sync-static and telegram-keycache-bounded-13165, which fail the same way on a clean release/v3.8.51 on Windows.
• tsc on the changed files (temp tsconfig extending the root one): clean; eslint clean; prettier --check clean
• Based on the current release/v3.8.51
• Production-code change includes a new automated test

Tests Added Or Updated

• tests/unit/outbound-url-guard-ssrf-flag.test.ts (new). Each case clears and restores this flag and both sibling flags, env and DB:
  • a DB ON beats OUTBOUND_SSRF_GUARD_ENABLED=false in env (validation and outbound guards back to block-metadata);
  • a DB OFF opens private URLs with no env var set;
  • the webhook check follows the DB toggle (a 192.168.x webhook is rejected again);
  • an empty DB value leaves env false in effect;
  • env false with no DB override still opens private URLs, as before;
  • nothing set: private URLs stay closed.

With outboundUrlGuardPolicy.ts reverted, the first three fail and the other three pass.

Coverage Notes

• The changed branch is exercised with the DB override set, unset and empty, and with env set and unset.

Reviewer Notes

• Upgrade effect: a DB override that used to do nothing starts to work. Someone who once switched the SSRF Guard off in the dashboard, with no env var, moves from block-metadata to none on upgrade, the same state the env escape hatch already gives. The flag is warningLevel: "info" while "Allow Private Provider URLs" is "caution", and both now reach none. I left the level alone to keep this to the precedence; raising it to "caution" is a one-line change if you want it here.
• The changelog fragment notes the upgrade effect.