Krishna lokhande 671aa3d80d fix(oauth): treat Kiro social poll status as alias of error for pending states (#10620) ...

Kiro's device poll endpoint reports progress in a `status` field (e.g.
`authorization_pending`), but `classifyKiroSocialPoll()` only inspected
`data.error`. This caused every pre-authorization poll to fall through to
the terminal `invalid_token_response` error, making social login impossible
for Kiro AI and Amazon Q via Google/GitHub.

Changes:
- Add `status` field to `KiroSocialPollData` type
- Update `classifyKiroSocialPoll()` to check `data.status` as fallback
  for `data.error` when detecting pending states
- Add tests covering `status`-based pending detection and precedence

Closes #10618

2026-08-18 10:53:29 -03:00

..

_helpers

…

_setup

…

benchmarks

…

boundary

…

e2e

fix(providers): validate bailian-coding-plan against the Token Plan host (#10634)

2026-08-18 05:51:34 -03:00

fixtures

feat(providers): add local ZCode ACP backend (#10184)

2026-08-16 00:13:36 -03:00

golden-set

…

helpers

fix(sse): close the synthetic keepalive reasoning item + harden output_index allocation (#10330)

2026-08-16 00:15:38 -03:00

homolog

…

integration

feat(providers): complete Jina + Gemini Embedding 2 multimodal via OmniRoute (#10581)

2026-08-18 10:52:43 -03:00

live

…

llm-security

…

load

…

manual

…

security

…

snapshots

Remove/mimocode sunset provider (#10186)

2026-08-18 10:49:24 -03:00

translator

…

unit

fix(oauth): treat Kiro social poll status as alias of error for pending states (#10620)

2026-08-18 10:53:29 -03:00

_cp_mock_hook.mts

…

_cp_mock_module.mts

…

_run_dns_guard_test.sh

…

e2e-tool-calls.sh

…

theoldllm-stress.test.ts

…