Contract with the phase-4/5 session (2026-11-14):
- ui-keys: syncUiKeys is called with pruneExtra (keys en.json dropped leave the other catalogs)
and rewrittenSinceRef (English values rewritten since the last release go back to translation;
--rewritten-since=<ref>, default origin/main, skipped when unresolvable). The backend translates
only when OMNIROUTE_TRANSLATION_* is configured, never in --check. The CLI fallback passes
--rewritten-since when the script supports it.
- e2e-timings: new step that runs syncE2eTimings (phase 5) when the tree ships it; skipped
otherwise.
- merge-train.sh: i18n:check-keys, i18n:check-keys:cli and i18n:check-ratio run in pr mode — the
train judges the catalogs its PRs changed against the merge base, and a key that exists only in
en.json is completed by the release refresh instead of reddening the train.
The npm description carried the live provider total, so every provider PR
rewrote the same line and 25 open PRs conflicted on it alone. Use a
count-free wording (also in flake.nix, which had drifted to 160+) and turn
the docs-counts check into a STRICT guard that rejects an exact provider
count in the description instead of requiring the live one.
Adversarial review of this branch, each finding reproduced before the fix:
- Coverage floor in pr mode: the locator read any four slash-separated numbers, so editing the
provider breaker's HTTP status list in AGENTS.md (`408/500/502/503/504`) failed as "edited a
managed value". The diff and the rewrite plan now use only tuples that can be percentages;
the release validator is unchanged.
- Merge train: its detached worktree cannot tell a writer branch (the nightly refresh PR, a
translation wave) from a feature, so a train boarding one went red on legitimate rewrites. The
gate honours OMNIROUTE_GATE_BATCH=1 (skip the managed-value diff, like merge_group) and the
train declares itself a batch.
- workflow_dispatch on a feature branch ran the docs jobs in strict release mode, red by design:
those steps now set OMNIROUTE_GATE_MODE=pr when the dispatch is not on main or release/v*.
- i18n-mirror-refresh (schedule) ran check:docs-all in release mode and stopped opening the
mirror PR whenever the base was behind the code: its docs check runs in pr mode (same line as
the phase-4 PR, coordinated with that session).
- Nightly refresh: a run with no diff now closes the robot's stale refresh PR (a hand-pushed
tip is only reported).
- Refresh: the plan lists the README mirrors' database row before README.md, so mirrors were
rewritten first, the relay found nothing to carry and 66 locales turned into drifted targets.
Sources now go first, a mirror the plan rewrote counts its rewrites as carried (local digits
included), and a mirror is certified in sync only when every change reached it; a locale that
was already stale keeps its source hash.
- The snapshot test judged release-only checks (provider reference vs live modules) against the
snapshot, which a provider PR that regenerates PROVIDER_REFERENCE.md would break; it now judges
the derived and invariant checks only, with a floor on how many it judges.
- ci.yml docs-sync-strict and quality.yml docs-gates ("Docs accuracy"): checkout with
fetch-depth 2 and BASE_SHA (PR or merge-group base) on `npm run check:docs-all`, so the
counts gate runs in pr mode on feature PRs against the base the merge commit sits on.
- Release-Green: every HARD item runs with OMNIROUTE_GATE_MODE=pr unless the environment
already sets one (they answer "did the base break?"); a new DRIFT item `derived-refresh`
runs `npm run release:refresh-derived -- --check`, the strict view, which reports without
opening the base-red issue. Between releases the base is behind the live code by design.
- nightly-derived-refresh.yml: once a day on the highest release/vX.Y.Z (skipped under
release-freeze), runs the refresh with --profile=nightly and keeps ONE PR open from the
robot branch chore/derived-refresh (same lease-pinned rebuild as the UI Kit watch). Never
merges; flags agent-instruction surfaces for the owner. Needs the DERIVED_REFRESH_PR_TOKEN
secret to open the PR; without it only the branch is pushed.
- merge-train.sh: the counts gate judges the train in pr mode against the train base.
Every number the counts gate checks inside the README SVGs (providers, MCP tools, routing
strategies, pools, free-forever providers, catalog entries, CLI integrations, scoring factors,
the free-tier budget card) comes from docs/reference/derived-facts.json through
scripts/docs/readmeFacts.mjs instead of a literal kept by hand in each generator. Curated copy
(150+, 15-95%, $0) stays literal. Each generator still produces the committed SVG byte for byte.
One entry point recomputes every derived value, in order: provider reference, facts snapshot,
managed numbers (planDerivedRewrites, relayed into the docs/i18n mirrors with the
bump-version-claims rule for .i18n-state.json), README diagrams, generated skills, UI key
catalogs and the llm.txt mirrors (the phase-4 sync functions when exported, the current CLIs
otherwise). Changelog aggregation is opt-in (--with-changelog, release profile only): the
release keeps `npm run release:reconcile` as the canonical path.
--check writes nothing (every step runs on an in-memory overlay), exits 1 when a step would
change a file and lists the rewrites that need a human (manual), exit 2 on an infrastructure
error. --profile=nightly never touches the changelog or version claims. Every subprocess gets a
throwaway DATA_DIR. On this tree the full --check reports zero changes and zero manual items.
The counts gate now has two modes, resolved by scripts/check/lib/gateMode.mjs
(--mode, OMNIROUTE_GATE_MODE, then the Actions event):
- release (release PR, release skill, local default): strict equality against the live code,
exactly as before. On this tree the report is identical to the previous gate except for the
mode header and two new STRICT sections (routing-strategy counts in prose), all green.
- pr (feature PRs, merge_group, omni-queue): no tsx, no facts. Every derived check exposes an
extractor with the span of each value; the gate diffs the PR's changed files against the
merge base and fails only what the PR itself did: writing a managed value the base did not
carry, or dropping a required claim. It never fails because the base moved. Content
invariants that need no facts run in both modes; fact-only checks (provider reference vs
live modules, mode-pack names, manifest free tier) are release-only. Writer branches
(chore/derived-*, release/v*, docs/i18n-*, chore/i18n-*) may edit managed values.
- Exit codes: 0 ok, 1 drift or a PR violation, 2 infrastructure (facts not collected, or the
PR diff base cannot be resolved in CI), with a message saying it is not documentation drift.
- planDerivedRewrites({facts, readFile}) returns the exact rewrites that bring every
rewritable STRICT claim to the facts, and lists the rest as manual. It is what
`npm run release:refresh-derived` applies.
- scripts/release/facts.mjs: collectFacts/readCodeFactsResult classify a failed probe
(timeout, spawn, exit, parse) as an infrastructure error, never as documentation drift.
The 180 s hard timeout that turned a loaded host into a false red is now
OMNIROUTE_FACTS_TIMEOUT_MS (default 600 s). readCodeFacts() and the test seams keep
their old shape.
- The inline `node -e` probe becomes a real module (scripts/release/lib/code-facts-probe.mjs),
run under tsx in a subprocess. It forces a throwaway DATA_DIR before any import, so loading
the MCP tool modules can never open or migrate the operator's SQLite file.
- `npm run facts [-- --key=a.b] [--snapshot]` prints every derived number as JSON
(exit 2 on an infrastructure error).
- docs/reference/derived-facts.json: the facts as of the last refresh, serialized in a stable,
Prettier-identical layout. Generated artifacts and unit tests are judged against it; only
the release refresh and the nightly refresh PR write it.
Plan 2026-11-13 (derived numbers resolved only at release), phase 1 groundwork:
- The counters and the tsx code-facts reader move verbatim from
check-docs-counts-sync.mjs to scripts/release/facts.mjs, so the gate,
`npm run facts` and `npm run release:refresh-derived` share one definition
of every number. The gate re-exports them; no importer changes.
- scripts/check/lib/gateMode.mjs is the shared pr|release mode resolver, a
byte-identical copy of the one introduced with the derived-files guard
(01258da1), so both PRs merge cleanly in either order.
No behaviour change: the gate output on this tree is byte-identical before and
after, and the four gate test files pass (77/77).
The release map is 536.8 MB, 77 KB under V8's maximum string length.
check-forgotten-sibling-tests (and select-impacted-tests) loaded it with
readFileSync(utf8) + JSON.parse, so any PR adding tests failed Fast
Quality Gates with 'Cannot create a string longer than 0x1fffffe8
characters'.
The writer now starts every entry of a top-level object (sources,
artifacts) on its own line - still valid JSON - and readTestImpactMap()
parses it line by line from a Buffer, never decoding the whole file.
Other layouts fall back to JSON.parse while they fit in one string.
The base added the expiry-first strategy (#17829) and the
CODE_ASSIST_INELIGIBLE_ONBOARD_LEGACY_TIER flag (#18060), so both sides
had moved the same counts.
- Strategies: the code registry now has 22 public strategies (expiry-first
and jev). AGENTS.md, open-sse/services/AGENTS.md, the bs AGENTS mirror,
AUTO-COMBO.md (table now has both rows), RESILIENCE_GUIDE.md and llm.txt
state 22. The other docs the expiry-first PR bumped to 21 now say 22
(README, CONTRIBUTING, ARCHITECTURE, FEATURES, OPEN_SSE_ARCHITECTURE,
REPOSITORY_MAP, CODEBASE_DOCUMENTATION, comparison, diagrams README,
request-pipeline, QUOTA_SHARE, RELEASE_CHECKLIST, tier-flow images).
README's strategy table gets a jev row. The README SVGs were regenerated
from their generators (comparison table, hero, tier cascade, strategies
grid).
- Flags: both sides' flags are kept (catalog total 125, Runtime 62).
featureFlagDefinitions.ts stays under the 1440-line cap: the System One
spread loses its comment and two blank lines are dropped.
- llm.txt i18n mirrors: same five count lines as the root (docs-sync).
- stryker.conf.json: list boundary-engine-seams.test.ts, which now covers
auth.ts and autoStrategy.ts (check:mutation-test-coverage --strict).
- strategy-registry test: CANONICAL is 22 public + quota-share = 23.
- connectionAwareExpansion.ts, check-fabricated-docs.mjs, stryker.conf.json:
both sides kept.
Brings the recut of #17920 up to release/v3.8.54 at 2f2c1957. The base
added Hetzner, Grokified, Replicate and Cerebrium (#19206) and moved the
canonical provider count 388 -> 393 on the same lines this branch bumps.
The 93 conflicted files were count-only (verified by masking digits). Each
conflict hunk keeps the release side; the merged tree then has 394
canonical providers (check:provider-consistency), so the provider total
was replayed 393 -> 394 on the lines check:docs-counts flags, the matching
llm.txt mirrors, the tier-flow SVGs and the README diagram generators.
Digit-only edits. PROVIDER_REFERENCE.md was regenerated with
gen:provider-reference and the README diagrams with docs:readme-diagrams.
The "Catalog-Marked Free" figure (153) and the README locale mirrors
(389) are left as the base has them; neither is gated and both were
already behind the code before this merge.
Co-authored-by: Ilya Bogin <246701201+ilya-bogin-keenable@users.noreply.github.com>
Validated in the full merge-train on the .113 (lot 6, 2026-11-13): typecheck, static gates and the full unit suite. Every failure from that run was re-run in isolation, both on the merged tree and on the train base. They come from the .113 root environment, load-sensitive timing, or known flakes. None trace back to this change.
Co-authored-by: Bob.Hou <houminxi@gmail.com>
Co-authored-by: Minxi Hou <houminxi@gmail.com>
Validated in the full merge-train on the .113 (lot 6, 2026-11-13): typecheck, static gates and the full unit suite. Every failure from that run was re-run in isolation, both on the merged tree and on the train base. They come from the .113 root environment, load-sensitive timing, or known flakes. None trace back to this change.
Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
Validated in the full merge-train on the .113 (lot 5, 2026-11-12): typecheck, static gates and the full unit suite. Every failure from that run was re-run in isolation, both on the merged tree and on the train base. They come from the .113 root environment, load-sensitive timing, or known flakes. None trace back to this change.
Co-authored-by: Jowimila <127446097+jowimila@users.noreply.github.com>
Validated in the full merge-train on the .113 (lot 5, 2026-11-12): typecheck, static gates and the full unit suite. Every failure from that run was re-run in isolation, both on the merged tree and on the train base. They come from the .113 root environment, load-sensitive timing, or known flakes. None trace back to this change.
Co-authored-by: Dizzle <112548150+maxmad64bis@users.noreply.github.com>
Validated in the full merge-train on the .113 (lot 3c, 2026-11-11): typecheck, static gates and the full unit suite. Every failure from that run was re-run in isolation, both on the merged tree and on the train base. They come from the .113 root environment, load-sensitive timing, or known flakes. None trace back to this change.
Co-authored-by: Bl0ck <36800583+Bl0ck154@users.noreply.github.com>
Validated in the full merge-train on the .113 (lot 3c, 2026-11-11): typecheck, static gates and the full unit suite. Every failure from that run was re-run in isolation, both on the merged tree and on the train base. They come from the .113 root environment, load-sensitive timing, or known flakes. None trace back to this change.
Co-authored-by: Cristiano M Bergamo <cmbergamo@outlook.com>
Validated in the full merge-train on the .113 (lot 3a, 2026-11-11): typecheck, static gates and the full unit suite. Failures in that run were re-run in isolation against the train base. They come from the .113 root environment, load-sensitive timing, the known base-red (#19329), or a source-window test fixed separately in #19486. None trace back to this change.
Co-authored-by: serenity <295272363+serenity-X@users.noreply.github.com>
Validated in the full merge-train on the .113 (lot 2b, 2026-11-11): typecheck, static gates and the full unit suite. The remaining failures in that run come from the .113 root environment, the known base-red (#19329), or timing flakes under load. None trace back to this change.
* feat(dashboard): ratchet the kit type scale and cut 57 sub-12px hints (#19066)
scripts/check/check-type-scale-ratchet.mjs counts text-[8-11px] and font-bold in
src/. Ceilings in quality-baseline.json (914 and 254) equal the live count and may
only go down; the pre-commit hook and tests/unit/check-type-scale-ratchet.test.ts
enforce them. 57 non-dense hints, wizard subtitles, errors and empty states move
from text-[11px] to text-xs (971 -> 914).
Refs #19066
* chore(quality): tighten the type-scale ceilings to the current tip (911 / 251)
* test(dashboard): empty the stale kit-exception allowlist now that every entry is resolved
* chore(quality): give the type-scale ceilings headroom for in-flight PRs
release/v3.8.54 reached 13510 in-scope files from test growth, above the 13500 ceiling, so check:build-scope failed on the release branch and in every PR's Quality fast gates. The owner chose 18000; a leaked worktree or vendored copy (~12k files) still exceeds it.
Both this branch (keenable-search) and release/v3.8.54 (#15201, chatgpt)
moved the canonical provider count 387 -> 388 on the same lines, so the merge
kept 388. The merged tree has 389 canonical providers
(check:provider-consistency). Digit-only edits on those lines (AGENTS.md,
llm.txt + mirrors, README + mirrors, skills, package.json, docs, generator
constants); PROVIDER_REFERENCE.md and the README diagrams regenerated with
gen:provider-reference and docs:readme-diagrams.
Adds ChatGPT as its own OAuth provider through OpenAI's official Sign in with ChatGPT (SIWC) token-sharing flow and the public Responses API: a recognizable sign-in button, OpenAI's consent screen, an account-specific live model catalog, public Responses inference and usage management, without a separately created OpenAI API key or client secret.
Provider-count train, step 6: the branch was merged with the release tip after Codex Web Search (#17933). Both sides had raised the count from 386 to 387, so git kept identical lines; every count line was recounted to 388 (`gen:provider-reference`: 388 unique IDs, oauth=31): README and its 66 mirrors (Persian digits in `fa`), `llm.txt` and its 66 mirrors, AGENTS.md, skills, docs, `package.json` and the SVG generators. PROVIDER_REFERENCE and the README diagrams were regenerated. RESERVED_PREFIX_COUNT is 444 (443 on the base plus `chatgpt`). The `QuotaCard` conflict keeps the ChatGPT local-usage branch and the base's Cursor per-model usage. The PKCE challenge and the test owner fingerprints now go through `generateCodeChallenge` and `opaqueTokenFingerprint`, byte-identical to the inline SHA-256 they replace. Protected files differ from the tip only in digits. Validated with check:docs-counts, check:provider-consistency (388), the focused SIWC, usage UI, golden and count tests, lint and the full fast gates.
Both this branch (keenable-search) and release/v3.8.54 (#17933, codex-search)
bumped the canonical provider count 386 -> 387 on the same lines, so the merge
kept 387. The merged tree has 388 canonical providers
(check:provider-consistency). Digit-only edits on the lines either side bumped,
plus PROVIDER_REFERENCE.md regenerated with gen:provider-reference.
Adds `codex-search` (alias `codex_search`), a fallback-only `/v1/search` provider that uses the built-in `web_search` tool through connected OpenAI Codex (ChatGPT) accounts, so no separate search-service key is needed. Normalizes observed sources and citations into standard search rows, bounds the stream to 4 MiB with cancellation, keeps search failures in a search-specific in-memory lock so they never touch the shared Codex connection's health, and records upstream token usage in call logs. `CODEX_SEARCH_AUTO_FALLBACK_ENABLED` (default off) controls whether automatic searches may use a Codex account. Closes#17925.
Provider-count train, step 5 of 5: the branch was merged with the release tip after deAPI (#19319), ParalonCloud (#18356), MegaBrain (#18129) and RenderHour (#18103). Count-only conflicts took the base text and were recounted to 387 (`gen:provider-reference`: 387 unique IDs, search=20): README and its 66 mirrors (Persian digits in `fa`), `llm.txt` and its 66 mirrors, AGENTS.md, skills, docs, `package.json`, the SVG generators and the tier-flow SVGs. PROVIDER_REFERENCE and the README diagrams were regenerated. The feature-flag count is 121 on the merged tree. Protected files differ from the tip only in digits. Validated with check:docs-counts, check:provider-consistency (387), the focused search, flag, golden and count tests, lint and the full fast gates.
Adds RenderHour (`renderhour`) as one dual-auth media provider for images, video and speech: subscription sign-in (authorization code + PKCE with the public client via `resolvePublicCred`, rotating refresh tokens) or an `rh_…` API key, both validated with `GET /v1/balance`. One shared client runs RenderHour's async job API (upload, `POST /v1/generations` with an Idempotency-Key, polling with back-off), with thin image, video and TTS handlers on top.
Provider-count train, step 4 of 5: the branch was merged with the release tip after deAPI (#19319), ParalonCloud (#18356) and MegaBrain (#18129). Count-only conflicts took the base text and were recounted to 386 (`gen:provider-reference`: 386 unique IDs): README and its 66 mirrors (Persian digits in `fa`), `llm.txt` and its 66 mirrors, AGENTS.md, skills, docs, `package.json`, the SVG generators and the tier-flow SVGs. PROVIDER_REFERENCE and the README diagrams were regenerated. The OAuth test-config and provider-list conflicts keep both MegaBrain and RenderHour. Protected files differ from the tip only in digits. Validated with check:docs-counts, check:provider-consistency (386), the focused provider, OAuth, refresh, public-creds, golden and count tests, lint and the full fast gates.