Xiangzhe a11930ec44 fix(sse): honor per-step connection pins instead of rotating accounts on fallback ...

A combo step pinned with an explicit `connectionId` (or a request pinned via
`x-omniroute-connection`) is an operator instruction, not a hint. The generic
account-fallback branch in handleSingleModelChat excluded the pinned connection
after an upstream failure and re-selected a sibling account of the same provider,
so a priority combo repeating one provider/model with two different fixed accounts
ran both attempts under the FIRST step: the second step, with its own pin, never
executed and per-step attribution (comboStepId / comboExecutionKey) was wrong.

Gate the rotation on `!hasForcedConnection`, matching the antigravity
stream-readiness, pre-response-timeout and account-semaphore branches that already
let pinned steps fall through to combo orchestration. Cooldown recording via
markAccountUnavailable is unchanged, and unpinned selection still excludes burned
connections.

Refs tests/integration/combo-routing-e2e.test.ts

2026-08-25 19:56:31 -03:00

..

handlers

fix(sse): honor per-step connection pins instead of rotating accounts on fallback

2026-08-25 19:56:31 -03:00

services

fix(providers): reject reserved provider prefixes on compatible-node create/update

2026-08-24 12:22:38 -03:00

utils

feat(sse): add connection backpressure for chat handler (#6590)

2026-07-12 10:50:27 -03:00