fix(kimi): point kimi-web to international www.kimi.ai

[MeRezaRezaei]

Summary

• kimi.com is the China-region endpoint; from outside China it is not reachable, so the kimi-web consumer chat provider must default to the international www.kimi.ai (Connect-RPC API base URL + top-of-page website link).
• The kimi-coding / kimi-coding-apikey partnership affiliate links intentionally stay on kimi.com (that plan is sold in the China region). Only kimi-web switches to kimi.ai.
• Refreshes the stale comment in src/lib/providers/validation/webProvidersA.ts (kimi.com -> kimi.ai).
• Updates the matching unit tests (executor-kimi-web, kimi-partner-aff-links, token-health-check-kimi, providerPageHeaderKimiPartnerLink).

Scope

8 files, 28 insertions / 38 deletions — kimi-web domain correction only, no unrelated changes.

Verification (all clean)

• prettier --check on all 8 files ✅
• eslint on all 8 files (exit 0) ✅
• typecheck:core ✅ · typecheck:noimplicit:core ✅ · check:cycles (no cycles) ✅
• Affected kimi tests pass: 3 node:test files + 1 vitest UI test ✅

Note

⚠️ base-red inherited: #9985 — release/v3.8.50 is red per the nightly release-green check. That is pre-existing and not introduced by this branch; not fixed here per project policy.

[diegosouzapw]

Thanks for this — the alignment work is clean and the kimi tests pass (25/25) on the head. One note to keep the fix coherent: since the chat executor already targets www.kimi.ai, the consistency sweep is incomplete in two live surfaces that still reference kimi.com:

• src/lib/providers/validation/webProvidersA.ts:43 still probes https://www.kimi.com/api/user (and the Origin/Referer at :47-48 plus the error strings at :29/:38/:58/:72 say kimi.com). If www.kimi.ai is the international endpoint, the credential-validation probe and its messages should point there too (ideally reusing getKimiWebBaseUrl()/the KIMI_WEB_BASE_URL override so validation and chat agree).
• open-sse/services/tokenExtractionConfig.ts:192-194 still lists the kimi.com login URL and .kimi.com cookie domain for the token-extraction guide.

[MANDATORY] Please update these so the whole kimi-web surface is on one domain, and record a short VPS live check (Hard Rule #18): after logging in at www.kimi.ai, confirm both the Connect-RPC chat endpoint and GET /api/user answer on www.kimi.ai rather than redirecting to kimi.com — the prior comments in #7531/#10944 asserted the opposite, so a live confirmation makes the flip trustworthy. Minor/optional: the kimi-web website field drops the aff=omniroute attribution (web-cookie.ts:326) — just confirm that removal is intended.