mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-14 10:52:17 +03:00
c9a5948b3d
Both reds were inherited from release/v3.8.51 — every production file involved is byte-identical to the base tip. Three PRs merged 2026-09-07 moved or added call sites without updating the golden inventory: - #12867 (d6f315018) extracted the codex 429 / antigravity 422 account rotation out of chatCore.ts into chatCore/providerExecutionPipeline.ts. The managed-lease fence was NOT removed: it crosses the seam as `policy.allowAccountRotation`, still derived from `!managedLease` on both the streaming and the non-streaming leg. The antigravity branch, which had no lease fence at all before the extract, is now gated by the same flag. The two credential-resolution sites moved with it and are called off the injected `connection` context, so countCalls() now also sees that property-access shape — otherwise an extract-to-a-seam refactor would silently drop a credential site out of the inventory. - #12746 (6b587d004) lifted combo.ts's persisted-cooldown connection read into combo/executeTargetGates.ts byte-identically (same site, renamed). - #12805 (c042a5188) added grok-cli reset credits: grokResetCredits.ts already carries isConnectionUnavailableToAuxiliaryActivity() ahead of its lookup, so it joins the auxiliary-isolation source list; the shared reset-credit route reads the connection only to pick a handler (class C). Assertions are pinned tighter, not looser: the single chatCore regex is replaced by both ends of the split fence, and the two rotation-policy sites are counted exactly rather than merely detected.