Expose Arena ELO sync in feature flags (#3821)

Adds ARENA_ELO_SYNC_ENABLED to the Dashboard Feature Flags registry (DB-overridable),
routes Arena ELO startup/status checks through the shared feature-flag resolver while
preserving the existing env fallback, and refreshes env docs (adds the missing
STREAM_READINESS_TIMEOUT_MS example) so env/doc sync stays green.

Integrated into release/v3.8.25.

Co-authored-by: R.D. <rogerproself@gmail.com>
This commit is contained in:
Randi
2026-06-14 07:45:02 -04:00
committed by GitHub
parent ebf06b5e6c
commit 31e4e46ef9
11 changed files with 143 additions and 41 deletions

View File

@@ -88,9 +88,10 @@ describe("Pipeline Wiring — instrumentation-node.ts", () => {
it("should initialize Arena ELO sync on the live startup path (on by default, opt-out)", () => {
// The Next standalone runtime boots through instrumentation-node, NOT server-init.ts.
// The Arena ELO sync (which feeds the Free Provider Rankings page) must be wired here,
// or it never runs in production regardless of ARENA_ELO_SYNC_ENABLED.
// or it never runs in production. initArenaEloSync self-gates through the feature flag
// resolver so ARENA_ELO_SYNC_ENABLED and dashboard overrides still apply.
assert.match(src, /initArenaEloSync/);
assert.match(src, /ARENA_ELO_SYNC_ENABLED !== "false"/);
assert.match(src, /const started = await initArenaEloSync\(\)/);
});
it("should initialize pricing + models.dev sync on the live startup path (self-gated, opt-in)", () => {