Thanks @maxmad64bis — repo quality checks run in a throwaway data directory. The route-guard membership check still loads `isLocalOnlyPath`; the import only moves to after that isolation. Covered by `tests/unit/repo-checks-isolate-datadir.test.ts`.
Boarded on release/v3.8.52 at ac590dafa6. Focused node tests: 74 passed, 0 failed. The #16473 dashboard case is a vitest file and passed 3/3 under vitest. Changelog integrity passed. File-size kept the inherited executeTargetAttempt.ts overage (1288 > 1284). This pull request does not touch that file.
⚠️ base-red inherited: #15306
Thanks @opensource-elearning — parseModel hot-path logging goes through the level-gated logger, in `open-sse/services/model.ts`, covered by `tests/unit/model-logger-gating.test.ts`.
Boarded on release/v3.8.52 at e23fb0f8e8. Focused tests: 87 passed, 0 failed. Changelog integrity passed. File-size kept the inherited executeTargetAttempt.ts overage (1288 > 1284). This pull request does not touch that file.
⚠️ base-red inherited: #15306
Thanks @Junior-HJ — accepted connections now enable TCP keepalive. The change is in `src/shared/utils/runtimeTimeouts.ts` plus the dev server scripts, covered by the three main-server keepalive and timeout-parity tests.
Boarded together on release/v3.8.52 at 4833845bda. Focused unit tests: 133 passed, 0 failed (`node --import tsx/esm --test --test-force-exit`). File-size gate: only the inherited `open-sse/services/combo/executeTargetAttempt.ts` overage (1288 > frozen 1284), unchanged by this pull request.
⚠️ base-red inherited: #15306
The markdown table helper escaped pipes but not backslashes, so a summary
ending in a backslash turned the escaped pipe into a real column separator
(CodeQL js/incomplete-sanitization #1135).
Batch-merged with the owner's 2026-10-10 hold/backlog PR wave (/merge-batch). Validated in one combined tree of 43 boarded PRs on top of release/v3.8.52 (048d9e2f): typecheck:core, check:open-sse-typecheck, check-deps, check-test-discovery, changelog-integrity, complexity + cognitive ratchets, check:docs-all, i18n UI coverage, ESLint on the 142 changed source files - green; 58 changed node:test files 584/586 (2 timing flakes in video-retention-http-12150 that pass in isolation) and 3 vitest files 116/116. File-size overruns in that tree belong only to PRs held out of this wave (#16110, #16112, #16140, #15790). Warning: base-red inherited: #15306.
Batch-merged with the owner's 2026-10-10 hold/backlog PR wave (/merge-batch). Validated in one combined tree of 43 boarded PRs on top of release/v3.8.52 (048d9e2f): typecheck:core, check:open-sse-typecheck, check-deps, check-test-discovery, changelog-integrity, complexity + cognitive ratchets, check:docs-all, i18n UI coverage, ESLint on the 142 changed source files - green; 58 changed node:test files 584/586 (2 timing flakes in video-retention-http-12150 that pass in isolation) and 3 vitest files 116/116. File-size overruns in that tree belong only to PRs held out of this wave (#16110, #16112, #16140, #15790). Warning: base-red inherited: #15306.
Batch-merged with the owner's 2026-10-10 hold/backlog PR wave (/merge-batch). Validated in one combined tree of 43 boarded PRs on top of release/v3.8.52 (048d9e2f): typecheck:core, check:open-sse-typecheck, check-deps, check-test-discovery, changelog-integrity, complexity + cognitive ratchets, check:docs-all, i18n UI coverage, ESLint on the 142 changed source files - green; 58 changed node:test files 584/586 (2 timing flakes in video-retention-http-12150 that pass in isolation) and 3 vitest files 116/116. File-size overruns in that tree belong only to PRs held out of this wave (#16110, #16112, #16140, #15790). Warning: base-red inherited: #15306.
* ci(release): preview-artifact build-once workflow with artifact identity (#8084)
Manual (workflow_dispatch pr_number) or `preview-artifact` label lane that
builds the PR head once (npm ci + build:release), validates that build with
check:pack-artifact and check:pack-boot (fake secrets, ephemeral DATA_DIR),
proves the uploaded tarball is byte-identical to a re-pack of the validated
tree, records its identity (head/base SHA, lockfile hash, platform/arch/node
ABI, bundler, build policy) and uploads tarball + identity + SHA256SUMS.
A separate GitHub-hosted `attest` job, the only one holding id-token/
attestations write, verifies the checksums and attests the tarball. Fork PRs
are refused on both trigger paths; nothing publishes.
Refs #8084
* feat(release): dry-run script for the 3.9.0 LTS cut (rail 3.8.58)
`npm run release:dry-run-lts-cut` prints and validates the cut without
executing anything: preconditions (source resolves, previous tag v3.8.59,
package.json = 3.9.0, release-freeze open, release branch green per the
"Release branch not green" issue, stable/v3 + develop absent), stable/v3 from
the tip, develop with the 4.0.0 bump (package.json x3, lockfile, openapi),
which dormant-workflow triggers/`if:` turn true (and which stay gated by a
repository variable or are pinned to the canonical repo), expected dist-tags
(latest -> 3.9.0, next/nightly empty; uses scripts/release/dist-tag.mjs when
present, a minimal fallback otherwise) and the rollback.
`--execute --remote <fork>` runs the two branch steps (or `--rollback`) only
against a fork: origin and any remote whose URL is the canonical repository
are refused, every step is confirmed on the terminal, the develop bump commit
is built with git plumbing (no working tree touched) and every command is an
execFile argv array. Rehearsal parameters (`--target-version`,
`--previous-tag`, `--advisory`) let 3.8.58 run it on the current tip.
* feat(release): print the stable/v3 and develop SHAs after an LTS-cut rehearsal
* docs(release): 3.9.0 LTS cut runbook and GO/NO-GO checklist (rail 3.8.58-.59)
RELEASE_CHECKLIST gains "3.9.0 LTS cut (rehearsed in 3.8.58)": the read-only
dry-run (`npm run release:dry-run-lts-cut`), the fork-only rehearsal and its
rollback, the PR preview-artifact lane (download, checksum, attestation
verify, install the same bytes) and the ordered real cut.
New docs/ops/LTS_GO_NO_GO.md: rail gates G0/G1/G2/G11/G12/G13/G14 and the
10-item closing battery, each with the command that proves it and an empty
evidence column for the owner, ending in the GO / NO-GO line. Linked from the
ROADMAP (Phase 3), the docs index and the ops sidebar.
* fix(release): model G11 as the Mergify queue and report base-green as unknown for missing branches
G11 is the Mergify `release` queue (GitHub's native merge queue was rejected
in v3.8.49: no branch wildcards on a personal-account repo), not a ruleset
`merge_queue` rule. The dry-run now reads `.mergify.yml` at the cut source
(queue_rules[release] targeting release/*, entered via the `queue` label, with
a checks_timeout) and checks the `queue` label exists; the release/* ruleset
is checked separately for deletion + non_fast_forward only.
base-green no longer reads "green" when the release branch does not exist on
origin: no open base-red issue is not evidence for a branch the observer
cannot see, so it reports `unknown ... (not verifiable)` and fails closed.
* perf(rail): add reproducible LTS performance baseline script
scripts/perf/lts-baseline.mjs orchestrates test:heap, bench:heap-body,
bench:routing-events, optional build:release (--with-build) and TTFB
(median + p95 after 3 warmups) into one JSON report with per-measurement
ok/skipped/failed status. Isolated DATA_DIR per child, fake secrets, no
shell, process-group kill in finally. Exposed as npm run perf:lts-baseline.
* docs(ops): document the LTS performance baseline procedure
PERF_BASELINE.md covers flags, the meaning of each number, the
same-host-only comparison rule and the idle VPS/.113 procedure; linked
from QUALITY_GATES.md.
* test(quality): add a reproducible src/open-sse boundary measurement script
scripts/quality/measure-boundary.mjs scans src/**/*.ts(x) and open-sse/**/*.ts(x)
(skipping node_modules, .next, tests/, __tests__/ and *.test/*.spec files), lexes out
comments/strings/regex literals, extracts static, re-export, side-effect, dynamic
import() and require() specifiers, resolves @/, @omniroute/open-sse and relative paths,
and counts unique cross-boundary file edges in both directions, grouped by subsystem of
origin. Emits --json or --md, deterministically ordered, plus the full open-sse -> src
edge list as the v4 remediation input. Exposed as `npm run quality:boundary` and
registered in the gate manifest as separately-invoked (report only, not a gate).
Rail 3.8.55, Task 13.
* test(api): add Claude- and Gemini-format provider-journey contract suites
The #8330 journey covers one OpenAI-compatible provider and stops at /v1/models.
Two companion suites extend it to other wire formats and add the legs that only
break across module boundaries, against a fake upstream on an ephemeral 127.0.0.1
port (no external network):
- provider-journey-claude: anthropic-compatible node -> connection -> REAL model
sync (sync route -> /models route -> upstream /models) -> /v1/models publishes
<prefix>/<model> with owned_by = prefix -> /v1/messages (JSON and SSE) reaches the
upstream as an Anthropic call for the raw model id with the connection key, and the
client gets a Claude message / Anthropic event stream.
- provider-journey-gemini: openai-compatible node, same sync/catalog legs, then
/v1beta/models/<prefix>/<model>:generateContent is translated to an OpenAI Chat
Completions upstream call and back to candidates[].
A TODO step records a gap found on the way: /v1beta/models still names
custom-provider models by the raw provider-node UUID (#8327 residue on the
Gemini catalog surface).
Rail 3.8.55, Task 13.
* feat(dev): local candidate build/validate/promote loop with rollback
Add scripts/dev/candidate.mjs (npm run dev:candidate), the local side of
RFC #8084: build one candidate from the current tree (npm pack) or a
prebuilt tarball into an isolated npm prefix under _artifacts/candidate/<id>,
boot that packaged CLI on a free port with an isolated DATA_DIR and fake
secrets, require /api/health and /v1/models to answer 200, promote the same
validated artifact with compensated renames, and roll back automatically
when the promoted slot fails its health check. Every command supports
--dry-run and --json; child processes use argument arrays only (Hard Rule #13).
stopChild is now exported from check-pack-boot.mjs so the loop reuses the
same process-group shutdown instead of duplicating it.
* docs(ops): document the local candidate loop in the golden path and release checklist
* fix(dev): isolate the candidate boot from operator .env files
The first real validate run against the published 3.8.51 tarball booted and
answered /api/health, but /v1/models returned 401: the packaged CLI fills
undefined keys from <packageRoot>/.env (postinstall copies .env.example with
INITIAL_PASSWORD=CHANGEME), and any password is a credential surface for the
model catalog. It also reads the default data dir's .env, derived from
HOME/XDG_CONFIG_HOME/APPDATA, i.e. the operator's real ~/.omniroute/.env.
The candidate now gets an isolated HOME (plus XDG/APPDATA) under its slot,
INITIAL_PASSWORD pinned to an empty value, a fresh DATA_DIR on every
validation, and --log so failures show server output. run --dry-run no
longer claims the candidate is active.
* 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.
* chore(release): declarative rail labels + labels:sync script
Add .github/labels.yml with the dormant LTS-rail labels (v4-feature, lts,
forward-port, channel:latest|next|nightly, preview-artifact) and
scripts/release/sync-labels.mjs (npm run labels:sync): dry-run by default,
--apply creates missing / edits divergent labels, never deletes and never
touches labels outside the file. gh runs via execFile argv (Hard Rule #13).
Colors must be quoted in the YAML: unquoted hex such as 5319E7 is parsed as
a float and 012345 as an int, so the parser refuses non-string colors.
* chore(release): feature and bugfix PR templates + target-branch checklist
Add .github/PULL_REQUEST_TEMPLATE/feature.md and bugfix.md (selected with
?template=feature.md / ?template=bugfix.md). The bugfix template requires a
failing-then-passing test or a recorded real-environment validation (Hard
Rule #18). The default template gains a short target-branch checklist that
links the release strategy, the contribution golden path and the ROADMAP.
* docs(release): RELEASE_STRATEGY for the dormant LTS rail
Document the 3.9.0 branch model (stable/v3, develop, main), what lands in each
branch, the npm dist-tags (latest = v3 until 4.0 GA, next = rc, nightly),
forward-port with Co-authored-by credit, the 3.8.55-3.8.59 validation window
and the v4-feature label rule. States what the publish workflow wires today
and what is still missing (nightly dist-tag, post-GA v3 patch tag). Linked
from ROADMAP.md, docs/README.md and the ops sidebar.
Merged with the owner's 2026-10-09 linked-PR wave. Validated on top of release/v3.8.52 together with #15676: classify-pr-changes unit tests 46/46, ESLint + Prettier clean, both workflow YAMLs parse. The `domains` output has no consumer yet, so CI behavior does not change. check:docs-all is red on the pure tip too (provider count 371 vs docs 370, inherited, not from this PR).
Image generations and upscale proxy errors go through the shared error helper. Both routes left the missing-helper allowlist.
⚠️ base-red inherited: #15306
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).
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).
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!
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!
Validated in a local merge-train on a clean-install host: static gates green, changed tests green, i18n drift classified as inherited. The vitest gate was red only on base-reds and timeouts that reproduce on the untouched tip (audit.test.ts, provider-family-combos, tieredRotation; the rest pass with a longer timeout).
⚠️ base-red inherited: #15306
Validated locally: merged with the current tip (no conflict), tests/unit/merge-train-plan.test.ts 17/17, bash -n, --plan output, changelog-integrity.
⚠️ base-red inherited: #15306
ICU-escapes message catalog values that broke IntlMessageFormat, and adds check:ui-icu as a local script. The tiktoken externalize on the tip is unchanged; this only drops a duplicate serverExternalPackages entry. Thanks @chirag127.
⚠️ 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 (perf(db): drop two conversation_turn_nodes indexes no query reads).
A migration ficou em `201_drop_unused_turn_node_indexes.sql`. O 200 não entra em `KNOWN_GAPS`: o arquivo já existe. 197 e 198 continuam reservados até o #15564. 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 @insoln (fix(sse): stabilize standalone compression worker resolution (#12797)).
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, @insoln.
Onda 6. Este squash entra com o crédito de @QuangBlue (fix(api): standalone server owns SIGTERM so graceful-shutdown cleanup runs).
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, @QuangBlue.
Onda 6. Este squash entra com o crédito de @QuangBlue (fix(api): keep Next's upgrade listener off the run-next server).
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, @QuangBlue.
Onda 5. Este squash entra com o crédito de @grapeslush (fix(cli): prefer an existing ~/.omniroute over XDG_CONFIG_HOME in every data-dir resolver).
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, @grapeslush.
Onda 4. O restante do lote do @maxmad64bis já estava na release. Este squash é o índice cobrindo da matriz de saúde (migration 200) mais a reserva dos buracos 197, 198 e 199.
197 e 198 continuam com o #15564. 199 continua com o #15314. Os dois ainda estão abertos. Sem a reserva, o gate de numeração quebrava no tip no momento em que o 200 entrasse.
Evidência neste board: `check-migration-numbering` OK (194 migrations, 6 gaps). Testes focados: 26 passaram, 0 falharam (`check-migration-numbering`, `migration-200-provider-health-matrix-cover`, `call-logs-family-agg`). O índice é `CREATE INDEX IF NOT EXISTS` e a segunda corrida é no-op.
⚠️ base-red inherited: #15306 (timeouts de suíte no tip, não neste diff).
Obrigado, @maxmad64bis.
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 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 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 2 (HouMinXi) validada num único board em `.claude/worktrees/batch-w2` sobre `origin/release/v3.8.52` (`e05f1bd78bac`), 26 PRs, superfícies protegidas 0.
Evidência: `typecheck:core` limpo. changelog-integrity, complexity (2973/3218) e cognitive-complexity (1356/1437) dentro do baseline. Testes focados: 235 passaram. Os 5 vermelhos não são deste diff: o `.test.tsx` do cloudflared passa no Vitest (1/1); o intervalo do Codex usage passou 3/3 isolado (flake sob carga); o banner no-auth cai no mesmo `useContext` nulo de `tests/unit/request-log-detail-stream.test.ts`, que já existe no tip, por causa do React duplicado em `node_modules/node_modules` desta worktree.
O file-size do board ainda vê o teto antigo de `gateways.ts` (já corrigido em #15679) e o crescimento próprio desta onda em RoutingTab, auth, responseSanitizer, search, proxyFetch e stream. Esse rebaseline entra no follow-up, fora do squash.
⚠️ base-red inherited: #15306 (timeouts de suíte no tip, não neste diff).
Obrigado, @HouMinXi.
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.
Brought the tip into the branch and revalidated: focused tests, typecheck:core, open-sse typecheck, file-size, changelog-integrity, complexity and mutation-test-coverage green. Thank you for the contribution.
Validated in a combined board on the current release tip: 165 focused tests (0 failures), typecheck:core, open-sse typecheck, gate-manifest, mutation-test-coverage, file-size, changelog-integrity, complexity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, test-masking, cli-i18n and the i18n gates green. Thank you for the contribution.
Validated in a local merge-train on a clean-install host (FAST gates green: static + changed tests + vitest on the combined tree; audit.test.ts verified passing on base and PR tree when the machine is idle).
⚠️ base-red inherited: #15306
Validated in a combined board on the current release tip: focused node:test + vitest suites, typecheck:core, open-sse typecheck, gate-manifest, mutation-test-coverage, file-size, changelog-integrity, complexity, env-doc-sync, test-discovery, vitest-exclusions, error-helper, cli-i18n and the i18n new-keys/ui-coverage gates green. Thank you for the contribution.