[qiantingwl]

Summary

Implement opt-in, operation-specific proxy selection for account balance, check-in and rewards, independent of model/account proxy settings.

Host changes

• Authenticated maintenance-policy API and web/desktop Network Proxies settings card.
• Direct / automatic / fixed entrance selection, using the existing native proxy pool.
• Current defaults inherited by newly registered/imported accounts without writing account proxy bindings.
• Global/per-entrance concurrency, shared randomized launch spacing, bounded queue, per-account serialization, successful-balance cache and transport cooldown.
• No direct fallback when a configured proxy is unavailable; no automatic replay of potentially committed reward/check-in mutations.
• Versioned capability negotiation: unsupported plugins fail closed with an upgrade-required message.

Compatibility

Default-off. One compatible host upgrade is required; an old host cannot acquire the new management API solely through a plugin update. Afterwards additional providers can implement the same optional capability in plugin updates. The initial provider implementation covers Raccoon and Loomy.

An external HTTP/SOCKS5 aggregation service remains one native pool entrance; its internal downstream rotation is separate from host entrance rotation. No retired subscription subsystem is restored. No real subscription URLs, credentials, account exports, deployment addresses or logs are included.

Verification

• Host production binary builds successfully.
• Web/desktop islands TypeScript check and production build pass.
• 8 tests execute the actual production scheduler module in a small harness (only persistence/proxy-pool adapters are stubbed).
• 28 end-to-end checks run the real host + plugin in a loopback-only network namespace with synthetic accounts and upstream/proxy servers: authentication, validation, persistence across restart, all modes, balance/check-in/rewards, new-account inheritance, unchanged account.proxy, and disable-to-legacy behavior.
• Companion plugin: 2 SDK tests and 48 real-process RPC fixture cases pass, including before/after model-plan comparison (excluding per-request trace IDs).
• The upstream beta baseline's full host --lib test target does not compile: existing RequestQuery initializer fields in api/pipeline.rs and send_with_retry test arity in core/upstream/provider_loop/tests.rs. Reproduced on the unmodified baseline; not fixed in this feature PR. Production build and isolated tests are reported separately, not as a full-suite pass.

Boundaries

No live production deployment, real account claims, paid model requests or claims of real-provider availability. No dedicated mobile settings UI yet; use the web panel. No version bump, tag or release. See docs/maintenance-egress.md and the reproducible test scripts.

Companion provider PR: ProvidersPlugin/Agent2Providers#33

🤖 本条回复由 AI Agent 生成
Generated by an AI agent.