[Bl0ck154]

Safe staged integration — NOT for production

Built from the upstream-first staging branch (#51), no changes to the existing production branch or running VPS. This is a stacked draft PR; do not merge into production. The new branch is a source migration candidate only, not a tested release.

Included

• Cherry-merge upstream contribution feat(auth): add per-API-key ordered connection preference cheaper-inference/OmniRoute#13102 for API-key-specific preferredConnections ordering, UI, credential selection and regression tests (source of 91-file change, including translations).
• Resolve all 3 locale conflicts (en, pt-BR, vi) by preserving existing removeSelection and new preferredConnections* labels. All JSON parsed successfully.
• Add explicit compatibility metadata to rehome the historical fork 170/api_key_preferred_connections and 194/api_key_preferred_connections ledger entries to canonical 213/api_key_preferred_connections.
• Restore official 194_proxy_logs_attempt_timing invariant by checking both proxy_logs.headers_ms and first_chunk_ms; 213 checks api_keys.preferred_connections. This matters because the live fork database is known to contain the legacy 194 marker and no official timing columns (see docs/maintenance/UPSTREAM_PARITY_GAP_AUDIT_20261024.md on production).
• New tests/unit/api-key-preferred-migration-bridge.test.ts exercises fresh database, previously migrated database and historical 170/194 markers plus idempotent repeat boot, using synthetic in-memory SQLite.
• Preserve preexisting staged URL speech, Antigravity 504 and Codex paid-plan filtering (Draft: upstream-first patch migration — phase 1 (speech, Antigravity, Codex) #51). src/sse/services/auth.ts retains the Codex eligibility import.

Checked so far

• Git 3-way merge completed, no unresolved conflicts or staged whitespace problems (git diff --check).
• Three resolved i18n files parse with Python JSON.
• All changes committed and pushed from an isolated worktree, no local build/tests on production VPS.

Required before integration

• Off-host focused Node/Vitest tests, full core typecheck and relevant CI.
• Run synthetic migration matrix with real runMigrations(); verify legacy 170/194 and new 213 ledgers, partially migrated states, rollback/backup safeguards and repeat startup.
• Confirm previous production custom account priority, allowedConnections boundary, quotas/cooldown, model eligibility, forced/leased connections, tenant isolation and concurrency are preserved by newest upstream.
• Port the fork-only preferredFallbackAvailable metadata, preferred 5s/12s Gemini 3.8 timeout behavior, and the newer hot DB/API settings from fork feat(api): adaptive Antigravity resilience, model quarantine and hot timeouts #47 separately. This branch includes only the contribution feat(auth): add per-API-key ordered connection preference cheaper-inference/OmniRoute#13102 and DB bridge, not advanced feat(api): adaptive Antigravity resilience, model quarantine and hot timeouts #47/fix: prevent Antigravity timing metrics from leaking on ignored responses #49 runtime quarantine/telemetry.
• Validate all preserved custom changes, including Order Forge images and account-specific telemetry, before any production merge.

Keep #51 and this PR draft, no deployment or migration against live DB.

[Bl0ck154]

2026-10-24 validation update: isolated stacked branch integration/preferred-bridge-20261024 at fd66e6b70f30bdf2d4f363f7b5560af86518e242 passed API Route Typecheck (GitHub Actions, completed successfully). A manual full CI run has been requested against the exact same SHA; it was in progress at last observation. This does not establish that migration cases or full CI passed yet. No build/tests ran on the production VPS, and production DB/service remain unchanged.

[Bl0ck154]

2026-10-25 staged progress: ce54587190c710471e9b78975606e27a4bb76e37 ports soft preferred Antigravity 5s default / Gemini 3.8 12s header-timeout caps into the new upstream executeWithUpstreamStartTimeout chain (both primary and retry), keeping explicit pins/singletons/other providers unchanged and preserving stricter connection/model timeouts. Production-style cached resilienceSettings.antigravity numeric overrides (500–120000ms) remain readable without introducing another settings DB query. Credential selection now emits selectedByApiKeyPreference plus preferredFallbackAvailable only when a second currently eligible account survives filtering. Added unit + timeout behavior tests and a targeted manual GitHub Actions gate in .github/workflows/api-route-typecheck.yml. Hosted run 40132837056 completed SUCCESS at exact SHA ce54587190, including the new preferred routing/legacy SQLite synthetic tests and API route typecheck. The previous all-project run 40117341814 at SHA fd66e6b failed several broad gates (notably npm audit dependency alerts, 66+ i18n untranslated ratio errors, unrelated Codex/image/UI regressions), so the draft remains NOT release-ready. No production restart, database mutation, local build, package promotion or change to production.