2 Commits

Author	SHA1	Message	Date
backryun	65e0aeda79	[Part 1/3]refactor(qwen): replace legacy Qwen Code and remove OAuth provider (#7866) ... * refactor(cli): remove legacy Qwen Code integration * refactor(qwen): remove deprecated Qwen OAuth provider * feat(cli): rebuild Qwen Code integration for upstream V4 * fix(qwen): clear stale CLI auth on reset * test(qwen): align retired provider coverage * fix(db): renumber qwen-cleanup migration 129 -> 130 release/v3.8.49 tip took slot 129 via #7843 (usage_history_codex_strong_identity, itself renumbered from 128 during the #7838/#7840 base-red cleanup) after this branch forked; renumber remove_unregistered_qwen_data to 130. Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com> --------- Co-authored-by: Diego Rodrigues de Sa e Souza <8016841+diegosouzapw@users.noreply.github.com>	2026-07-20 17:53:04 -03:00
danscMax	858d762918	fix(oauth): repair qwen + codebuddy-cn device-code endpoints (#7517) ... Both device-code providers failed at the upstream request (surfacing in the companion extension as 'ошибка сервера OmniRoute'). Diagnosed by calling the upstream endpoints directly: - qwen: QWEN_CONFIG used the bare host qwen.ai, whose /api/v1/oauth2/device/code and /token paths return 404 Not Found. The working qwen-code device flow lives at chat.qwen.ai (verified: 200 + a valid device_code/user_code). Point both URLs at chat.qwen.ai. - codebuddy-cn: the Tencent state endpoint reads 'platform' from the QUERY string, not the JSON body. Sending it only in the body returned 400 {"code":10001,"msg":"platform is empty"}. Passing ?platform=CLI returned 200 with {code:0, data:{state, authUrl}}. Build the stateUrl with the platform query param (body kept as-is). Validation: live upstream calls returned 200 for both corrected requests (device flow can't be hit from CI). Regression guard: tests/unit/oauth-device-code-endpoints.test.ts.	2026-07-18 11:35:09 -03:00