Thanks @PrinceThummar011. Wave 27 boarded this pull request cleanly on release/v3.8.52 at f8d11c9326. The focused unit tests for the files it touches passed on that combined tree (116 passed in the second run, plus the auto-combo weight tests and the skills characterization tests). Changelog integrity passed. The only file-size finding is executeTargetAttempt.ts, already over its frozen ceiling on the release tip and unchanged by this diff.
⚠️ base-red inherited: #15306Closes#15530
Merged with the owner's 2026-10-10 hold/backlog wave. Reworked to keep frozen files within config/quality/file-size-baseline.json after #16070 ratcheted it down (logic extracted into new modules, no baseline raised). Validated together with #16147/#16112/#16110/#15790 on top of release/v3.8.52: typecheck:core, open-sse and API-route typecheck, eslint on changed files, complexity/cognitive ratchets, changelog-integrity green; 117/117 changed tests; only file-size overrun is the inherited executeTargetAttempt.ts. Warning: base-red inherited: #15306.
Thanks @pacocartones.
Wave 26 boarded this pull request cleanly on release/v3.8.52 at 7a0bb875. The focused unit tests for the files it touches passed on that combined tree. This diff does not push a frozen file past its ceiling.
⚠️ base-red inherited: #15306
* feat(release): nightly version and npm dist-tag resolver for the LTS rail
scripts/release/dist-tag.mjs is the single source of the channel rules in
docs/ops/RELEASE_STRATEGY.md: -nightly.* -> nightly (never latest),
rc/beta/alpha (and any other pre-release) -> next, a stable of an older
major than the highest stable tag -> lts, everything else -> latest, with
the publish guard demoting a non-highest stable to historic.
scripts/release/compute-nightly-version.mjs builds
<core>-nightly.<YYYYMMDD>.<sha7> (UTC, validated semver, all-digit SHA
prefixed with g) for the develop nightly build.
* ci(release): resolve npm dist-tag via dist-tag.mjs and add dormant LTS workflows
npm-publish.yml: tag=auto now goes through scripts/release/dist-tag.mjs, so a
4.0.0-nightly.* build resolves to nightly instead of falling through to the
stable path (where it could claim latest), and a 3.9.x patch published after
the 4.0 GA resolves to lts. Stable 3.8.x keeps latest/historic exactly as
before; nightly and lts join the explicit dispatch choices.
Dormant workflows (never fire until stable/v3 / develop exist):
- forward-port.yml: cherry-pick -x of every stable/v3 commit onto
forward-port/<sha7> from develop, original author kept plus a
Co-authored-by trailer; a conflict opens a draft PR with instructions.
- validate-stable-pr.yml: stable/v3 PRs need a fix|docs|chore(i18n)|
feat(providers) title or the lts label.
- nightly-v4-build.yml: computes <core>-nightly.<date>.<sha7>, runs
build:release + check:pack-artifact, keeps the tarball as an artifact and
publishes --tag nightly --provenance only when vars.NIGHTLY_PUBLISH is true.
tests/unit/release-channel-workflows.test.ts executes the npm-publish resolve
step and the stable-PR check against scratch inputs and pins the dormancy,
permissions and SHA pins of the new workflows.
* feat(api): expose release channel and npm dist-tags on /api/system/version
GET /api/system/version gains two additive fields:
- releaseChannel: latest | next | nightly | lts for the running build,
resolved by src/lib/system/releaseChannel.ts with the same rules as
scripts/release/dist-tag.mjs (parity test in release-channel.test.ts);
- channels: { latest, next?, nightly?, lts? } from npm view omniroute
dist-tags (registry HTTP fallback), cached with the same TTL, single-flight
and refresh semantics as the latest-version lookup (both caches now share
one createCachedLookup helper and are cleared together).
The existing channel field keeps meaning the deployment mode
(npm/source/docker-compose) that the dashboard updater reads, so the shape is
unchanged for current consumers. Documented in API_REFERENCE.md and as an
additive response schema in openapi.yaml.
* feat(server): headless mode gate for dashboard routes and optional boot subsystems
OMNIROUTE_HEADLESS=1 boots only the proxy engine. A single helper
(src/lib/system/headless.ts) drives two gates:
- route gate in src/proxy.ts: /dashboard, /dashboard/*, /home, /home/*
answer 404 {"error":"dashboard disabled (headless)"} before the authz
pipeline; /v1/*, /api/monitoring/health and /api/auth/* are untouched.
- boot gate in src/instrumentation-node.ts: the optional subsystems of the
background block move into OPTIONAL_BOOT_SUBSYSTEMS, started through
startOptionalBootSubsystems() (skipped as a whole when headless); the
free-proxy sync and cloud sync serial steps use skipInHeadless(). No init
code is removed; proxy-core work (token auto-refresh, cooldown recovery,
context-window reconcile, backup schedule) stays inline in both modes.
* feat(cli): omniroute serve --headless sets OMNIROUTE_HEADLESS=1 on the server
The flag reaches the server process through the same child env that
carries --port (applyHeadlessServeEnv). Headless runs skip the automatic
browser open, print 'Dashboard: disabled (headless)' in the banners, and
reject --tray (the tray exists to open the dashboard). New CLI string
serve.headless added to all 67 CLI locales.
* docs(server): headless mode guide and OMNIROUTE_HEADLESS env reference
docs/guides/HEADLESS.md covers what stays on, what is switched off, curl
checks and limits; linked from docs/README.md and the guides nav. The
variable is documented in .env.example and docs/reference/ENVIRONMENT.md.
* fix(headless): keep the memory subsystems running in headless mode
Memory is cross-cutting to the request pipeline (/v1 injects and queries
memory), so memory-backends and memory-decay-sweep leave the
OPTIONAL_BOOT_SUBSYSTEMS table and return to the inline core boot path in
registerNodejs() (same position as on the base branch), running in both
modes. The test now asserts both stay out of the headless-skipped table and
start inline; HEADLESS.md lists memory as staying on.
An opt-in flag removes combo steps pinned to models a successful catalog sync no longer lists, and never empties a combo.
⚠️ base-red inherited: #15306
An opt-in nadir combo strategy asks Nadir which model the last user turn needs, and leaves the connection choice to the existing rules.
⚠️ base-red inherited: #15306
Thanks @Junior-HJ! This adds CodeBuddy international (codebuddy-intl / cbai), splitting the CN and intl modules over shared executor, OAuth, usage and token-refresh helpers. Your commits are kept intact. Maintainer fix-up commits on top: restored the 'N AI providers' wording that the count bump had turned into bare numbers in 67 llm.txt files, README alt texts and SVGs; synced the total to 372, since the tip had meanwhile added typesafe without regenerating the reference; typed the two `any` casts in codebuddyDeviceAuth.ts; and regenerated the executor-map and translate-path goldens. The translate-path golden had been generated on win32. Protected surfaces (AGENTS.md, llm.txt) carry the count change only, approved by the owner. Validated: typecheck:core, open-sse typecheck, file-size, t11 any-budget, ESLint, check:docs-all, provider consistency/assets/order/provenance, and 195/195 focused tests across 13 files.
Batch-merged with the owner's 2026-10-09 PR wave (/merge-batch). Validated in one combined tree of 57 boarded PRs on top of release/v3.8.52 (35ef635c): typecheck:core, check:open-sse-typecheck, check-deps, changelog-integrity, complexity + cognitive ratchets, check:docs-all, i18n UI coverage, ESLint on all 247 changed source files — all green for this wave; 89 focused unit test files (739/744 pass under node:test, the 4 UI .tsx files re-run under vitest 13/13, check-deps fixed in #15912). Remaining reds in that tree belong only to held/draft PRs outside this wave (#15790 file-size, #15780 open-sse types).
Batch-merged with the owner's 2026-10-09 PR wave (/merge-batch). Validated in one combined tree of 57 boarded PRs on top of release/v3.8.52 (35ef635c): typecheck:core, check:open-sse-typecheck, check-deps, changelog-integrity, complexity + cognitive ratchets, check:docs-all, i18n UI coverage, ESLint on all 247 changed source files — all green for this wave; 89 focused unit test files (739/744 pass under node:test, the 4 UI .tsx files re-run under vitest 13/13, check-deps fixed in #15912). Remaining reds in that tree belong only to held/draft PRs outside this wave (#15790 file-size, #15780 open-sse types).
Batch-merged with the owner's 2026-10-09 PR wave (/merge-batch). Validated in one combined tree of 57 boarded PRs on top of release/v3.8.52 (35ef635c): typecheck:core, check:open-sse-typecheck, check-deps, changelog-integrity, complexity + cognitive ratchets, check:docs-all, i18n UI coverage, ESLint on all 247 changed source files — all green for this wave; 89 focused unit test files (739/744 pass under node:test, the 4 UI .tsx files re-run under vitest 13/13, check-deps fixed in #15912). Remaining reds in that tree belong only to held/draft PRs outside this wave (#15790 file-size, #15780 open-sse types).
Brought the current tip in: additive conflicts with #13191/#14131 in the provider registry, executor map, web-cookie constants and web-session credentials resolved as unions; the models route keeps the tip's shared webDiscoveryArgs bag and routes it through this PR's Conol+SYNTX discovery chain. RESERVED_PREFIX_COUNT re-measured on the merged tree (429). Provider count tests, translate-path golden, module-integrity, SYNTX/Twinmind/Token Market/image tests (159/159), provider-consistency, typecheck core/open-sse/api, file-size, complexity, env-doc-sync, fabricated-docs, test-masking and changelog green; PROVIDER_REFERENCE regenerated. Includes the worker's fix sanitizing getSyntxUsage errors (JWT echo). Thank you!
Brought the current tip in (additive conflict with #13191 in the provider registry index resolved as a union) and re-measured RESERVED_PREFIX_COUNT on the merged tree (427). Provider count tests, translate-path golden, Twinmind + Token Market tests (55/55), provider-consistency, open-sse typecheck, file-size, complexity, fabricated-docs, test-masking and changelog green; PROVIDER_REFERENCE regenerated. Full gate set was validated by the maintainer's worker on the previous tip. Thank you!
Brought the current tip in and re-measured the provider count fixtures on the merged tree (reserved prefixes / api-key providers). Provider count tests + translate-path golden green, provider-consistency, file-size, fabricated-docs, test-masking and changelog green; the PR's own tests and the full gate set were validated by the maintainer's worker on the previous tip. Docs counters are synced in a separate follow-up. Thank you!
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
Validated with scripts/release/merge-train.sh --fast (train tip 57a1c7a2, 20 PRs): static gates and the changed node:test files green. Only inherited base-red remains, reproduced on the pure tip: translation drift of docs/reference/ENVIRONMENT.md, 3 autoCombo vitest 5s timeouts (#15106), agent-skills-sync drift (#15306).
Validated with scripts/release/merge-train.sh --fast (train tip 57a1c7a2, 20 PRs): static gates and the changed node:test files green. Only inherited base-red remains, reproduced on the pure tip: translation drift of docs/reference/ENVIRONMENT.md, 3 autoCombo vitest 5s timeouts (#15106), agent-skills-sync drift (#15306).
* test(translator): expect boolean is_error on tool_result blocks (#15754)
#15754 made the OpenAI-to-Messages translator always emit a boolean is_error on
every tool_result block (strict upstreams such as the Zed hosted proxy
reject requests without it). The older multimodal translation test still
pinned the block shape without the field.
* test(images): include Codex GPT Image models in the image catalog listing (#14976)
#14976 registered gpt-image-2.5-flare and gpt-image-2 under the codex image
provider (routed to the dedicated Codex Images API) and updated the registry
test to the five-id list, but the image catalog route test still pinned the
three GPT-5.6 hosted-tool ids.
* docs(flags): keep RATE_LIMIT_AUTO_ENABLE catalog default in sync with its definition
#15736 changed the catalog Default cell to _(unset)_, but the catalog
documents FEATURE_FLAG_DEFINITIONS 1:1 and the definition (what the
feature-flags API/UI resolves when nothing is set) is still "false".
Restore the code value and keep the corrected runtime explanation in the
description: rateLimitManager reads only the env var and falls back to the
dashboard setting (default on) when it is unset.
* test(combos): pin on-demand per-candidate reads on the tables #15378 left unmemoized
#15353 added a contrast test asserting the on-demand capability path re-reads
the synced catalog per candidate (>50 reads). #15378, merged just before it,
memoized the synced vision verdict behind the catalog version, so that path
now issues 7 synced reads and the contrast went red on the tip.
Keep the contrast on the capability and override tables (still thousands of
per-candidate reads on demand vs <=2 / bounded on the snapshot route) and pin
the memo itself: synced reads stay within the per-provider bound. With the
pre-#15378 module the new assertion fails (336 synced reads).
* test(chatcore): end the prompt-cache fixture on a user turn (#15830)
#15830 re-landed #13572: the first-party Messages provider now strips a trailing
text-only assistant turn (upstream rejects assistant prefill). The prompt-cache
metadata fixture ended on an assistant text block carrying a cache_control
breakpoint, so the strip dropped it and the recorded totalBreakpoints fell from
3 to 2. Append a user turn so the fixture still exercises system, user and
assistant breakpoints; the assertions are unchanged.
* fix(providers): keep discovered Codex effort variants in the exclusive dashboard listing
#13224 lists one <model>-<tier> row per reasoning level the Codex account
advertises (appendSyncedEffortVariants, non-exclusive branch). #15132 then made
Codex an exclusive synced-listing provider, and the exclusive branch returns
before that step, so the provider dashboard / Test All listing lost the
discovered tier rows while /v1/models still advertised them (cx/<model>-max).
Apply the same variant step on the exclusive branch for codex. The variants
come from the live inventory, so #15132's contract (no static aliases the
account does not advertise) still holds; its own tests stay green. The one
assertion in codex-discovered-reasoning that expected a static registry-only
row (gpt-5.6-sol-ultra) next to the live inventory is flipped to #15132's
contract.
* test(providers): keep the custom gpt-6 max_tokens case on an unregistered id (#15164)
The #14869 custom-model case used gpt-6-luna because it was not in the openai
registry, so it stayed on Chat Completions and had to be renamed to
max_completion_tokens. #15164 registered gpt-6-luna with targetFormat
openai-responses, so the request now goes through the Responses translator
(max_output_tokens) and the Chat Completions assertion read undefined.
Use an unregistered gpt-6 id for the custom-model case and add a case for the
registered gpt-6-luna Responses path (max_output_tokens, no max_tokens).
* chore(changelog): add fragment for the v3.8.52 tip unit-red drain
Brought the tip in (reserved provider-prefix count re-measured to 420: ChatPlayground's 418 + notrack-web id/alias). Provider tests 29/29, provider-consistency, translate-path golden, fabricated-docs, file-size green; the PR's own tests (81/81 + 2/2) and the full gate set were validated on the previous tip merge in the d7 board. Thank you!
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
Brought the tip in twice (env docs union: the PR's OMNIROUTE_API_KEY_WEEKLY_WINDOW/_TIMEZONE + the tip's OMNIROUTE_MAX_TOOLS_LIMIT; .i18n-state.json resolved per entry keeping the newer translation record). Validated in a combined board: own tests 23/23, full gate set green, check:docs-all green. Thank you!
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
* fix(proxy): restore Groq TLS fingerprint skip lost in #13717 (#13445, #14062)
The #13717 squash reverted #13445. Groq is excluded from Chrome TLS impersonation again
(direct and proxied branches, even when TLS_FINGERPRINT_PROVIDERS lists it) because
Cloudflare answers the spoofed fingerprint with 1010 browser_signature_banned.
The allowlist helper now lives in open-sse/utils/tlsFingerprintExclusions.ts so the
frozen proxyFetch.ts shrinks instead of growing; tests moved to tls-groq-skip-13445.test.ts.
Co-authored-by: Bob.Hou <houminxi@gmail.com>
* fix(gemini): restore thinkingLevel for Gemini 3.8 lost in #13717 (#13463, #14062)
Re-lands #13463: Gemini 3.8 requests carry thinkingLevel instead of a numeric
thinkingBudget and includeThoughts is only sent when the client asked, so thoughts
stop eating the output cap. Layered on top of the tip's buildGeminiThinkingConfig and
explicit thinkingLevel handling (explicit client level still wins).
Co-authored-by: Bob.Hou <houminxi@gmail.com>
* fix(sse): restore Claude assistant-prefill strip lost in #13717 (#13572, #14062)
Re-lands #13572: strip a trailing text-only assistant turn for the official Claude
OAuth provider (rejected upstream with "does not support assistant message prefill"),
alongside the existing Mistral handling.
Co-authored-by: Bob.Hou <houminxi@gmail.com>
* fix(combos): restore Gemini no-thinking probe and truncation reclassification lost in #13717 (#13560, #14062)
Re-lands #13560: combo health probes for Gemini models send reasoning_effort "none", and
detectMalformedNonStream no longer rewrites an empty-content 200 that stopped on
tool_calls / content_filter (alongside the tip's existing "length" exemption) into a 502.
Co-authored-by: Bob.Hou <houminxi@gmail.com>
* fix(embeddings): restore stored-key promotion on private-host nodes lost in #13717 (#13398, #14062)
Re-lands #13398: a private-host embeddings node classified authType "none" now sends its
stored API key as a bearer token (matching dashboard Check) instead of dropping it.
Co-authored-by: Bob.Hou <houminxi@gmail.com>
* fix(providers): restore SenseNova DeepSeek V4 Flash effort clamp lost in #13717 (#13626, #14062)
Re-lands #13626: SenseNova deepseek-v4-flash tops out at high, so xhigh/max requests are
clamped to high and the registry no longer advertises xhigh for it.
Co-authored-by: Bob.Hou <houminxi@gmail.com>
---------
Co-authored-by: Bob.Hou <houminxi@gmail.com>
* fix(claude): forward the message-threads beta so Claude Code's thread field is accepted (#15705)
* fix(claude): ignore stale CLAUDE_USER_AGENT below the pinned Claude Code version (#15740)
* docs(i18n): carry the pinned Claude Code version (2.1.280) into every mirror (#15740)
Language-neutral literal swap (2.1.258 -> 2.1.280) in the 66 mirrors of the three
docs this PR updated. STEALTH_GUIDE/AGENTROUTER re-adopted; ENVIRONMENT.md only has
its target hashes refreshed so its pre-existing source drift on the tip stays visible.
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
Validated in a combined board with the other PRs of this wave on release/v3.8.52: the PR's own tests pass; typecheck:core, open-sse typecheck, api-typecheck, complexity, changelog-integrity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, lockfile, deps, gate-manifest, cli-i18n and i18n coverage green. Any file-size ceiling or stryker registration this wave needs lands in the wave's follow-up PR. Thank you for the contribution!
Adds OMNIROUTE_EGRESS_IP_LOCK_PROVIDERS so an operator can disable the egress-IP lockout or replace the free-tier provider set. Unset keeps opencode, opencode-go, and opencode-cli. Thanks @alvinveroy.
⚠️ base-red inherited: #15306
Gates Grok subscription image routes behind GROK_SUBSCRIPTION_IMAGES_ENABLED, default off. With the flag off, the existing xAI API-key image path stays, and high/hd quality is not rewritten. Thanks @QuangBlue.
⚠️ base-red inherited: #15306
Onda A 2026-10-07. Combined board e1b721a1 validated this PR together with the rest of the wave, then this squash lands the contributor head unchanged.
- typecheck:core passed
- complexity 2993 (baseline 3218)
- cognitive complexity 1366 (baseline 1437)
- changelog integrity passed
- file-size passed after the authorized ceiling bump; that bump ships in the wave follow-up, not in this squash
- focused tests: 318 passed in the batch run. The Devin anthropic price assertion already mismatches CLAUDE_SONNET_5_PRICING on origin/release/v3.8.52, and this wave does not change that constant. The combo-metadata miss did not reproduce when that file ran alone.
fix(reasoning): honor explicit opt-outs and Claude classifier defaults
Thanks @D4rk4.
⚠️ base-red inherited: #15306
Onda A 2026-10-07. Combined board e1b721a1 validated this PR together with the rest of the wave, then this squash lands the contributor head unchanged.
- typecheck:core passed
- complexity 2993 (baseline 3218)
- cognitive complexity 1366 (baseline 1437)
- changelog integrity passed
- file-size passed after the authorized ceiling bump; that bump ships in the wave follow-up, not in this squash
- focused tests: 318 passed in the batch run. The Devin anthropic price assertion already mismatches CLAUDE_SONNET_5_PRICING on origin/release/v3.8.52, and this wave does not change that constant. The combo-metadata miss did not reproduce when that file ran alone.
feat(api): add ZenMux image generation support
Thanks @JeanRGW.
⚠️ base-red inherited: #15306
Onda 8. Este squash entra com o crédito de @maxmad64bis (feat(proxy-subscription): warn with a translated count when generation skips entries).
As migrations são `197_proxy_subscription_core_config.sql` e `198_proxy_subscription_core_binary.sql`. Com esses arquivos no disco, 197 e 198 saem de `KNOWN_GAPS`. A contagem de `skipped` não soma `core_rejected` duas vezes. O catch de `internal_error` permanece. O branch do #15377 não entra. O teto de file-size fica para o follow-up da onda.
⚠️ base-red inherited: #15306
Obrigado, @maxmad64bis.
Onda 8. Este squash entra com o crédito de @maxmad64bis (feat(proxies): accept operator-provided dated egress observations for pool members).
A migration ficou em `199_proxy_operator_egress.sql`. O 199 sai de `KNOWN_GAPS` porque o arquivo existe. O 200, que já existia, continua fora da lista. A flag `PROXY_OPERATOR_EGRESS_ENABLED` permanece desligada por padrão. O teto de file-size fica para o follow-up da onda.
⚠️ base-red inherited: #15306
Obrigado, @maxmad64bis.
Onda 6. Este squash entra com o crédito de @lorenzozanee (fix(sse): make streaming fetch-start cap configurable).
O board único validou os 19 PRs (sem o #15412): file-size OK, changelog OK, i18n drift OK, typecheck:core OK, complexity e cognitive dentro do baseline. Testes focados: 390 passaram, 1 skip. O teste novo de GHE Copilot Sonnet 5.5 falhou no head original e foi corrigido no board; esse ajuste entra com o #15478, fora deste squash.
O rebaseline de file-size e o adopt de i18n ficam num follow-up.
⚠️ base-red inherited: #15306
Obrigado, @lorenzozanee.
Onda 5. Este squash entra com o crédito de @Kizuno18 (feat(proxy): add an operator HTTP/2 opt-out).
O board único validou os 28 PRs juntos: file-size OK, changelog OK, i18n drift OK, typecheck:core OK, complexity 2976/3218, cognitive 1358/1437. Testes focados: 545 passaram, 0 falharam, 3 skip em 52 arquivos. Cinco timeouts de resilience-http-e2e eram carga e passaram isolados.
O rebaseline de file-size e o adopt de i18n ficam num follow-up, fora deste squash.
⚠️ base-red inherited: #15306
Obrigado, @Kizuno18.
Onda 5. Este squash entra com o crédito de @HDBR (perf(usage): cache slow analytics responses so the dashboard stops blocking the event loop).
O board único validou os 28 PRs juntos: file-size OK, changelog OK, i18n drift OK, typecheck:core OK, complexity 2976/3218, cognitive 1358/1437. Testes focados: 545 passaram, 0 falharam, 3 skip em 52 arquivos. Cinco timeouts de resilience-http-e2e eram carga e passaram isolados.
O rebaseline de file-size e o adopt de i18n ficam num follow-up, fora deste squash.
⚠️ base-red inherited: #15306
Obrigado, @HDBR.
Onda 3 (woodsonl) validada num único board em `.claude/worktrees/batch-w3` sobre `origin/release/v3.8.52` (`4f4c983347b9`), 27 PRs, superfícies protegidas 0.
Evidência: `typecheck:core` limpo. i18n drift limpo no board. changelog-integrity ok. file-size ok (170 congelados). complexity 2975/3218 e cognitive-complexity 1357/1437 dentro do baseline. node:test focado: 1868 passaram, 0 falharam. Vitest da UI: 150 passaram em 12 arquivos. Os 38 do RTK caem no `useCallback` nulo de `node_modules/node_modules/react` via zustand, o mesmo React duplicado desta worktree. Onde dois PRs mexiam no mesmo save, o board ficou com os dois comportamentos: escrita parcial de engine por id e a fila/resync do PR que entrou depois.
O hash de `.i18n-state.json` do guia de quality-gates entra no follow-up, fora do squash.
⚠️ base-red inherited: #15306 (timeouts de suíte no tip, não neste diff).
Obrigado, @woodsonl.
Onda 1 (jonlwheat2-gif) validada num único board em `.claude/worktrees/batch-w1` sobre `origin/release/v3.8.52` (`2eee95e1`).
Evidência do board: 93 testes focados passaram (sanitização de áudio, Kie, import degradado, literais das 8 rotas de auth, hop MCP, freetheai, check-error-helper). `typecheck:core` limpo. changelog-integrity, complexity e cognitive-complexity dentro do baseline. O arquivo `src/shared/constants/providers/apikey/gateways.ts` cresce 1544→1547 por causa do #15520; o rebaseline entra no follow-up desta onda.
⚠️ base-red inherited: #15306 (timeouts de suíte no tip, não neste diff).
Obrigado, @jonlwheat2-gif.