* fix(dashboard): single frame for tables in child components hosted by a Card
Follow-up to #20181 (owner decision of 2026-11-14: the Card is the only
frame around a table). The AST guard only saw a table and a Card written in
the same file; it now follows one level across files: when a parent writes
`<Card>…<Child />…</Card>` with `Child` imported from another dashboard
file, that file's tables are checked as if they sat in that card. On the
base it lists 8 violations, fixed here:
- Cache → Reasoning tab (ReasoningCacheTab, inside the cache page Card):
the By provider, By model and Recent entries sub-panels lose their border
and background (titles and spacing kept); their kit Tables get the
borderless container, and the leftover sticky header patch on the capped
Recent entries table goes (the kit pins the header).
- Quota share pool card: AllocationTable (inside PoolCard's Card).
- Agent bridge card: ModelMappingTable (inside AgentCard's Card).
Refs #19620
* test(dashboard): cross-file single-frame check follows the hosted component
Review on #20213:
- only the component the parent renders inside its Card (plus same-file
components it renders by tag) is checked, not every export of its file;
- bordered elements between the child and the Card on the parent side are
reported too.
Fixtures cover a local helper table, an unhosted sibling export and a
parent-side bordered panel.
Refs #19620
* test(dashboard): cross-file single-frame check tracks each declarator
`export const A = () => …, B = () => …` declares two components in one
statement; only the hosted declarator is checked now (review on #20213).
Regression fixture added.
Refs #19620
* fix(dashboard): the Card is the only frame around a table
Owner decision of 2026-11-14 (item 3): tables inside a Card no longer draw a
frame of their own, and a bordered sub-panel around a table inside a Card
becomes a plain section.
- Cache → Semantic Cache: the Entries sub-panel loses its border and
background (title and spacing kept); CacheEntriesTab drops DataTableShell
for the kit TableLoadingRegion + a borderless Table (search and pagination
kept, search keeps the kit toolbar width).
- Cache → Prompt Cache: same for the "Breakdown by provider" sub-panel.
- Evals → suites: suites are sections of the card split by hairlines (kit
plain accordion pattern) instead of bordered boxes; the cases DataTable
uses framed={false}.
- Provider stats, cost overview (explorer + breakdown tables), resilience
cooldowns and the other kit Tables found inside a Card get
containerClassName="rounded-none border-0", the same borderless container
already used by #20141 and the analytics tables.
The AST guard now also covers Table inside Card, any depth (through
expressions, fragments and .map callbacks), and bordered elements between a
table and its Card. A jsdom test covers the two tables rendered by child
components (semantic cache entries, cooldowns).
Refs #19620
* test(dashboard): single-frame guard reads only static classes; stable translator mock
- The AST guard no longer searches the source text of a dynamic class
expression: only string literals and the literal parts of a template
count, so an inactive conditional branch can neither satisfy the
borderless check nor report a sub-panel (review on #20181). Fixtures added.
- The jsdom test returns one translator for every useTranslations call, so
the CacheEntriesTab fetch effect settles.
Refs #19620
* chore(ui-kit): sync vendored kit to 0.0.116
Upstream keak-ai/cheaper-inference-ui-kit#204 (closes#203): Table and
DataTable take `maxHeight`; the capped container scrolls on both axes,
pins the header row and takes focus while it overflows. No new dependency.
Refs #19620
* fix(dashboard): scroll tall tables through the kit Table maxHeight
Kit 0.0.116 (keak-ai/cheaper-inference-ui-kit#204) caps a Table with
`maxHeight`: the kit container scrolls both axes, pins the header row and
becomes a focusable, named region while it overflows (WCAG 2.1.1). Our own
scroll boxes never took focus, so keyboard users could not scroll them.
- DataTable adapter: the `<div style={{ maxHeight, overflow: "auto" }}>`
wrapper is gone; `maxHeight` goes to the kit Table, `!overflow-visible`
and the sticky/background patch on the header cells are dropped (the kit
pins and paints the header; `whitespace-nowrap` stays). New required
`label` prop names the scroll region; the five call sites pass a
translated string (evals recent runs and suite cases, conductor runners
and tasks, resilience connections).
- Kit Tables that capped themselves with `max-h-* overflow-y-auto` classes
or a capped wrapper now take `maxHeight` + a translated `scrollLabel`,
and lose their `sticky top-0` header patches: reasoning cache entries,
cache trend, import providers from file, OAuth export preview (the kit
container border replaces the wrapper's), proxy bulk import preview,
proxy bulk health check, proxy logger.
Tests: jsdom test for the adapter (capped container is a named tab stop,
no own scroll wrapper, no header patch, borderless when framed={false});
AST guard over the dashboard for class caps, capped wrappers and unnamed
capped tables. design-kit-bridge assertions aligned: the header colour and
the opaque viewport now come from the kit table.
Refs #19620
* test(dashboard): template classes count only when whitespace bounds them
A class written against an interpolation (`border-0${suffix}`) can render
as another class, so the single-frame guard no longer treats it as whole
(review on #20181). Fixtures for interpolations adjacent to `border-0` and
`border` added.
Refs #19620
The new lint step would fail release-green-static-profile.test.mjs (Unmodeled workflow command: lint/check:generated-artifacts), the same way the phase-4 step did on #20177. It is a real gate of the lint job, so it is modeled as a hard gate next to check:agent-skills-sync.
The new PR Test Policy step made release-green-static-profile.test.mjs fail (Unmodeled workflow command: pr-test-policy/check:pr-derived-paths; CI run 43593391660, Unit Tests 2/8). It judges a pull request's own diff and prints SKIP in release mode, so it is listed as an exclusion with that reason, like check:pr-evidence.
combo-responses-sse-failure-fallback took ~344 s and vertex-shared-capacity-429-combo-lockout
~326 s (already on v3.8.53). When a PR's new test files reshuffle the unit shards so both land
in one shard, that shard exceeds its 25-minute job limit and is cancelled (#16083, twice).
- The SSE cancellation test leaves the primary stream open after response.failed, so the combo
exits it through the per-target first-output deadline; without an explicit value that is the
cooldown-wait budget + 10 s (310 s). An explicit targetTimeoutMs of 1 s keeps the same path.
- The Vertex lockout file asserts whether a 429 records a model lockout; the default-on
cooldown-aware re-dispatch (covered by combo-cooldown-retry.test.ts) waited out the 30 s
Retry-After hint five times per hinted test. The file's combos now opt out of that wait.
All assertions are unchanged: 18/18 and 17/17, now 13 s and 15 s.
- docs/reference/derived-facts.json: the base merged a provider and the `jev` strategy (394
providers, 238 migrations, 22 strategies) and regenerated the README SVGs; the snapshot follows,
so the generators reproduce those SVGs byte for byte.
- docs/routing/AUTO-COMBO.md: the combo-matrix sentence said "all 21 public strategies" — a test
coverage statement, not the strategy total, but the count extractor reads it as one. The matrix
has no `jev` test, so "22" would be false; the sentence no longer carries a number.
- validate-release-green test: the --full-ci loop of the base computes the bucket with
`fullCiKindFor(g.id, results, g.kind)` and builds `gateEnv`; the wiring assertion follows.
- pr-mode strategy test: compares against the snapshot's strategy count instead of the fixture's.
tests/unit/video-live-stt-server.test.ts covers the mutated open-sse/utils/error.ts;
check:mutation-test-coverage --strict requires it in tap.testFiles.
Owner decisions 1 and 4 of 2026-11-14 (follow-up of #19620):
- Hover-only red ghost buttons, decided screen by screen: the nine row/card
deletes (batch, batch file, Codex profile, quota group, pool, schedule
window, playground preset, tool, NoAuth account) use the kit
destructive-ghost variant; chip x's, input clears, form-row x's and
toolbar/nav actions keep the grey ghost with error ink on hover. The
#19620 guard now fails on any new hover-only red ghost/outline button
that is not destructive-ghost or a listed exception.
- A disabled kit button has pointer-events: none, so a title explaining
why it is disabled never showed. New GuardedAction adapter
(src/shared/components/GuardedAction.tsx) over the kit GuardedAction,
with the legacy Button vocabulary; the ten reason-only titles now pass
as reason (update, file in use, judge model, repeat, set model, max
columns, TPROXY, budget selection, combo step). Busy states stay
disabled; general hints stay as title while the action is available.
New guard test fails on a disabled Button whose title can only be a
reason.
Refs #19620
- media-cost-tracking pins the applied migration sequence; #18353 adds 240 and #16864
adds 241 (renumbered on the train), so both entries join the expected list.
- phi untranslated ratio crossed its +0.5 tolerance once #19328, #19771 and #18359
added keys together; translate the five translatable new strings.
The early targetSupportsEndpoint() guard in handleSingleModelChat returned a JSON 400
before the executor ran. That bypassed the #17858 contract the base pins in
chat-search-provider-error.test.ts (an unclassified executor rejection propagates; a
search-provider rejection after keepalive stays SSE 200 with a sanitized error) and also
turned media-only chat targets away with a search-specific message. Search providers are
already rejected in chat by their executors with search_provider_not_chat.
With #20161 the Release-Green HARD items run with OMNIROUTE_GATE_MODE=pr and the strict comparison moves to the release:refresh-derived --check drift item, so the skip text now says: the release PR, pushes to main, local runs.
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.
locale-parity-mode.test.ts lists every test that imports tests/_helpers/localeParityMode; the fixture's import line made check-test-masking.test.ts look like a new user.
Owner decisions 2026-11-14: the edited-artifact comparison runs in job lint (fetch-depth: 0), right after check:agent-skills-sync, so a PR that regenerates a README SVG or e2e-timings.json wrongly fails in CI (the shallow test-unit checkout could not tell). QUALITY_GATES.md no longer says the step is unwired.
AGENTS.md (protected surface, approved by the owner for this PR): the Quality Gates quick reference says a feature PR never banks a ratchet improvement and leaves the generated files and derived baselines to the release refresh; Hard Rule 9 says the coverage baseline is tightened at release. The approved draft also named the nightly banking PR; that job banks only file-size and complexity shrinks (nightly-release-green.yml, bank-ratchet-shrinks), so that mention was dropped. "fails" reads "flags" while the guard is advisory.
AGENTS.md -> Documentation accuracy gains item 5 (protected surface, approved by the owner on 2026-11-14 for this PR). The Bosnian mirror docs/i18n/bs/AGENTS.md follows in the next translation wave: the derived-files guard keeps a feature PR from writing it.
The .env loader ran at module load, so release:refresh-derived and the tests that import syncUiKeys() got the operator's .env (DATA_DIR, OMNIROUTE_TRANSLATION_*, ...) in their own process. loadDotEnv() is now exported and called by the CLI and by syncUiKeys() only on the translate path, before backendConfig(); the translate concurrency default is read after it, so a value in the .env still applies there.
Owner decision 2026-11-14: check:pr-derived-paths starts with --warn and, in GitHub Actions, adds one ::warning annotation per violation so the advisory result is visible on the PR. A one-line PR drops --warn after the one-time cleanup of the open PRs (plan section 8).
i18n-mirror-refresh.yml runs check:docs-all with OMNIROUTE_GATE_MODE="pr", byte-identical to the same line in feat/derived-p1-gate-modes (#20161), so the two branches merge without a conflict.
The locale-parity helpers (localeParityOptions, localeParityIsReleaseOnly, placeholderParityDeferred) and the mirror-freshness helper (announceMirrorPlan) skip in a feature PR what the release refresh rewrites. countSkips() cannot see them, so the gate now counts each helper (imports excluded) and names it with its effect in the report-only block. The helpers' own unit tests are left out of the list. Report-only, as approved by the owner on 2026-11-14.
check-test-masking.test.ts quotes releaseOnlyUnlessTouched( as fixture text, so the new
report-only block listed the gate's own test. It now skips the self-test family, the same
exclusion the tautology counters already apply; covered by a new test.
(cherry picked from commit e78c2de871)
The comment of the new gate-mode skip tests quoted the skip modifier call and the literal
true skip option; countSkips() reads raw text, so check:test-masking flagged the comment as
two new skips. Reworded without the literals; no assertion changes.
(cherry picked from commit a554be9840)
Review finding: the README SVG / e2e-timings tests moved from t.skip() to
{ skip: releaseOnlyUnlessTouched(...) }, which countSkips() does not see (it matches only
.skip( and { skip: true }), so check:test-masking answered a plain OK for 13 assertions that
a PR run can skip.
countModeConditionalSkips() counts releaseOnlyUnlessTouched( calls per changed/renamed test
file; a net increase is printed on its own report-only block naming each file and where the
edited-artifact comparison runs in a PR (check:generated-artifacts). It does not fail the
gate: whether a mode-conditional skip should block is the owner's decision. countSkips()
and every existing signal are unchanged.
(cherry picked from commit c20f9d67cb)
Owner decision 2026-11-13: reuse the robot token the i18n mirror refresh already opens its PR with (Contents + Pull requests: write) instead of waiting for a new secret. DERIVED_REFRESH_PR_TOKEN still wins when set; with neither, the branch is pushed and the run summary says so.
Security fix; failing checks at merge were the inherited base reds (provider-asset-provenance, useModelImportHandlers, advisory forgotten-sibling-tests crash). Unit shard 3/8 passed 9301/9301 and was cancelled by the job time limit while uploading its coverage artifact.
Security fix; failing checks at merge were the inherited base reds (provider-asset-provenance, useModelImportHandlers, advisory forgotten-sibling-tests crash). fal-native-panel failed in CI but passes 20/20 locally with this change and does not touch search.
Security fix; failing checks at merge were the inherited base reds (provider-asset-provenance, useModelImportHandlers, advisory forgotten-sibling-tests crash).
Security fix; failing checks at merge were the inherited base reds (provider-asset-provenance, useModelImportHandlers, advisory forgotten-sibling-tests crash).
Security fix; failing checks at merge were the inherited base reds (provider-asset-provenance, useModelImportHandlers, advisory forgotten-sibling-tests crash).
Security fix; failing checks at merge were the inherited base reds (provider-asset-provenance, useModelImportHandlers, advisory forgotten-sibling-tests crash).
* chore(dashboard): sync vendored CI UI Kit to v0.0.115
Snapshot 940b0d28 (kit 2026-11-13) via scripts/dev/sync-ui-kit.sh latest.
Brings Button destructive-ghost (#197), Progress bands + info tone (#198),
focusable overflowing Table container (#200), Stat animateFrom + warning
tone (#199), notification card/feed, setup-layout aside and benefits footer.
No new runtime dependency.
* feat(dashboard): use the kit destructive-ghost Button for inline deletes
Kit 0.0.110 (#191) added a quiet destructive variant. The Button adapter
maps destructive-ghost onto it, and the 22 ghost buttons that drew error
ink at rest for delete/remove/revoke actions (proxy, API key, invite,
relay token, webhook, connection, cache entry, ACP agent, ...) use it
instead of hand-made text-error/hover:bg-error classes.
A source guard fails on any new ghost Button with error ink at rest;
status-coloured ghost buttons are listed with their reason.
Refs #19620
* feat(combos): count Combo Studio run numbers from the previous value
Kit 0.0.115 (#189) adds Stat animateFrom="previous" and a warning tone.
The run summary numbers were static on purpose because the ticker
restarted from zero on every attempt event; targets and failed attempts
now count on from the number on screen. A run still in progress shows
its outcome in the warning tone instead of the neutral one.
Refs #19620
* feat(usage): draw the Kilo Pass meter with kit Progress bands
Kit 0.0.112 (#190) adds allocation bands with their own tracks and an
info tone. KiloPassMeter drops its hand-made bar: the paid and bonus
pools are kit bands (success and info), each sized by its capacity with
its own used fill and legend, paid credits spent first. Each band is a
named progressbar inside a group named by the meter label; the header
text, legends, remaining, renewal and balance rows are unchanged. A zero
total still draws an empty determinate bar.
Refs #19620
* fix(analytics): name the overflowing table scroll containers
Kit 0.0.114 (#192) makes an overflowing Table container focusable and
exposes it as a region only when it has a name (scrollLabel, caption or
the table aria-label). The analytics tables only passed scrollbarLabel,
which names the persistent scrollbar, so on a phone their containers
would be focusable but unnamed. ModelTable, ApiKeyTable, ProviderTable,
RequestCountTable (new optional tableLabel, set to the section title)
and the Cache Health by-model table now pass scrollLabel.
Refs #19620
* test(combos): the running Combo Studio outcome uses the kit warning tone
design-kit-bridge pinned running = default because the kit Stat had no
warning tone; kit 0.0.115 (#189) added it and the studio now uses it.
Refs #19620
* fix(usage): translate the Kilo Pass band usage text
The kit band valueText (spoken value of each progressbar) was built with
an English "of". It now goes through a new usage.kiloPassBandUsage
message with used/total placeholders, added to all 67 catalogs, with the
English string as fallback. CodeRabbit review on #20163.
Refs #19620
check:docs-counts drops AGENTS.md, llm.txt, the services guide and the skills from the derived
count checks (README.md and the docs keep them) and adds one STRICT invariant per
agent-instruction file — AGENTS.md, llm.txt, the bs fork (Bosnian patterns), the services guide,
agentSkills.ts, skills/README.md and every skills/*/SKILL.md — that fails any provider,
migration, MCP-tool, scope, strategy, scoring-factor or mode-pack count there, in both gate modes.
It reuses the gate's own claim patterns, now named constants.
Tests: #15159 DOC-01 now proves the instruction files point to the strategy registry and carry
no count or inline list (the AUTO-COMBO.md table is still checked against the code); the skill
provider-count test proves descriptions and generated skills are count-free and that the
invariant rejects a count; the provider-count coverage test checks the skill surfaces through
the invariant. QUALITY_GATES.md documents it; changelog fragment.
Plan 2026-11-13 (derived numbers resolved only at release), phase 2. AGENTS.md, llm.txt and its
66 docs/i18n copies, the bs AGENTS.md fork, open-sse/services/AGENTS.md, agentSkills.ts (and the
three skills generated from it), skills/README.md and the curated skill blocks no longer state the
provider, migration, MCP-tool, MCP-scope, routing-strategy, scoring-factor or mode-pack counts.
They point to the source (ROUTING_STRATEGY_VALUES, DEFAULT_WEIGHTS, src/lib/db/migrations/) and
to `npm run facts`, and AGENTS.md says so once. The inline strategy lists go too: llm.txt's had
already lost `expiry-first`, and the bs fork still said 381 providers, 228 migrations and
20 strategies.
On 2026-11-13, 37 open PRs edited AGENTS.md's count lines and 36 those of llm.txt (dragging the
66 copies); after this change feature PRs have nothing there to edit, and the release refresh
never has to rewrite an agent-instruction file.
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.
tests/unit/skill-write-routes-always-protected.test.ts covers src/server/authz/routeGuard.ts, a mutated module, so check:mutation-test-coverage --strict requires it in stryker.conf.json tap.testFiles.
StreamSection and RequestLoggerDetail started a 2 s setTimeout to reset their copied flag and never cleared it. When the Vitest worker outlived jsdom by two seconds, the timer fired after teardown and threw "window is not defined" as an unhandled error, so test:vitest:ui exited 1 with every test green (base-red, #19329). A small useTransientFlag hook keeps the timer in a ref and clears it on unmount. Two new tests fail on the old code (one reset timer left pending after unmount) and pass now.
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.
#18154 pins the old inline npm audit command for audit:deps in config/quality/release-green-static-profile.json; #18156 moves package.json audit:deps to node scripts/quality/audit-dependencies.mjs. Each PR is green alone; combined, validateFullCiProfile rejects the stale pin (Invalid or stale full static gate: audit:deps). Point the pin at the new entrypoint. tests/unit/build/release-green-static-profile.test.mjs: 15/15.
check-test-masking.test.ts quotes releaseOnlyUnlessTouched( as fixture text, so the new
report-only block listed the gate's own test. It now skips the self-test family, the same
exclusion the tautology counters already apply; covered by a new test.
The comment of the new gate-mode skip tests quoted the skip modifier call and the literal
true skip option; countSkips() reads raw text, so check:test-masking flagged the comment as
two new skips. Reworded without the literals; no assertion changes.
The contribution golden path still told feature PRs to keep the en/pt-BR
CLI catalogs aligned and put i18n:sync-ui:dry and a release-mode value-drift
run in the local loop, which reports every key the cycle added and pushes
the author to edit locales. The feature PR template asked for strings in
"the i18n catalogs", and the translate-new-keys.sh header said a branch that
adds keys must translate them before its PR opens.
Now: a feature PR edits en.json only and previews CI with --mode=pr; the
template asks for en.json only; translate-new-keys.sh names its callers
(release refresh, translation waves). I18N.md and QUALITY_GATES.md document
the changed-catalog judgment of pr mode, the placeholder-rename case (prefer
a new key) and localeParityMode.ts as the only sanctioned mode-conditional
skip; the ci.yml i18n UI Coverage comments and step names say the same.
Review findings: docs/diagrams/README.md (12 rows + the workflow note) and DESIGN_SYSTEM.md
still said a stale SVG fails test-unit in every PR, and QUALITY_GATES.md promised 'only an
SVG the PR edits' in test-unit, where the shallow PR checkout has no base, and called release
mode byte-for-byte identical although check:agent-skills-sync prints one added mode line.
The docs now say: release mode fails a stale SVG; in a PR, check:generated-artifacts (full
history, fail-closed) judges an edited SVG; the unit tests skip with base-unresolved in
test-unit; release mode adds at most one mode line; the new check is not wired into ci.yml
yet. The changelog fragment mentions the new check and the test-masking report.
Review finding: the README SVG / e2e-timings tests moved from t.skip() to
{ skip: releaseOnlyUnlessTouched(...) }, which countSkips() does not see (it matches only
.skip( and { skip: true }), so check:test-masking answered a plain OK for 13 assertions that
a PR run can skip.
countModeConditionalSkips() counts releaseOnlyUnlessTouched( calls per changed/renamed test
file; a net increase is printed on its own report-only block naming each file and where the
edited-artifact comparison runs in a PR (check:generated-artifacts). It does not fail the
gate: whether a mode-conditional skip should block is the owner's decision. countSkips()
and every existing signal are unchanged.
Review finding: in PR CI the README SVG byte comparison and the e2e-timings completeness
never ran, not even for an SVG the PR edited. test-unit checks out a shallow merge ref with
no base, so resolvePrDiffBase() returns null and releaseOnlyUnlessTouched() skipped
(reason=base-unresolved). A PR allowed by the generated family's companions (generator +
regenerated SVG) passed with a wrong or hand-edited SVG.
- scripts/check/check-generated-artifacts.mjs (npm run check:generated-artifacts): the 12
README diagrams plus the e2e timings seed. release = every artifact strict (what the unit
tests check); pr = only the artifacts the change edits; pr without a diff base = every
artifact strict (fail-closed). Meant for a job with fetch-depth: 0 (the lint job, next to
check:agent-skills-sync); wiring it there is requested from the job's owner.
- resolveDerivedScope() gains onUnresolved: "skip" (default, unit tests) | "strict".
- The unit tests' base-unresolved skip reason now names the check that owns the comparison.
- gate-manifest: new alias, separately-invoked.
Two gaps of the programmatic API the release refresh calls:
- a locale code outside the set it would process (typo, missing from
config/i18n.json, no catalog file, or en) was dropped silently and the
run reported nothing to do; it now throws before writing anything;
- a dry run left out the src/i18n/global-error-messages/*.json files a real
run writes (2 listed vs 5 written in the review fixture). The compact
catalogs are now rendered in memory (renderGlobalErrorCatalog, extracted
from generate-global-error-messages.mjs, whose output is unchanged), so
dry and real runs report the same changedFiles.
A feature PR that renames a placeholder in en.json only ({count} rows ->
{rows} rows), which is what the new rule tells it to do, failed two unit
tests in pr mode: "every locale keeps the placeholders and tags its English
source defines" and "Vietnamese locale preserves every ICU placeholder
name". Correcting the translations instead is refused by
check:pr-derived-paths, so the PR had no way out (review of 2026-11-13).
tests/_helpers/localeParityMode.ts gains placeholderParityDeferred(key). In
release mode it defers nothing. In pr mode it defers the UI keys whose
English value changed since the merge base, which is the set
syncUiKeys({ rewrittenSinceRef }) marks and retranslates at release; every
other key is still judged. When the merge base cannot be read (the
unit-test job checks out one commit) it defers every key: a feature PR
cannot touch a locale catalog, and a PR that does is judged key by key,
placeholders included, by check-key-completeness in the i18n UI Coverage
job, which has the full history. No assertion changes in release mode.
check:test-masking counts .skip( and { skip: true } but not the computed
{ skip: "<reason>" } this helper returns, and its skip signal can never be
allowlisted, so wiring the helper into it would turn this very PR red with
no way out. tests/unit/locale-parity-mode.test.ts pins instead the list of
tests allowed to use the helper (adding one is a reviewed edit) and the
deferral semantics.
- With --json, the pr-mode SKIP / scope lines go to stderr and a skip prints a JSON object
({skipped, mode, reason, detail}) on stdout, so --json output is always JSON again.
- classifyTouchedSkills judged any non-SKILL.md file under skills/<id>/ as generated. The
generator writes only SKILL.md (outside the custom block) and references/**; a PR that adds
an example or a note beside SKILL.md is no longer judged against the generator.
Both are covered by new tests that fail on the previous commit.
QUALITY_GATES.md: mode resolution, what each mode fails, exit codes, where each mode runs
(feature PRs, queue, release PR, Release-Green, release skill, nightly refresh PR),
`npm run facts`, `npm run release:refresh-derived` and the facts snapshot, and how to reproduce
the CI verdict locally. Changelog fragment for phase 1.
Feature PRs no longer write derived numbers, so between releases the tree is behind the live
code by design and any unit test comparing the two would be red on the base itself. Each such
assertion now proves the same property deterministically:
- release mode with injected facts rejects the stale value and accepts the right one;
- the committed docs, skills and SVGs agree with docs/reference/derived-facts.json, and each
generator still reproduces its SVG byte for byte;
- "the release refresh closes the cycle": live facts, collected once per file, ->
planDerivedRewrites applied in memory -> release mode leaves no rewritable STRICT drift.
Pure validator tests are unchanged. The facts failure path keeps its STRICT ERR check and is
now also asserted as an infrastructure exit (2). Suite time drops from one tsx probe per
buildChecks() call to one per file.
syncE2eTimings rewrote the _meta note (its \u2014 escape became a raw em dash) and
counted a new spec's LOC as split('\n').length, one more than the seed's wc -l. It now
escapes non-ASCII like the committed file and counts newlines; the existing test's
expected LOC goes from 4 to 3 for a three-line fixture because 3 is the seed's value
(the old 4 encoded the off-by-one). Two new tests pin the byte-for-byte behaviour.
- 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.
The pr-mode advisory reused the release instruction (run quality:ratchet --update and
commit the tightened baseline in this PR), contradicting the line above it. The
measurement and the instruction are now separate: release mode prints exactly the old
line, pr mode says the improvement is banked by the release refresh / nightly.
The pr-mode SKIP of the completeness gates also covered the PRs that still
edit locale catalogs: translation waves (docs/i18n-*, chore/i18n-*), the
release refresh (chore/derived-*) and translation-only PRs, which
check:pr-derived-paths allows. A wave that deleted a key from ko.json or
overwrote a translation with __MISSING__ failed before and passed after.
check-key-completeness (UI and --catalog=cli) now SKIPs in pr mode only when
the PR changed no locale catalog of that family. Otherwise each changed
catalog is judged against itself at the merge base
(scripts/i18n/lib/touched-catalogs.mjs): no key it had may be lost, no key
en.json lacks may appear, no real translation may become a __MISSING__
marker or the English text (outside untranslatable-keys.json), and no value
the PR changed may break the placeholders/tags of an English value the PR
did not touch (ICU scanner in scripts/i18n/lib/icu-names.mjs, same grammar
as the placeholder-parity test). A catalog new in the PR must carry the
whole en.json key set. Release mode is unchanged.
The ratio and CLI-parity SKIP lines now say where a changed catalog is
judged. The support list of i18n-release-mode-gates.test.ts gains the two
new libs, which the copied check-key-completeness imports.
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.
QUALITY_GATES: the strict judgement of a change that edits mirrors needs a
resolvable diff base (not the depth-1 docs-sync-strict checkout), PR mode
still requires the llm.txt mirrors to agree, the pre-commit hook runs in PR
mode, per-section freshness is coarse for long sections, and the scheduled
refresh syncs llm.txt. The changelog fragment says the same.
Feature PRs now edit only the root llm.txt. The scheduled refresh never ran
sync-llm-mirrors (run-translation and the drift report skip llm.txt), then
ran check:docs-all in release mode and opened no PR when it failed, so one
llm.txt edit would have stalled the refresh of every doc.
The drift step now counts stale llm.txt mirrors with syncLlmMirrors()
--dry-run; a new step syncs them before the check; setup, check and commit
run when either docs drifted or llm.txt mirrors are stale (translation still
runs only for drifted docs: an empty --files would translate everything).
The commit and PR body list llm.txt among the sources. Covered by
tests/unit/i18n-mirror-refresh-llm-sync.test.ts (fails on the old workflow).
tap.testFiles was a hand-kept list of 781 entries (775 unique) and 46 open
PRs touched it. stryker.conf.json becomes stryker.conf.mjs (Stryker 10
auto-discovers it), which computes the list at load time: every unit test
that imports a module in `mutate`, the same rule check:mutation-test-coverage
--strict enforces, now shared in scripts/quality/mutation-test-files.mjs.
The 109 former entries the import rule does not select (barrel/indirect
coverage) stay pinned, so the resolved list equals the old set exactly.
All other options keep their values.
The drift gate and mutation-radiography load the config the way Stryker
does (dynamic import of the default export). stryker.disablebail.json
becomes stryker.disablebail.mjs and spreads the base config: Stryker 10
does not implement "extends", so the redundancy run had none of it.
The mirror-freshness helper threw when an anchor was absent from the English
source, in both modes. Three docs/*-locales tests passed prose anchors that
the tests only used for their negative English-fallback assertion, so a PR
that merely reworded that English sentence failed them, even in release
mode, where the tests never read the English source before.
- analyzeSource() no longer throws: a missing anchor drops the section-level
shortcut and the whole-file hash decides (never looser than the anchor).
The helper test that asserted the throw (added on this branch) now asserts
the fallback in both modes.
- vision-key-scope and remote-token-privilege anchor only on the identifier
the test already pins in every mirror.
- The header notes that freshness is per ## section, which is coarse for
long sections such as the QUALITY_GATES gate inventory.
The direct-run guard added with the syncLlmMirrors() export compared the
module URL (a real path) with argv[1] as invoked, so a symlinked checkout
turned the CLI into a silent no-op that exited 0. The old script always ran.
The guard now resolves argv[1] with realpathSync first; covered by a test.
Two review findings on the PR-mode split of check-docs-sync:
- The docs-sync-strict job checks out at depth 1, so the diff base never
resolves there and a hand edit to one docs/i18n/<locale>/llm.txt passed
as SKIP. PR mode now runs a check that needs no base: every llm.txt
mirror must exist, keep its separator and carry either the root body or
the body most mirrors share. A base that moved leaves them all equally
stale and passes; a single hand-edited mirror fails. Release mode is
unchanged (same lines and exit code as the script before the split).
- The pre-commit hook ran the script without a mode, i.e. release mode
locally. After a feature PR that edits only the root llm.txt merged,
every later commit on that base would be blocked until the wave synced
the mirrors. The hook now passes --mode=pr: a commit is judged on what
it does; mirrors it writes are still judged strictly.
The README SVG byte-compare tests and the e2e-timings completeness test skipped
themselves with `t.skip()` inside the body, which check:test-masking counts as a new
unconditional skip. They now pass the same condition as the `{ skip: <condition> }`
test option, the form 42 other unit tests already use for environment-conditional
skips (platform, network interface). The condition is unchanged:
releaseOnlyUnlessTouched() is false — the assertion runs — in release mode and in a
PR that edits the artifact. Assertions untouched; check:test-masking against the
contract base: OK.
- docs/guides/I18N.md: new "Feature PRs touch en.json only" section (what a feature PR
edits, what check:pr-derived-paths rejects, who completes the locales, --mode=pr to
preview, tests assert en.json and not every locale); the parallel-runner section is now
for the release refresh and translation waves; --rewritten-since / --prune-extra /
--keep-extra; the CLI-locale and best-practice lists drop "translate in the PR".
- docs/architecture/QUALITY_GATES.md: i18n-ui-coverage table marks which gates run in
both modes and which in release mode only (adds the missing ICU and key-completeness
rows; the ratio gate is blocking, not advisory: its step has no continue-on-error), a
"Two modes" paragraph, the mode note in the key-completeness, new-key and value-drift
sections, and the check:cli-i18n row. Mirror and generated-file rows are untouched.
- changelog.d/maintenance/0000-i18n-ui-keys-release-mode.md (PR number to be filled in).
No behaviour change in the workflow: the scripts resolve pr/release themselves through
scripts/check/lib/gateMode.mjs. The job header explains the two modes, the
release-mode-only steps say so in their names, and the coverage floor step gets a name and
the measurement that keeps it in both modes (every locale at 100 % on 2026-11-13; the
largest recorded cycle, ~1,352 keys, moves it about 8 points against a 65 % floor).
BASE_REF already reaches both diff-aware steps (origin/main on the release PR).
config/quality/derived-paths/translation.json: a feature PR may edit en.json (UI and CLI)
and the English docs; these belong to the release refresh, the translation waves and the
scheduled mirror refresh:
- ui-locale-catalogs: src/i18n/messages/*.json except en.json
- cli-locale-catalogs: bin/cli/locales/*.json except en.json
- docs-i18n-mirrors: docs/i18n/** and .i18n-state.json
- ui-translation-ratio-baseline: config/quality/i18n-translation-baseline.json (measured
on the catalogs; npm run i18n:check-ratio:update after a refresh)
Writers: release/v*, docs/i18n-*, chore/i18n-*, chore/derived-*. The merged i18n PRs of
the repo (318 found by title) used docs/i18n-wave-*, docs/i18n-<doc>-*, docs/i18n-g54-*
and chore/i18n-mirror-refresh; all match. Companions: changelog.d/** and
src/i18n/global-error-messages/*.json. The compact error catalogs are regenerated from
the catalogs on every build (build-next-isolated) and pinned by
tests/unit/global-error-messages.test.ts. A feature PR that edits
publicSystem.globalError in en.json has to regenerate en.json there (and the others when a
key is removed), so they cannot be a category. A translation-only PR may carry them.
QUALITY_GATES.md documents the two families, the writer branches, and how
check:agent-skills-sync, the README SVG tests, the e2e-timings test and
--require-tighten behave in each gate mode. CONTRIBUTION_GOLDEN_PATH.md no longer tells
a provider PR to commit the regenerated PROVIDER_REFERENCE.md. Changelog fragment
(number assigned when the PR opens).
Same rule as the completeness gates (phase 4 of the plan "derived numbers and texts
resolved only at release"): a feature PR adds keys to en.json only, so "locale X carries
every key of en.json" can only hold after the release refresh.
Found by adding one key to src/i18n/messages/en.json and bin/cli/locales/en.json only and
running every unit test that reads a catalog (212 files): exactly these failed —
cli-i18n-catalog (zh-CN / zh-TW parity), i18n-pt-br ("every key present in en.json") and
i18n-vi-completeness (key parity, and the "missing" entries of the placeholder and ICU
checks). The pt-BR top-level-sections test of cli-i18n-catalog fails the same way when
the new key opens a new section.
tests/_helpers/localeParityMode.ts resolves the mode with scripts/check/lib/gateMode.mjs
(env only). In release mode (local runs, Release-Green, pushes to main, the release PR)
every assertion is unchanged. In pr mode the parity tests skip with the reason in the
report, and the vi placeholder/ICU checks keep judging every key vi carries and only stop
reporting absent keys. No assertion is removed or loosened in release mode; verified with
the probe key: release mode 6 failures as before, pr mode 0 failures and 5 skips.
config/quality/derived-paths/generated.json: docs/reference/PROVIDER_REFERENCE.md, the
twelve generated README SVGs (README_DIAGRAMS), skills/*/references/** and the 31
SKILL.md files with no hand-written custom block. Writers: release/v*, chore/derived-*.
Companions: changelog.d/**, the generator scripts and their tests, so a generator
change can still ship with its own output. Hand-drawn SVGs, the Mermaid exports and the
SKILL.md files with a custom block are not claimed.
config/quality/derived-paths/baselines.json: config/quality/e2e-timings.json only, the
one measured baseline no gate asks a feature PR to edit any more. Policy files and the
ceilings a feature may legitimately edit with code stay out.
Against the 321 open PRs of 2026-11-13: 43 carry files of these families (30
PROVIDER_REFERENCE.md, 30 README SVGs, 10 skill references, 4 generated SKILL.md, 2 e2e
timings).
.gitattributes: linguist-generated=true for the generated reference, the twelve SVGs,
the skill references and .i18n-state.json. The generated SKILL.md files and the
docs/i18n/*/llm.txt mirrors are agent-instruction surface and stay visible.
tests/unit/derived-paths-generated-family.test.ts keeps both lists exact (driver outputs,
custom-block scan, files on disk, attributes).
check-quality-ratchet.mjs --require-tighten failed a PR whose metric improved beyond
tightenSlack unless the PR also edited quality-baseline.json, so two improving PRs
conflicted on the baseline. Banking belongs to the release refresh / nightly (plan
2026-11-13, phase 5).
In pr gate mode the un-banked improvement is printed as information and the run
passes; a regression fails exactly as before. Release mode (push, schedule, the
release PR, local runs) is byte-identical to the previous script on the 12-case matrix
(with/without _policy x improved/regressed/equal x with/without --require-tighten),
and the velocity-phase advisory (_policy.requireTighten=false) is unchanged.
The existing tests now pin OMNIROUTE_GATE_MODE=release in their spawn helper: they
describe release behaviour, and a CI pull_request run would otherwise resolve to pr
mode. No assertion was removed or relaxed; four tests cover the pr/release split.
Owner decision 2026-11-13 (plan "derived numbers and texts resolved only at release",
phase 4): a feature PR adds or rewrites keys in en.json and touches no other locale, so
the gates that compare every locale with en.json judge the base, not the change.
With scripts/check/lib/gateMode.mjs, these gates print one
"SKIP reason=pr-mode — <mode>: <why>; the strict check runs in release mode (...)" line
and exit 0 in pr mode (feature PR, merge_group, omni-queue), and run unchanged in release
mode (release PR, pushes to main, workflow_dispatch, local runs):
- check-key-completeness (UI and --catalog=cli)
- check-new-key-coverage (also --json)
- check-ui-value-drift (also --json)
- check-translation-ratio (the gate path only; --report, --json and --update still run)
- check-cli-i18n: the t()-key check runs in both modes; pt-BR sections and zh-CN/zh-TW
parity skip in pr mode.
Release mode was compared against the 01258da1 scripts on this tree and on a tree with an
en.json-only key plus a rewritten value: same stdout/stderr and exit code for every gate
(UI, CLI, new-key, value drift, ratio, cli-i18n).
The shared line lives in scripts/i18n/lib/release-mode.mjs. The new test runs each real
script in a throw-away git repo: both modes, the event-derived mode, and the release PR
(BASE_REF=main) judging every key of the cycle until syncUiKeys completes the catalogs.
Kept in both modes: check-ui-keys-coverage (65 % floor) and check:ui-icu.
tests/unit/balance-e2e-shards.test.ts asked every PR that adds an e2e spec to add an
entry to config/quality/e2e-timings.json (two of the 321 open PRs on 2026-11-13), while
the shard packer already gives a spec without an entry the median weight.
- balance-e2e-shards.mjs gains `--sync [--dry-run]` / syncE2eTimings(): new specs get
their LOC (the seed's proxy), entries of deleted specs are dropped, every other value
and the key order stay. Exported for release:refresh-derived.
- The completeness test runs in release mode, or when a change edits the timings file;
a feature PR skips it with the shared SKIP line. New test for the sync writer.
Plan "derived numbers and texts resolved only at release" (2026-11-13), phase 4: feature
PRs add keys to en.json only, and the non-English catalogs are completed once per release
by release:refresh-derived. sync-ui-keys.mjs gains what that refresh needs:
- syncUiKeys({ catalog, locales, translate, pruneExtra, rewrittenSinceRef, dryRun, root })
returns { changedFiles, added, pruned, markedRewritten, translated, failed, locales[] }
with repo-relative paths. A dashboard run that changed a catalog also regenerates the
compact global-error catalogs. translateFns is a test seam; the default is the real
backend client.
- --rewritten-since=<ref> (API: rewrittenSinceRef) marks as __MISSING__:<new english> the
translations of values rewritten since the merge base with <ref> that the locale left
untouched: the same set check-ui-value-drift reports (findStaleTranslations, cosmetic
rewrites excluded). Off by default.
- mergeMissing() now reports extraPaths and takes { pruneExtra }. The merge always dropped
keys en.json no longer has, so the CLI default stays pruning (callers unchanged);
--prune-extra names it, --keep-extra opts out. The API defaults to pruneExtra: false and
the refresh passes true.
- isDirectRun no longer throws when the module is imported without argv[1].
The twelve README diagrams are generated from live catalogs and counts, and the
release refresh regenerates them (plan 2026-11-13, phase 5). The "committed file is
exactly what the generator produces" test of each diagram now skips in pr gate mode
when the change does not edit that SVG (scripts/check/lib/derivedArtifactScope.mjs),
so a feature PR is never red because a sibling moved the catalog. Release mode and a
PR that edits the SVG keep the byte-for-byte assertion unchanged; every other test in
these files (outlines, copy strings, palettes, the counts-gate readers) is untouched.
I18N.md no longer tells a PR that edits a core doc to bring its 66 mirrors
along. The mirrors, the llm.txt copies and .i18n-state.json are derived
files rewritten by the translation wave (docs/i18n-* / chore/i18n-*
branches, the scheduled refresh) and the release; the wave commands
(i18n:run, --adopt, sync-llm-mirrors) are documented as wave steps.
QUALITY_GATES.md describes the PR/release modes of check:docs-sync, the
mirror-content unit tests and the docs drift gate, and corrects the
"i18n translation drift" row (it reads docs/i18n mirrors, not UI keys;
advisory on PRs, strict on push and nightly).
Adds the maintenance changelog fragment (0000- prefix until the PR number
exists).
The generated skills (skills/<id>/SKILL.md, skills/<id>/references/**) are rewritten
from the catalog, docs/openapi.yaml and the CLI registry. Feature PRs that added routes
regenerated them and conflicted with every sibling doing the same; the release refresh
regenerates them once instead (plan 2026-11-13, phase 5).
The dry-run check now reads the gate mode (scripts/check/lib/gateMode.mjs):
- release: unchanged — every skill, same table, same exit codes (0 in sync, 2 drift);
one line with the mode is appended to the human output (the --json output is
byte-identical);
- pr: only the skills whose generated text (outside the hand-written custom block) or
references/ the change edits are regenerated and compared, still exit 2 on drift; a
custom-block-only edit or an untouched skill prints
"SKIP reason=pr-mode — ...; the strict check runs in release mode" and exits 0.
--apply ignores the mode. Proved against the 01258da1 script: release output equal
apart from the mode line, exit 0 clean and exit 2 with a hand edit in cli-a2a; pr mode
exit 2 for that hand edit and SKIP for a custom-block-only edit in omni-mcp.
Plan 2026-11-13 (derived files are written at release), phase 5. A check that
compares a generated file with its generator means two things now:
- release mode (push, schedule, the release PR, local runs): every artifact is
compared, exactly as before;
- pr mode (feature pull_request, queue batch): only an artifact the change itself
edited is compared (an edited generated file must still be exactly the generator
output); the rest is the release refresh's, so drift the base accumulated is never
the PR's failure. No resolvable diff base skips, like the other diff-aware gates.
scripts/check/lib/derivedArtifactScope.mjs builds on the shared gateMode.mjs and
gives node:test a `skip` reason with the shared SKIP wording.
PR mode skipped both translation-mirror checks for every pull request,
including the translation wave's own PR, which is the one that writes them.
In PR mode the checks now run strictly when the change writes mirrors:
- the head branch is a declared writer of a derived-paths family that owns
docs/i18n/** (config/quality/derived-paths/*.json, e.g. docs/i18n-* and
chore/i18n-*): both mirror checks run strictly;
- otherwise, when the PR diff base resolves (BASE_SHA, origin/<base>, the
active release line) and the change itself edits
docs/i18n/<locale>/llm.txt or docs/i18n/<locale>/CHANGELOG.md, the
matching check runs strictly. A depth-1 checkout with no base keeps the
SKIP, like the other diff-aware gates.
Release mode is untouched (same output on the current tree).
scripts/i18n/sync-llm-mirrors.mjs now exports
syncLlmMirrors({ root?, dryRun?, log?, warn? }) returning
{ changedFiles, updated, unchanged, missing, locales, skipped } with
repo-relative paths, so release:refresh-derived and the translation wave can
call it instead of shelling out. The library call is silent by default.
The CLI is unchanged (same stdout/stderr lines and files written, checked
against the previous script on a copy of the 66 mirrors) and gains
--dry-run, which lists the mirrors that would change without writing. The
direct-run guard uses pathToFileURL, so importing the module no longer runs
the sync.
check-docs-sync.mjs reads the gate mode from scripts/check/lib/gateMode.mjs.
Release mode (push, schedule, the release PR, any local run, the pre-commit
hook) runs every check exactly as before: same lines, same exit code; the
only addition is a first line naming the mode.
PR mode keeps the checks a feature PR can break in its own sources:
package.json vs docs/openapi.yaml version, the root CHANGELOG [Unreleased]
heading and latest release, and the superseded-docs guard. It skips, with a
"SKIP reason=pr-mode" line, the two checks on derived files: the 66
docs/i18n/<locale>/llm.txt exact copies and the version sections / size of
the translated CHANGELOG.md mirrors. Feature PRs no longer write docs/i18n;
the translation wave (sync-llm-mirrors) and the release
(release:sync-changelog-i18n) do.
The jobs that run it (docs-sync-strict, Docs accuracy) need no change: the
mode comes from the Actions event. An invalid --mode fails closed.
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 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.
cycle-docs-mirror-contract, resilience-pre-dispatch-docs-mirrors,
cli-env-quality-docs-mirrors and docs/{remote-token-privilege,
route-guard-import,vision-key-scope}-locales pin an English contract in all
66 translated mirrors. A feature PR that changes that contract (and the test
literals) had to ship 66 translations in the same PR. They now take the
locale list from tests/_helpers/mirrorFreshness.ts: every locale in release
mode (unchanged behaviour), and in PR mode only the mirrors whose anchored
English section is unchanged since their translation.
Nothing is removed: every content assertion is still made for every locale
in release mode, and the target_hash provenance checks (mirror bytes ==
recorded translation) still run for every locale in both modes. The
remote-token, route-guard and vision-key tests move the provenance assert
to the top of the loop so it is not gated by the freshness plan.
tests/_helpers/mirrorFreshness.ts decides which docs/i18n mirrors a test that
pins a contract in every locale must assert. Release mode (push, schedule,
release PR, local run) asserts every mirror, as before. PR mode asserts only
mirrors that are current with the English source per .i18n-state.json: the
record's source_hash equals the source bytes, or every `## ` section holding
one of the test's anchors still hashes to a recorded section_hashes entry
(the same split run-translation.mjs writes). Stale mirrors are skipped with a
"SKIP reason=pr-mode" diagnostic and left to the translation wave and the
docs drift gate. Untracked mirrors are asserted; an anchor missing from the
English source throws in both modes.
The mode comes from scripts/check/lib/gateMode.mjs.
Plan 2026-11-13 (derived numbers and texts resolved only at release), shared contract
for phases 4 and 5:
- scripts/check/lib/gateMode.mjs resolves pr|release for every gate that judges derived
content: --mode, then OMNIROUTE_GATE_MODE, then the Actions event (feature pull_request,
merge_group and omni-queue pushes are pr; push, schedule, dispatch, the release PR and
local runs stay release, the strict behaviour of today). It also resolves the PR diff
base and the changed files.
- scripts/check/check-pr-derived-paths.mjs fails a feature PR that carries files a
refresh owns, per family declared in config/quality/derived-paths/*.json. A PR that only
touches one family (a translation fix) and the family's writer branches are allowed;
queue batches are skipped. No family is declared yet: phases 4 and 5 add theirs together
with the gates they switch to release mode.
- Wired as a step of the PR Test Policy job.
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 Textarea adapter now forwards label to the kit Field, so the full
JSON template editor drops its hand-written <label> and uses it; the form
test asserts the textarea keeps an associated label.
- chat: the capability guard for non-chat providers now returns the typed
search_provider_not_chat code (invalid_request_error), so /v1/messages and
/v1/responses keep the #17858 contract (search-provider-chat-rejection-routes-17858).
- combos/[id]: cast the normalized capability routes back to the update schema type (TS2322).
- music/generations: dispatchMusicModel accepts the validated body's `duration?: unknown`
(TS2345 on the direct dispatch call).
- skills: regenerate omni-inference endpoint references for the new /v1/search and
/v1/web/fetch combo descriptions (check:agent-skills-sync).
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>
Resolve the conflicts with the base, which added the
CODE_ASSIST_INELIGIBLE_ONBOARD_LEGACY_TIER flag (#18060) next to this
branch's PII_REVERSIBLE_VAULT_ENABLED flag:
- featureFlagDefinitions.ts: keep both module imports.
- feature-flags-settings / server-owned-tool-loop-flag tests: both flags
are counted, so the catalog total is 123.
- FEATURE_FLAGS.md: the catalog header and the API example now say 123.
PII_REDACTION_ENABLED and PII_RESPONSE_SANITIZATION still default to
"false" (Hard Rule 20).
Base added migrations 237-239, so the custom JSON node migration moves to
240_provider_node_custom_json_config.sql (test name and guide updated).
Count conflicts in AGENTS.md, llm.txt, README.md and the docs/i18n mirrors
took the base side, then the migration count was bumped to the merged
tree's 237 SQL files (llm mirrors via scripts/i18n/sync-llm-mirrors.mjs);
check:docs-counts reports no strict drift.
Renumber the seen_models migration to 240 (base took 236-239) and carry the +1 migration count (237) onto the base docs and mirrors. Move the New models count chip and unread badge onto the kit Badge (no font-bold / sub-floor text sizes) for the base's type-scale ratchet.
Since #19254 a provider with a connection imports through the model
sync, so the case added by #19337 (inside the model-sync block, with an
active connection) never reached POST /api/provider-models and failed on
release/v3.8.54. Move it, with the same assertions, to the no-auth
listing block, where the hook does create the rows. Verified that
removing the supportsVision forwarding from the hook fails it.
The quota-preflight rotation aliased the selector into a local variable, so
the hard-lease credential inventory stopped seeing the codex 429 rotation site
(providerExecutionPipeline.ts counted 1 instead of 2). Call both arms directly
off the injected connection context and record the extra call expression in
the inventory (2 -> 3, still class B, same allowAccountRotation gate).
Also list tests/unit/codex-failover-quota-preflight-18425.test.ts in
stryker.conf.json tap.testFiles: it covers src/sse/services/auth.ts, a mutated
module, and check:mutation-test-coverage --strict flagged it as missing.
CodeQL (js/incomplete-url-substring-sanitization, 3 high) flagged the
three startsWith("https://stream.replicate.com") checks in the Replicate
executor test: a raw prefix also accepts stream.replicate.com.evil.test.
The test now compares the parsed protocol and hostname through a small
isReplicateStreamUrl() helper. Assertions are unchanged.
Co-authored-by: jowimila <127446097+jowimila@users.noreply.github.com>
CodeQL js/incomplete-sanitization flagged the ASSET.replace(/\./g) escape in the
CSP-directive test. Assert the full error string with equality, which is stricter
than the regex and needs no escaping.
Brings the recut up to release/v3.8.54 at 2f2c1957. The base already
contains the original #19206 (bf8a11df), which ships the same Replicate,
Cerebrium, Hetzner and Grokified code as this recut, so every source,
test and snapshot file merges to the base copy.
The count-only conflicts (AGENTS.md, llm.txt and its mirrors, README,
docs, README diagrams and their generators, skills, package.json) keep
the base side: the providers are already counted there (393). The
reserved-prefix test keeps the base side, which already pins 450 with the
four new prefixes. This recut's changelog fragment is dropped because the
base's changelog.d/features/19206-free-llm-providers.md already records
the same providers with credit.
Co-authored-by: jowimila <127446097+jowimila@users.noreply.github.com>
recordKeyHealthStatus wrote the whole per-request providerSpecificData, so
request-local values landed on the shared connection and a stale snapshot
overwrote concurrent edits. It now merges only apiKeyHealth in a transaction,
and resolveKeyForRequest no longer returns a sticky key in 429 cooldown.
GitLab, GHE Copilot, CLIProxyAPI, 9Router, Dario, GLM, GitHub Copilot auto,
NLP Cloud and 1min.ai called the global fetch for their upstream requests, so
redirects were followed with no guard check, cloud metadata included. They now
use dispatchGuarded, which follows redirects by hand and checks every hop.
The lazy body restarted at every BEGIN header and ran to the end of the text
when no END marker followed, so a body of repeated headers cost the square of
its size on the event loop. The body may no longer contain "-----", so each
scan stops at the next marker.
/api/agent-skills/generate (prune deletes host directories) and the
marketplace and skills.sh install routes (global skill injected into every
key's requests) checked auth only when login was on. They are now
ALWAYS_PROTECTED and call requireManagementAuth with alwaysRequireAuth.
/v1/search can be called without a credential, so a caller-supplied
provider_options.baseUrl on loopback or LAN let anyone make the server fetch
internal services. A caller base URL now must be public on the first hop, on
every redirect and at connect time; the operator's stored base URL keeps
loopback and LAN.
joi 18.2.9 (pulled by wait-on ^18.2.9) is affected by GHSA-4528-x5fx-h6hg,
a quadratic-time split in string().email({ multiple: true }); fixed in
18.3.1. This is the last HIGH advisory left once mongoose moves to 9.12.1,
and it keeps check:vuln-ratchet red on release/v3.8.54 (#19329): 8 > 7.
Lockfile-only update via `npm update joi --package-lock-only`; joi's
dependency set is unchanged. With both bumps, osv-scanner reports 7
(LOW=1, MODERATE=6) against the baseline of 7, and npm audit has no
high or critical advisory.
#15201 recorded auditedCommit 959ff4dd, the merge commit on its own branch.
The squash merge left that object unreachable from release/v3.8.54, so
check:provider-asset-provenance fails in CI on the base and on every PR
("auditedCommit object does not exist", release-green run 42875024212, #19329).
895c0f35 is the squash of #15201 on the release branch. Its public/providers
tree is identical to 959ff4dd (146 files, empty diff), so the recorded hashes
still describe the audited snapshot.
Recut of #19206 keeping only the four providers:
- Replicate: chat executor on the predictions API (native SSE relay,
polling fallback with cancel on deadline, real token usage from
metrics, owner/name:version models, same-origin Bearer guard, errors
through buildErrorBody/sanitizeErrorMessage). Joins the existing
Replicate video entry as an llm+video catalog provider.
- Cerebrium: per-deployment /run Base URL used verbatim; a connection
without a Base URL fails fast with a 400.
- Hetzner Inference and Grokified: OpenAI-compatible registry entries
with live model discovery.
Provider counts move 388 -> 392 (digit-only), PROVIDER_REFERENCE is
regenerated, and the executor-map and translate-path goldens include
the new entries.
Co-authored-by: jowimila <127446097+jowimila@users.noreply.github.com>
After the release merge the catalog reached the 1440-line cap. The
non-mutating PII_RESPONSE_SANITIZATION_MODE definition moves unchanged
into piiVaultFeatureFlag.ts and keeps its position in the list; the two
data-mutating PII flags (Hard Rule 20) stay in the catalog.
Keeps the contributor's approach (no blob: module script; same-origin
first-party chunks loaded with a native dynamic import() through
page.evaluate) and closes the review items on top of it:
- The installer is built as source text by
buildChatGptWebBridgeInstallerSource() instead of a function literal.
Playwright serializes a function with toString() after tsx/esbuild or
the Next bundler ran, and tsx already rewrites the inline import() into
an interop wrapper and injects __name(), which does not exist inside
chatgpt.com. The text form also keeps one source of truth for the
integrity resolution (buildChatGptWebIntegrityResolutionSource) and
removes the dead buildBridgeModuleSource that failed lint.
- Restore the CSP diagnosis from #14773: the installer listens for
securitypolicyviolation and reports "csp: <directive> blocked <url>",
extracted from Playwright's prefixed message.
- Retry only a destroyed execution context; a navigation timeout is no
longer retried. One shared helper for both page probes.
- The session preflight reports a credential failure only for 401 or a
JSON session without a user; a 403/429/5xx or a non-JSON challenge page
becomes "session check is unavailable", classified as a local bridge
failure so a transient answer cannot put the account on cooldown.
- Prettier on the contributor's files; tests for the installer (legacy and
integrity paths, validated URLs, CSP naming, no blob/__name), the
navigation-timeout case and the session status split.
Verified in headless Chromium under script-src 'self': a blob module is
blocked, the installer loads a same-origin chunk, and a cross-origin
import is refused and named as csp.
Co-authored-by: GodsQuantum <193283917+GodsQuantum@users.noreply.github.com>
Carries the three items worth keeping from the closed#18165 draft:
verify repository, event and ref before a workflow_run deploy, stop
restoring a package-manager cache in publishing and opencode workflows,
and pin the Semgrep image by digest. The electron cache contract is
inverted on purpose and four zizmor cache-poisoning ignores are removed.
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.
Resolve the count-only conflicts with #15201 (chatgpt): README and
ARCHITECTURE keep this branch's lines, the three generated README SVGs take
the base copy and are regenerated in the next commit.
Move the capability projection and ordering modules under open-sse so the engine
gains no new dependency on the app, and split the functions flagged by the
complexity ratchets. Behavior is unchanged.
The catalog treated every no-auth provider as always active, so aug/* and zc/* models were advertised on hosts without the CLI and failed at request time. A new cached host check (AUGGIE_BIN/ZCODE_BIN, installer paths, PATH) is resolved once per catalog build; an explicit connection row still keeps the provider listed, and other local-CLI providers stay fail-open.
chatCore needs hasMintedPiiTokens, which added an open-sse -> src edge. The vault only
depends on node builtins, so it now lives in open-sse/utils; src/lib/pii/tokenVault.ts
stays as a re-export for the app side and the tests.
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.
Resolve the Codex Web Search (#17933) collision: keep both keenable-search
and codex-search in the registry, aliases, handler imports and tests
(24 search providers, 8 fetch providers).
Projection ran on every chat request and normalized all saved combos, scanning
every name per string step (54 ms with 10 combos, 2.1 s with 500). Walk only the
requested combo's DAG with one precomputed name set.
Also move the capability tab strings to the combos catalog and add a registry
wide guard that chat-capable models stay chat-capable.
Tool-call reasoning was cached under the bare tool call id, which clients can
reuse. Entries are now keyed by the API key and session that produced them, and
every replay path reads with the same scope.
A blocking hook decides on the request, so skipping it above the per-plugin rate
limit let the request through unchecked. The limit now covers fire-and-forget
hooks only.
Long runs of one character class and heavy non-ASCII text can make the exact
tokenizer block the event loop. Such input now uses a linear estimate; ordinary
text keeps the exact count.
Brings the recut of #17920 up to release/v3.8.54 at 8943ca61, which added
RenderHour (#18103) and moved the provider count 385 -> 386 in the same
count-only files this PR bumps. For those 93 files the release side was kept
and the PR's own +1 provider / +1 hasFree was replayed on top (387 providers,
154 hasFree, 20 search providers). PROVIDER_REFERENCE.md and the four README
diagrams were regenerated. Protected files change in digits only.
Co-authored-by: Ilya Bogin <246701201+ilya-bogin-keenable@users.noreply.github.com>
dead-code flagged it on the new-code check: only the engine (codex executor
and chatCore service tier) calls scopeCodexServiceTierDefault, and both import
it from open-sse/config directly.
Brings the recut of #17920 up to release/v3.8.54 at 8e72dbf5. The base added
MegaBrain (#18129), which moved the provider count 384 -> 385 in the same
count-only files this PR bumps. For those 93 files the release side was kept
and the PR's own +1 provider / +1 hasFree was replayed on top (386 providers,
154 hasFree, 20 search providers). PROVIDER_REFERENCE.md and the four README
diagrams were regenerated. Protected files change in digits only.
Co-authored-by: Ilya Bogin <246701201+ilya-bogin-keenable@users.noreply.github.com>
The jev strategy added three open-sse -> src edges, failing the boundary
ratchet (head 777, base 774). Remove them without raising the ceiling:
- jevBlockChecker: derive JevResilienceSettings from the engine's own
isProviderInCooldown signature instead of importing the src type.
- jevRuntimeUnits: take the already-resolved resilienceSettings from combo
setup (combo.ts -> tryRuntimeUnitDispatch) instead of resolving them from
src again; same value, comboSetup resolves the same settings object.
- jevAsk: reach getProviderCredentials through autoStrategy.ts, which already
imports src/sse/services/auth (same seam pattern as #18467).
boundary-engine-seams.test.ts pins the seam and the src-free jev files.
The CI unit checkout is shallow and has no origin/main, so loadFullCiProfile's
git rev-parse failed three static-profile tests. The base-SHA resolver is now an
injectable parameter (default unchanged: git rev-parse origin/<ref>); the tests
pin a fixed SHA and additionally assert the declared ref (main) is the one pinned.
The Codex executor and the chatCore service-tier resolver imported
scopeCodexServiceTierDefault from src/lib/providers, adding two
open-sse -> src edges the boundary ratchet rejects. The pure leaf module
moves to open-sse/config/codexServiceTierModels.ts (tier type made generic
so it needs no src type import); src/lib/providers/codexServiceTierModels.ts
re-exports it for the dashboard and settings modules.
Split the per-hop fetch selection out of openRemoteMedia (complexity 16 -> under 15)
and drop shim re-exports no application code imports through the src path.
The custom JSON executor imported safeOutboundFetch from src/, adding an
open-sse -> src edge the boundary ratchet rejects. It now sends its single
request through dispatchGuarded() — the transport every other executor uses
for an operator-supplied base URL — wrapped in the engine's fetchWithTimeout:
string-level guard on every call (403), connect-time DNS-rebinding guard
(403), default fetch timeout (504), no retry, redirects never followed (502).
The dispatchPin re-export of getProviderOutboundGuard is no longer needed.
Adds a regression test pinning the no-redirect behavior.
Co-authored-by: lyccccy <g1337699300@gmail.com>
build-typecheck flagged TS2345: with strict:false zod infers every key of
promotionRunReceiptSchema as optional, so the parsed previous report did not
satisfy PromotionRunReceipt. The schema mirrors the interface field for field.
Migrations 234/235 are now taken on the tip (agent_sessions, usage_history_agent_session_id), so the
seen_models migration moves to 236 (next free) and the migration count goes 232 -> 233 (digits only).
Migrations 234/235 are now taken on the tip (agent_sessions, usage_history_agent_session_id), so the
custom JSON migration moves to 236 (next free) and the migration count goes 232 -> 233 (digits only).
Keep the release side for the count lines and re-apply this PR's +1
(Keenable Search) on top of ParalonCloud: 384 -> 385 providers,
153 -> 154 hasFree; regenerated PROVIDER_REFERENCE.md and README SVGs.
Extract buildFetchResult() and mapFetchError() so keenableFetch stays
within the complexity ratchet (cyclomatic and cognitive 16 -> <=15).
No behavior change; covered by tests/unit/keenable-web-provider.test.ts.
Co-authored-by: Ilya Bogin <ilya-bogin-keenable@users.noreply.github.com>
Resolve the provider-count conflicts by keeping the release side and
re-applying this PR's +1 (Keenable Search): 383 -> 384 providers,
153 -> 154 hasFree, regenerated PROVIDER_REFERENCE.md and README SVGs.
safeOutboundFetch and getProviderOutboundGuard live in src/, so importing them
from open-sse/services/usage/openaiCompatible.ts added two open-sse -> src edges
and the boundary ratchet failed (head 775 > ceiling 774). The engine already has
the same provider URL policy in executors/dispatchPin.ts: the host-name guard
(cloud-metadata always refused, LAN per operator setting) plus the connect-time
DNS-rebinding guard. Use it, keep redirects unfollowed (redirect: manual), and
pin that with a test.
Conflicts: AGENTS.md keeps the release migration count (230, measured on the
merged tree) plus this PR's approved Domain services line. docs/i18n mirrors
and .i18n-state.json take the release versions: per-PR mirror translation was
retired (ci.yml "i18n docs drift (PR — advisory)"); the post-merge batch
refreshes the ARCHITECTURE/CODEBASE_DOCUMENTATION mirrors.
Migration 233 is now taken on the tip by 233_api_key_self_service_settings.sql (#14771), so the custom JSON migration moves to 234 (next free) and the migration count in AGENTS.md, README.md, llm.txt and their i18n mirrors goes 230 -> 231 (digits only).
The release moved CodexFastTierTab to the shared Button and ui-kit Checkbox;
the partial @/shared/components mock now exports the real Button, as the
sibling codex-fast-tier-catalog test does. Assertions are unchanged.
CodeQL js/incomplete-sanitization flagged the RegExp built from the e-mail with
only dots escaped. A literal substring check asserts the same restored delta.
The release now lines sections up by hash when a document gains or loses
a section (#19186) and walks a model chain with a Google fallback per
chunk (#18422, #18461). Keep both: the count-only reuse and the
revalidation of cached sections run on the aligned recorded section, and
the validation feedback is replayed inside translateChunk for each model
of the chain. The retry test disables the Google fallback so it keeps
exercising the LLM retry path.
dashboard-kit-sweep allows no hard-coded Tailwind palette hue or dark: variant
in the dashboard; the jev admission summary and privacy note used indigo/amber
with dark: overrides. They now use the kit primary/warning tokens.
The release tip already ships #14498 itself: getExecutor() refuses chat for a
decisions-only provider with a 400 on every request, covered by
tests/unit/typesafe-decisions-provider-14498.test.ts. The ported opt-in copy
(SYSTEMONE_CHAT_GUARD_ENABLED, default off) would only be a dashboard toggle
that changes nothing, so the merge keeps the release guard and this removes the
flag, its test and its changelog fragment. Flag count 124 -> 123; the
FEATURE_FLAGS.md System One rows also lose a stray duplicated cell.
The release already carries this branch's host-state, Kimi/Codex clock,
conversation-tracker, cursor, MITM and redaction-probe fixture repairs
(#19323), and fixed the log-export timing tests (#18440, #18960), the
Perplexity delayed-hook model (#18232) and the providers-page pin
differently; take the release versions of those files. Keep what the
release still lacks: offline catalog discovery for the twelve catalog
fixtures, the post-keepalive error-frame sequencing, the Kiro watchdog
test clock, and locale-independent ci-discriminate signature ordering.
Renumber the seen_models migration 227 -> 233 (the release took 227-232) and sync the
migration count to 230 in AGENTS.md / llm.txt / README + i18n mirrors.
- Model the new lint-job `check:build-typecheck` step in the reviewed static
profile (the profile coverage alarm rejected it as unmodeled after the sync).
- A declared hard gate upgrades the curated bucket but never downgrades a
curated hard result, so incomplete workflow-audit evidence (#17412) stays
blocking under any declared policy.
- The workflow-evidence fixture now supplies the static profile, quality.yml
and a complete ESLint record that --full-ci and the lint measurement require;
it declares the workflow audit under the ratchet policy so the evidence
boundary is what it exercises. Assertions are unchanged.
vi.fn(async () => {}) infers a zero-arg mock, so mock.calls[0][0] is a
TS2493 tuple-out-of-range error that check:dashboard-typecheck flags as a
new regression (3 sites). Give the mock the modal's real onSave signature.
Carry the release's remoteImageFetch changes (proxy-aware pinning, upstream
media helpers) into open-sse/utils/remoteMediaFetch.ts, keep the application
path as a full re-export, and point every engine importer of the downloader
at the engine module. URL transcription keeps the release's injected fetcher.
Boundary ratchet: 756 edges (ceiling 774); cycles 14 (ceiling 14).
The base kept error-only SSE frames as invalid_sse_payload (#18272 made it a
sanctioned public identifier), so the parse-level fixture returns to the base
contract and the provider-leg test asserts the public code the body carries.
Renumber the custom JSON migration 228 -> 233 (the release took 228-232) and sync the
migration count to 230 in AGENTS.md / llm.txt / README + i18n mirrors.
buildCloudflareTranscriptionUrl trimmed trailing slashes with /\/+$/, which
backtracks quadratically on a long run of slashes followed by a non-slash
(CodeQL js/polynomial-redos #1228). Use the shared stripTrailingSlashes()
helper from open-sse/utils/urlSanitize.ts, which is the same trim as a single
backward scan. Output is unchanged for every input.
Tests pin the URL shape (0, 1 and 3 trailing slashes, encoded id) and a
50k-slash adversarial input that must finish under 500 ms (old regex: ~11.7 s).
The README's first image showed the Classic (lime, dark) look. New capture of
the same Analytics page in Editions light, the dashboard's default palette
and the brand's canonical look: a local run of this branch on a temporary
data dir with synthetic usage rows only, 1640x893 at 2x, quantized to 128
colors (132,104 -> 118,680 bytes).
After the README diagrams moved to Switzer outlines (#18767) and the Editions
palette (#18901, #18957), gen-budget-card-svg.mjs no longer ran: readme-fonts.mjs
only embeds the mono subset now, and the card asked for the old display face.
The generator now ends with outlineSvg() like the README diagrams: the Switzer
roles become vector outlines, the code roles stay text on the embedded IBM Plex
Mono subset, and the palette is the theme module's Editions tokens (light
#f3f1e9 / #faf9f4 / #20211c, accent #e5ac82; dark #11120f / #191a16 /
#f2f0e8). The stat figures use the kit's num role (500, -0.02em) at 46px. No
literal color in the generator; every drawn string is unchanged and the figures
still come from computeFreeModelTotals().
The test asserts the new shape: one @font-face (CI Mono), no CI Serif / CI Sans
/ Switzer face, outlined glyphs, and the Editions light and dark values with no
Classic value left.
Editions became the dashboard's default palette (#18901), so the eight
header shields move from the Classic lime-on-ink to Editions copper on ink:
color=e5ac82 (--ci-color-accent) and labelColor=20211c (--ci-color-heading),
from the light block of packages/ui-kit/src/ci-editions.css. shields.io
draws the message text dark on the copper and white on the ink.
apply-readme-badge-colors.mjs carries the same values and was run over
README.md and the 66 mirrors: 528 lines, URL query strings only. The PR-scoped
i18n drift gate reports 0 drift introduced (README.md and its 66 mirrors are
already drifted on release/v3.8.54).
open-sse reads SYSTEMONE_CHAT_GUARD_ENABLED and COMBO_JEV_STRATEGY_ENABLED with
isRegisteredFeatureFlagEnabled (DB override > env > default, fails closed) instead of
importing src/shared/utils/featureFlags, so the port stays inside the open-sse -> src
boundary ceiling after the latest release merge.
Co-authored-by: Sean P. Ford <sean@seanford.com>
Co-authored-by: Miguel Enes <1568086+miguelenes@users.noreply.github.com>
The ported #15279 success hook bound the selected-connection header account and the
combo namespace for all strategies. Only jev needs that (it pins the account and the
model Jev chose); every other strategy now records the declared target connection
exactly as before.
Co-authored-by: Miguel Enes <1568086+miguelenes@users.noreply.github.com>
- the System One / Jev flag definitions move to featureFlagDefinitionsSystemOne.ts
(featureFlagDefinitions.ts is at its cap); check-fabricated-docs reads every
featureFlagDefinitions*.ts module.
- the ollama-local base URL is resolved on the route side
(systemOneOllamaUrl.ts) into target.upstreamUrl, so open-sse gains no import
edge into src for it; the Jev modules share one ResilienceSettings edge.
- tryRuntimeUnitDispatch delegates the jev/default unit ordering to a helper.
- the lease inventory classifies the two read-only typesafe credential lookups.
Co-authored-by: PixmaNTS <maxime@maxime-pointet.fr>
Co-authored-by: Miguel Enes <1568086+miguelenes@users.noreply.github.com>
Builds on #18017, whose vault was never scoped in production code. A new
PII_REVERSIBLE_VAULT_ENABLED flag (default false, Hard Rule 20 guard) works on
top of PII_REDACTION_ENABLED; the gate reads the DB override like every flag.
- One vault per client request, opened in handleChat next to the turn
ownership scope and passed to the pre-call pass as GuardrailContext.tokenVault.
Only the pii-masker mints, for built-in, validated (GDPR/POPIA) and custom
rules. Random 8-letter nonce per request, no singleton, no LRU, no timers;
hard limits fall back to the irreversible placeholder.
- Tokens are restored once, on the 2xx response leaving handleChat: per field
on the parsed SSE (a token split across events resolves, tool arguments are
JSON-escaped, snapshots are not duplicated, only a token prefix is held back)
or per field on JSON with a fresh Content-Length. Nothing in chatCore
detokenizes, so fusion panels and the judge only see tokens. Error bodies
keep the tokens.
- Input failure writes the placeholder (fail-closed); output failure leaves the
token literal with a count-only warning.
- When tokens were minted, memory extraction, the idempotency save and both
semantic-cache writes are skipped.
- With the gate closed, or no token minted, handleChat returns the very same
Response object (byte-identical regression test).
Co-authored-by: Dmitry Kuznetsov <ardemb22@gmail.com>
Complements the System One design from #17994 with pieces from open PRs, each
behind a default-off feature flag so nothing changes for current users:
- ollama-local/<model> on POST /v1/systemone, served by the ollama-local
connection's base URL with Ollama's own body limits checked before any
upstream call (from #14667; SYSTEMONE_OLLAMA_LOCAL_BACKEND_ENABLED).
- getExecutor refuses chat on the decisions-only typesafe provider instead of
letting the default executor post the TypeSafe key to the OpenAI fallback
(from #14498; SYSTEMONE_CHAT_GUARD_ENABLED).
- the jev combo strategy: one TypeSafe System One choice call admits the
targets, failover keeps the operator's order (from #15279). The TypeSafe
call needs COMBO_JEV_STRATEGY_ENABLED; a stored key alone never sends
traffic, and with the flag off a jev combo keeps its preference order.
Strategy count 20 -> 21 where the docs-counts gate and the
routing-strategy-docs-sync test pin it (digits and the jev name only).
Co-authored-by: PixmaNTS <maxime@maxime-pointet.fr>
Co-authored-by: Sean P. Ford <sean@seanford.com>
Co-authored-by: Miguel Enes <1568086+miguelenes@users.noreply.github.com>
Extracted from the workflow-hardening commits of #18348 ("pin workflow
dependencies and remove unsafe release cache reuse") and its main backports in
#18209, #18210 and #18345 ("backport complete gate execution and workflow
hardening to main").
- Every remaining `uses: owner/action@<tag>` in .github/workflows is pinned to
the commit SHA the tag resolves to today (resolved with the GitHub API on
2026-11-08), keeping the tag as a trailing comment so the github-actions
Dependabot ecosystem can keep bumping them.
- base-ci-repair.yml and wiki-sync.yml check out with
persist-credentials: false. Neither job pushes with the checkout token;
wiki-sync pushes from its own token-authenticated wiki clone.
- nightly-compat.yml drops the workflow-level issues: write; the report job
already declares its own issues: write.
zizmor 1.25.2 via check-workflows.mjs: 216 -> 13 findings. actionlint output
is unchanged (the same 8 pre-existing shellcheck notes).
The release cache-reuse removal and the .zizmor.yml rewrite were left out:
they reverse accepted-risk entries and need an explicit decision.
Ports the Cloudflare channel of #16676 onto the System One registry from #17994:
cloudflare-ai/<jev|clef|clef-flash> (alias cf/) runs on Workers AI through the
existing cloudflare-ai connection. Off by default via
SYSTEMONE_CLOUDFLARE_BACKEND_ENABLED: those ids are refused with a 400 and no
upstream call.
Co-authored-by: Qiancheng Yan <xiaoyaner0201@users.noreply.github.com>
getOpenAiCompatibleUsage now goes through safeOutboundFetch, which checks the
host with a DNS lookup before fetch() runs. The #13616 abort-signal test read
the signal after a single setImmediate, so it failed whenever the lookup took
longer (reproduced deterministically with a 50 ms delayed dns.promises.lookup).
The test now waits for the fetch call itself; the assertion is unchanged.
isCompatibleQuotaProvider reuses isOpenAICompatibleProvider and
isAnthropicCompatibleProvider instead of repeating the prefix checks.
CustomJsonFields was 138 lines, over the 80-line max-lines-per-function cap the complexity ratchet enforces on new code. The extra-field row, the simple-fields editor and the full-JSON editor are now their own components; markup, test ids and behavior are unchanged.
Keep the release side in usage.ts and providerQuotaVisibility.ts: #17136
already routes anthropic-compatible-* to the configurable quota fetcher and
gates visibility with hasCompatibleQuotaEndpoint.
Brings the stacked engine PR's fixes (migration renumbered to 228, no-replay latch fix, regenerated skills endpoints) under the dashboard form. The 67 locale conflicts keep every key from both sides: the release keys carried by #18353 plus this PR's 30 providers.customJson* keys.
Cursor renewal: the fake agent publishes its PID through a rename, so the
cleanup kill can never read an empty file (Number("") is 0, a signal to the
test runner's own process group), and cleanup ticks the SIGKILL follow-up
separately because a timer armed during tick() starts after that tick ends.
No-auth cooldown: hold Date from before the lock exists, with setTimeout real
until the lock is in place, so a slow failing request cannot use up the lock.
Codex handoff: wait for the completion on a bounded real-time loop while the
grace clock stays frozen; with SSE comments on it follows a pricing lookup.
Log export: the parent read probe also counts fs.promises.readFile, the path
the child resolver uses, with a positive control.
The latch wrapped every combo's abort signal in AbortSignal.any, so the
fallback wait listened on a derived signal and the #18569 cancellation test
failed for traffic that has no custom JSON node at all. The strategy now keeps
the caller's signal. A latched failure reaches it as the 499 it already treats
as a stop, which also skips the fallback wait and the failure bookkeeping, and
in-flight targets are cancelled through their own modelAbortSignal.
Also on this branch:
- migration moves to 228, 227 was taken by quota_recovery_due_cover (#19108);
the SQL file count goes from 224 to 225 in AGENTS.md, README.md, llm.txt and
their mirrors, digits only
- regenerate the omni-providers endpoint reference from docs/openapi.yaml
- reword a comment gitleaks read as a generic API key
Use the canonical zh-CN and zh-TW term for "provider" in the two new
strings that carried the retired renderings, and split the 153-line
NewModelsButton into a hook and two child components so it fits the
80-line function limit. Behavior is unchanged; two new UI tests pin the
error branch over loaded groups and over an empty inbox.
Co-authored-by: ErfanBagheri404 <mrenmityerf@gmail.com>
A custom JSON node whose endpoint sits on a ModelScope host matched the
host markers in isModelScopeProvider, so a retryable 429 re-sent the
business call up to three times. The node's apiType now wins over the host.
Resolve the hang-escalation conflict with #18960: keep the deterministic
mock-clock test, keep the SIGTERM handler at createClient, and use a single
handler so the term-ignored marker is written however early the SIGTERM lands.
The tip took 226 for request_cost_ledger_read_indexes, so the provider node
migration moves to the next free slot. The SQL file count goes from 223 to 224
in AGENTS.md, README.md, llm.txt and their mirrors (digits only).
The tip took slot 226 for request_cost_ledger_read_indexes, so seen_models moves
to the next free number. The count surfaces go from 223 to 224, digits only.
Keeps the logical-clock hang test and read-count hydration test from this branch
over the wall-clock bounds of #18440, and keeps #18440's early SIGTERM handler in
the hang fixture.
Resolves the stack's conflicts against the release tip:
- src/sse/handlers/chat.ts: keep buildModalityBridgeResponseHeaders and the
release's extracted deriveVideoBridgeLog import.
- docs/openapi.yaml: keep the release's /api/v1/systemone block and the stack's
detailed drilldown contract, placed in the release's alphabetical slot so
generated SKILL.md output stays byte-identical to the release.
- skills/omni-inference: SKILL.md equals the release version; references
regenerated from the merged OpenAPI document.
Keep the release's chat/videoBridgeLog.ts extraction with the drilldown response headers, and keep /api/v1/systemone next to the documented drilldown path. The path stays where the release has it, so skills/omni-inference/SKILL.md needs no change.
The release's dashboard-kit-sweep guard rejects the raw buttons, Material Symbols spans, animate-spin and palette hues the port brought. Adds a UI test for the badge, the provider grouping and both mark-as-read paths.
With FLUSH_EMPTY_RETRY_ENABLED on, an empty streamed business reply was sent again up to the retry budget (five upstream calls in the new test), which breaks the no-replay guarantee of custom JSON nodes.
Keep both sides in src/lib/providers/validation.ts and stryker.conf.json, and renumber the custom JSON node migration to 226 because 225 is now 225_token_ledger_balance_indexes.sql.
The old capture dates from May 2026, before the kit migration. This one is the Analytics
overview in dark, taken from a local instance on a throwaway data dir with synthetic demo
usage, so nothing real appears in it. Same path, filename and alt text.
The generator now draws through readme-diagram-theme.mjs and readme-fonts.mjs: palette in theme
classes and CSS variables, both color schemes, kit fonts embedded as subset data URIs. Figures
still come from computeFreeModelTotals() and every drawn string is the same as before.
The test keeps its stale compare and adds checks for inline fonts, no external references,
figures as <text> and no literal color outside the stylesheet.
Lime on ink (d8ff00 on 040d10) for the eight shields.io badges of the header group. The star
counter moves from style=social, which ignores both colors, to style=flat with its logo and
label spelled out, so it keeps the same text and mark.
scripts/docs/apply-readme-badge-colors.mjs applies the same URL change and is idempotent; it
is meant to be run over docs/i18n/*/README.md after the translation wave lands.
release/v3.8.53 shipped 217_quota_recovery_tickets.sql (#14982) after the previous renumber, so 217_seen_models.sql collided again. README Database row now reflects the 215 SQL migrations on the merged tree. Migration body unchanged.
Co-authored-by: ErfanBagheri404 <mrenmityerf@gmail.com>
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
Bring the updated #16074 head 688dbc92b3, which already carries release/v3.8.53, into this stacked branch. Resolve ModalityBridgeVideoTab.tsx on the release's UI-kit structure: keep the video-promotion-readiness block and the promotionStatus helper, and use the kit Collapsible for the advanced settings instead of the raw <details>.
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
release/v3.8.53 shipped 215_team_cost_centers.sql and 216_team_cost_shapes.sql, so this PR's 215_seen_models.sql collided. The migration body is unchanged (idempotent CREATE ... IF NOT EXISTS).
Co-authored-by: ErfanBagheri404 <mrenmityerf@gmail.com>
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
README Database row resolved to 214 migrations (213 on the release + this PR's seen_models). docs/i18n mirrors take the release side; they are refreshed after merge.
Co-authored-by: ErfanBagheri404 <mrenmityerf@gmail.com>
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
Resolve ModalityBridgeVideoTab.tsx by keeping the release's ui-kit Select (modality-bridge-video-analysis-mode, KEA-7886) and adding the two drill-down consent Toggles from this PR. The raw <select> is not restored.
Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
The seen_models migration was renumbered 206 -> 215 on the merge with
release/v3.8.53 (206 is taken by 206_codex_wakeup_tasks), which makes the
shipped SQL file count 212. AGENTS.md and llm.txt carry the same count but
are protected agent-instruction surfaces and are left for the operator.
Adds the "Custom JSON API" API type to the OpenAI-compatible Add and Edit
provider modals (the engine, storage and API landed in #18353):
- New CustomJsonFields component: HTTP method, auth type (bearer / API key in
a named header / none), auth header name, request template editor with two
modes (simple fields: model + messages always sent, optional text or JSON
rows; full JSON for other schemas) and the response path.
- customJsonForm.ts converts between the stored config and the form and
validates it client-side with the same Zod schema the server uses
(customJsonConfigSchema); extra rows are own properties, so a name such as
__proto__ is rejected instead of being dropped silently. A non-standard
stored template opens in JSON mode and is never forced back into fields.
- Choosing the type clears the OpenAI default base URL (custom JSON nodes take
the complete endpoint URL) and hides chat/models paths; the check button
becomes "Send test request" (one real request through
/api/provider-nodes/validate), usable without a key when auth is none.
- 30 new providers.* i18n keys, translated by hand in all 66 locales.
Co-authored-by: lyccccy <g1337699300@gmail.com>
Inspired-by: https://github.com/decolua/9router/pull/4929
Add `cloudflare-ai` (alias `cf`) to the transcription registry with the
`@cf/deepgram/nova-3` model. The handler POSTs the raw audio to
/accounts/{accountId}/ai/run/{model}, taking the account id from the
connection (URL-encoded) and returning 400 before any upstream call when it
is missing. `punctuate=true` is always sent, `diarize=true` only on request
(same spellings as the Deepgram/Soniox paths) and `language` only when set.
Workers AI returns no utterances, so verbose_json builds one segment per
speaker run from the word list and adds `words`, `num_speakers` and the
neuron usage. Diarization implies the verbose body, as on native Deepgram.
A `success:false` envelope delivered with HTTP 200 becomes a 502 that
carries only the vendor error code; non-2xx statuses go through the shared
sanitized upstreamErrorResponse.
Co-authored-by: LeandroTechify <leandro.techify@gmail.com>
Inspired-by: https://github.com/decolua/9router/pull/5140
The configurable quota fetcher (#13616) only covered openai-compatible-*
connections and could only be configured by hand-editing the connection's
providerSpecificData.quotaEndpoint.
- anthropic-compatible-* (CC-compatible included) is now dispatched to the
same fetcher and accepted by the Provider Limits visibility gate.
- The node edit modal gets a "Quota check" toggle and a quota path (default
/credits). Saving writes a standard-credits quotaEndpoint preset
({ credits, total?, used? }) to the node's connections, or removes it.
Only the preset is ever replaced or removed; a hand-written endpoint is
left untouched. Anthropic-compatible nodes authenticate with x-api-key.
- A key added to a node whose keys already use the preset inherits it.
- quotaEndpoint and the quota path get Zod schemas; the path must stay on
the node's own host (single leading "/", no scheme, no "//").
- The quota call goes through safeOutboundFetch with the provider outbound
guard (cloud metadata always blocked, no redirects).
- New strings translated in all locales.
Co-authored-by: MWGE22629 <207309548+MWGE22629@users.noreply.github.com>
Inspired-by: https://github.com/decolua/9router/pull/4999
Adds an OpenAI-compatible node with apiType "custom-json" that talks to any JSON
business endpoint: the full endpoint URL, POST/PUT/PATCH, bearer / named api-key
header / no auth, a JSON request template filled from {{prompt}}, {{messages}},
{{model}}, {{stream}} and {{request.<path>}} placeholders (substitution only, never
evaluated), and a response path whose value is returned as an OpenAI chat
completion (or a two-chunk SSE stream) through the regular translators.
- Config validated with Zod (customJsonConfigSchema): 64 KB / depth 32 template
caps, __proto__/prototype/constructor blocked in keys and paths, bounded
placeholder/path patterns, auth header denylist; endpoint must be http(s)
without credentials or fragment.
- Executor (open-sse/executors/customJson.ts) sends exactly one request through
safeOutboundFetch with the provider outbound URL guard on every call, retry:false
and no redirects; operator custom headers go through the shared sanitizer
(applyCustomHeaders moved to executors/default/customHeaders.ts); the auth
header is redacted in the logged headers; errors go through errorResponse /
buildErrorBody.
- Never replayed: responses are marked in-process (noReplayResponse) and
chat.ts returns them before account cooldown/fallback, while the combo
noReplayLatch makes the first marked target response final.
- Migration 215 adds provider_nodes.custom_json_config_json; node create/update
routes persist it and propagate it to every connection; connection creation,
bulk/import and the runtime self-heal hydrate providerSpecificData.customJson.
- Connection tests and health checks validate the config only (reported as
unverifiable); POST /api/provider-nodes/validate sends one explicit test
request; /models discovery is skipped for these nodes.
- Docs: docs/guides/CUSTOM_JSON_API.md. Dashboard form is a follow-up.
Co-authored-by: lyccccy <g1337699300@gmail.com>
Inspired-by: https://github.com/decolua/9router/pull/4929
Every successful model sync now records the provider's listing in a new
seen_models table (migration 206, src/lib/db/seenModels.ts). The first sync
of a provider seeds its baseline as already read, so existing installs and
freshly connected providers never flood the inbox; models that show up in
later syncs stay unread until acknowledged. Rows are never deleted, so a
model that drops out of a listing and comes back is not flagged again.
- GET /api/models/new returns the unread models grouped by provider
(read from the table only, no catalog rebuild per request).
- POST /api/models/new/acknowledge marks a selection, or everything, read
(Zod-validated body; errors sanitized via createErrorResponse).
- The Providers toolbar gets a "New models" button with an unread badge and
a modal grouped by provider, with Free tags from the shared free-model
knowledge and per-provider / mark-all-read actions.
- Recording is best-effort and never fails a sync; it runs for the regular
discovery path and the Volcano Ark console path, so the 6h auto-sync
scheduler fills the inbox too.
- New UI strings translated in all 66 locales.
Co-authored-by: ErfanBagheri404 <mrenmityerf@gmail.com>
Inspired-by: https://github.com/decolua/9router/pull/3604
echo "\`$REFRESH_BRANCH\` is pushed with ${COUNT} refreshed file(s), but no PR was opened:"
echo "neither \`DERIVED_REFRESH_PR_TOKEN\` nor \`I18N_REFRESH_TOKEN\` is set. Open it from that branch against \`$BASE\`."
} >> "$GITHUB_STEP_SUMMARY"
exit 0
fi
{
if [ -n "${BASE_RED_ISSUE:-}" ]; then printf '⚠️ base-red inherited: #%s\n\n' "$BASE_RED_ISSUE"; fi
echo "## Summary"
echo
echo "Nightly refresh of the derived numbers on \`$BASE\`: \`npm run release:refresh-derived -- --profile=nightly\` recomputed the provider, migration and MCP-tool counts, the version claims, the README SVG numbers and the facts snapshot from the live code (${RUN_URL})."
echo
echo "Feature PRs no longer write these values; this PR (and the release itself) does. The branch \`$REFRESH_BRANCH\` is rebuilt from \`$BASE\` on every run, so a later run replaces this commit."
echo
echo "## Files (${COUNT})"
echo
# shellcheck disable=SC2016 # the backticks are Markdown code spans, not substitutions
printf '%s\n' "$CHANGED" | head -200 | sed 's/^/- `/; s/$/`/'
echo
echo "## Before merge"
echo
echo "- [ ] CI is green, or every red check is inherited from the base."
echo "- [ ] The diff only touches derived numbers (no prose rewrites)."
# Agent-instruction surfaces are never merged without the owner's explicit approval
# (AGENTS.md → Review focus), even when the diff is digits only.
if printf '%s\n' "$CHANGED" | grep -qE '(^|/)(AGENTS|CLAUDE|GEMINI)\.md$|(^|/)llm\.txt$|^skills/.*/SKILL\.md$'; then
echo "- [ ] **Agent-instruction surface touched** (AGENTS.md / llm.txt / SKILL.md): needs the owner's explicit approval before merge."
Counts (providers, migrations, MCP tools and scopes, routing strategies, scoring factors, mode packs) are derived values: read them with `npm run facts` (one value: `npm run facts -- --key=providers`), never from prose. Feature PRs do not write them; `npm run release:refresh-derived` rewrites the docs at release.
API routes follow a consistent pattern: `Route → CORS preflight → Zod body validation → Optional auth (extractApiKey/isValidApiKey) → API key policy enforcement → Handler delegation (open-sse)`. No global Next.js middleware — interception is route-specific.
**Combo routing** (`open-sse/services/combo.ts`): 21 public strategies (priority, weighted, fill-first, round-robin, p2c, random, least-used, cost-optimized, reset-aware, reset-window, expiry-first, headroom, quota-weighted, strict-random, auto, lkgp, context-optimized, cache-optimized, context-relay, fusion, pipeline). Each target calls `handleSingleModel()` (wraps `handleChatCore()` with per-target error handling + circuit breaker checks); the `fusion` strategy instead fans out to a panel of models in parallel and a judge model synthesizes one final answer (`open-sse/services/fusion.ts`). 16-factor Auto-Comboscoring + full strategy table: `docs/routing/AUTO-COMBO.md`; the 3 resilience layers: `docs/architecture/RESILIENCE_GUIDE.md`.
**Combo routing** (`open-sse/services/combo.ts`): the public strategies are `ROUTING_STRATEGY_VALUES` in `src/shared/constants/routingStrategies.ts` (`quota-share` is internal). Each target calls `handleSingleModel()` (wraps `handleChatCore()` with per-target error handling + circuit breaker checks); the `fusion` strategy instead fans out to a panel of models in parallel and a judge model synthesizes one final answer (`open-sse/services/fusion.ts`). Auto-Combo scoring (`DEFAULT_WEIGHTS` in `open-sse/services/autoCombo/scoring.ts`) + full strategy table: `docs/routing/AUTO-COMBO.md`; the 3 resilience layers: `docs/architecture/RESILIENCE_GUIDE.md`.
---
@@ -176,6 +177,9 @@ Documentation must describe verified behavior, not plausible behavior.
`path/to/file.ts:line` to an invented signature.
4. Run `npm run check:docs-all` for edits under `docs/`; it includes the fabricated-docs
validation.
5. Edit only the English source. Never commit `docs/i18n/**` mirrors, `llm.txt` mirrors or
`.i18n-state.json` in a feature PR: the translation wave (`/i18n-waves`, `docs/i18n-*`
branches) and the release rewrite them (`docs/guides/I18N.md`).
---
@@ -200,7 +204,7 @@ Full step-by-step recipes: [`docs/architecture/MODIFICATION_SCENARIOS.md`](docs/
For any non-trivial change, read the matching deep-dive first:
`test:vitest:ui` has been blocking since PR #7127.
- **Velocity phase (2026-08-30 → v4.0)**: every numeric baseline is loosened by 20% and `--require-tighten` is advisory (`quality-baseline.json` → `_policy`); the nightly `baseline-headroom` job tracks how much of the budget is left in the issue "📈 Baseline headroom". See `docs/architecture/QUALITY_GATES.md` → "Velocity phase".
@@ -384,7 +392,7 @@ is a short form, its complete binding text, rationale and incident history are i
6. Never silently swallow errors in SSE streams
7. Always validate inputs with Zod schemas
8. Always include tests when changing production code
9. Coverage must not regress below the baseline frozen in `quality-baseline.json` (ratchet); absolute floor is 60% (statements/lines/functions/branches). Update the baseline via`npm run quality:ratchet -- --update`only when coverage genuinely improves. See `docs/architecture/QUALITY_GATES.md`.
9. Coverage must not regress below the baseline frozen in `quality-baseline.json` (ratchet); absolute floor is 60% (statements/lines/functions/branches). The baseline is tightened with`npm run quality:ratchet -- --update`at release, never inside a feature PR. See `docs/architecture/QUALITY_GATES.md`.
10. Never bypass Husky hooks (`--no-verify`, `--no-gpg-sign`) without explicit operator approval.
11. Never embed public upstream OAuth client_id/secret or Firebase Web keys as string literals — always go through `resolvePublicCred()` (`open-sse/utils/publicCreds.ts`). See `docs/security/PUBLIC_CREDS.md`.
12. Never return raw `err.stack` / `err.message` in HTTP / SSE / executor responses — always route through `buildErrorBody()` or `sanitizeErrorMessage()` (`open-sse/utils/error.ts`). See `docs/security/ERROR_SANITIZATION.md`.
**👋 Follow the maintainer — get new providers, releases & tips first:**
[](https://www.linkedin.com/in/diegosouzapw/)
[](https://github.com/diegosouzapw)
[](https://www.linkedin.com/in/diegosouzapw/)
[](https://github.com/diegosouzapw)
<img src="./docs/diagrams/promise-pillars.svg" width="100%" alt="The Promise — One endpoint and 393 providers. Automatic fallback keeps routing while another healthy target is available. Six pillars: resilient fallback across 393 providers · up to 95% token savings on eligible workloads · $0 to start with 150+ free tiers and 51 recurring/keyless free-forever providers · 39 CLI/agent integrations through one config · OpenAI, Claude, Gemini and Responses API compatibility at /v1 · production controls including circuit breakers, TLS stealth, MCP 110 tools, A2A, memory, guardrails, evals and 56,000+ static test declarations across 7,800+ tracked test files."/>
<img src="./docs/diagrams/promise-pillars.svg" width="100%" alt="The Promise — One endpoint and 394 providers. Automatic fallback keeps routing while another healthy target is available. Six pillars: resilient fallback across 394 providers · up to 95% token savings on eligible workloads · $0 to start with 150+ free tiers and 51 recurring/keyless free-forever providers · 39 CLI/agent integrations through one config · OpenAI, Claude, Gemini and Responses API compatibility at /v1 · production controls including circuit breakers, TLS stealth, MCP 110 tools, A2A, memory, guardrails, evals and 56,000+ static test declarations across 7,800+ tracked test files."/>
<img src="./docs/diagrams/tier-cascade.svg" width="100%" alt="OmniRoute request flow: your IDE or CLI (Claude Code, Cursor, Cline…) calls one local endpoint (http://localhost:20128/v1); the OmniRoute Smart Router (RTK + Caveman compression, 21 routing strategies, circuit breakers, TLS stealth, MCP, A2A, guardrails) can fall back across 4 provider tiers while an eligible healthy target remains — Tier 1 Subscription, Tier 2 API Key, Tier 3 Cheap and Tier 4 Free."/>
<img src="./docs/diagrams/tier-cascade.svg" width="100%" alt="OmniRoute request flow: your IDE or CLI (Claude Code, Cursor, Cline…) calls one local endpoint (http://localhost:20128/v1); the OmniRoute Smart Router (RTK + Caveman compression, 22 routing strategies, circuit breakers, TLS stealth, MCP, A2A, guardrails) can fall back across 4 provider tiers while an eligible healthy target remains — Tier 1 Subscription, Tier 2 API Key, Tier 3 Cheap and Tier 4 Free."/>
<img src="./docs/diagrams/strategies-grid.svg" width="100%" alt="Animated examples for 18 of the 21 combo routing strategies — one tile per strategy: priority, fill-first, weighted, round-robin, p2c, least-used, random, strict-random, cost-optimized, headroom, reset-window, reset-aware, context-relay, context-optimized, lkgp, auto, fusion, pipeline. cache-optimized, quota-weighted and expiry-first are not animated; the table below describes all 21."/>
<img src="./docs/diagrams/strategies-grid.svg" width="100%" alt="Animated examples for 18 of the 22 combo routing strategies — one tile per strategy: priority, fill-first, weighted, round-robin, p2c, least-used, random, strict-random, cost-optimized, headroom, reset-window, reset-aware, context-relay, context-optimized, lkgp, auto, fusion, pipeline. cache-optimized, quota-weighted, expiry-first and jev are not animated; the table below describes all 22."/>
> A **combo** is a chain of models OmniRoute routes across **automatically**. If quota runs out, a provider fails, or costs spike, the combo can move to the next eligible healthy model. 🛡️
@@ -374,9 +374,9 @@ No combo to create. Set your model to `auto` (or a variant) and OmniRoute builds
##
### 🔀 Or build your own — 21 routing strategies
### 🔀 Or build your own — 22 routing strategies
All **21** strategies — mix & match per combo step:
All **22** strategies — mix & match per combo step:
<table>
<tr>
@@ -489,6 +489,11 @@ All **21** strategies — mix & match per combo step:
<td nowrap><code>expiry-first</code></td>
<td>Spend the account whose quota would expire unused first — highest leftover with the nearest reset wins ⏳</td>
</tr>
<tr>
<td align="center">22</td>
<td nowrap><code>jev</code></td>
<td>Your ranked list; TypeSafe Jev picks which entries run per request, falling back to your order (opt-in flag) ⚖️</td>
</tr>
</table>
<sub>The Auto-Combo engine scores every candidate on **16 factors** (health, quota, cost, latency, task fit, quality, session availability…) — see [`docs/routing/AUTO-COMBO.md`](docs/routing/AUTO-COMBO.md).</sub>
@@ -509,7 +514,7 @@ All **21** strategies — mix & match per combo step:
</div>
<img src="./docs/diagrams/comparison-table.svg" width="100%" alt="What sets OmniRoute apart — a dated feature snapshot vs 9router, OpenRouter, CLIProxyAPI and LiteLLM across 13 capabilities. OmniRoute: 393 providers, 150+ free tiers built in, 21 routing strategies, 12-engine token compression, built-in MCP server with 110 tools, A2A agent protocol, persistent memory, guardrails, cloud agents, TLS fingerprint stealth, Desktop/Termux/PWA and 67 i18n UI locales. OmniRoute is MIT-licensed and self-hostable. Competitor capabilities and counts may change; see the linked methodology."/>
<img src="./docs/diagrams/comparison-table.svg" width="100%" alt="What sets OmniRoute apart — a dated feature snapshot vs 9router, OpenRouter, CLIProxyAPI and LiteLLM across 13 capabilities. OmniRoute: 394 providers, 150+ free tiers built in, 22 routing strategies, 12-engine token compression, built-in MCP server with 110 tools, A2A agent protocol, persistent memory, guardrails, cloud agents, TLS fingerprint stealth, Desktop/Termux/PWA and 67 i18n UI locales. OmniRoute is MIT-licensed and self-hostable. Competitor capabilities and counts may change; see the linked methodology."/>
<sub>📊 Full methodology & per-feature detail vs 9router, OpenRouter, CLIProxyAPI & LiteLLM → [`docs/comparison/OMNIROUTE_VS_ALTERNATIVES.md`](docs/comparison/OMNIROUTE_VS_ALTERNATIVES.md)</sub>
@@ -613,7 +618,7 @@ the current catalog at **[radar.omniroute.online/planos](https://radar.omniroute
- **🖼️ New endpoints** — `/v1/ocr` (Mistral OCR) and `/v1/audio/translations` (Whisper-style) round out the media surface. → [API Reference](docs/reference/API_REFERENCE.md)
- **🎨 Image / video / audio generation** — one API for media: xAI Grok Imagine & Novita AI video, ComfyUI, Magnific, Adobe Firefly, Segmind, and speech providers such as ElevenLabs. → [API Reference](docs/reference/API_REFERENCE.md)
- **🤝 More providers & agents** — cloud agents (Codex Cloud, Cursor, Devin, Jules), Grok Build (xAI) with browser + OAuth login, Ollama first-class card, Claude Opus 5 & Sonnet 5, Kimi official partnership (Code/Web/Moonshot), Zed, Requesty, SenseNova, Yuanbao, Agnes AI… and a refreshed **393-provider catalog**. → [Providers](docs/reference/PROVIDER_REFERENCE.md)
- **🤝 More providers & agents** — cloud agents (Codex Cloud, Cursor, Devin, Jules), Grok Build (xAI) with browser + OAuth login, Ollama first-class card, Claude Opus 5 & Sonnet 5, Kimi official partnership (Code/Web/Moonshot), Zed, Requesty, SenseNova, Yuanbao, Agnes AI… and a refreshed **394-provider catalog**. → [Providers](docs/reference/PROVIDER_REFERENCE.md)
- **📡 Routing transparency** — every response carries an `X-OmniRoute-Decision` header naming the strategy/provider/latency that served it, a new `cache-optimized` combo strategy + Auto-Combo `cacheAffinity` factor route repeat requests back to the connection holding the cached prefix, and a read-only `/v1/auto-combo/{channel}/candidates` endpoint exposes an `auto/*` channel's live candidate pool. → [Auto-Combo](docs/routing/AUTO-COMBO.md)
- **⚡ Local performance & infra** — one-click local Redis, Cloudflare Workers / Deno Deploy relay deployers, Bifrost & Mux as supervised embedded services. → [Embedded Services](docs/frameworks/EMBEDDED-SERVICES.md)
- **🧩 Also in the box** — plugin framework + marketplace, Omni/Agent/GitHub skills frameworks, Obsidian vault integration (22 MCP tools), OpenAI-compatible Batch & Files APIs, semantic response cache, gamification with leaderboards, ACP agent discovery (15 built-in agents), scheduled log export to BigQuery, `auto/chaos` parallel multi-model fan-out, a Telegram bot bridge, an in-app version manager and LMArena-ELO free-provider rankings. → [Docs](docs/README.md)
@@ -697,11 +702,11 @@ of your shell history. → [CLI Integrations](docs/guides/CLI-INTEGRATIONS.md)
<div align="center">
## 🌐 393 AI Providers — 153 Catalog-Marked Free
## 🌐 394 AI Providers — 153 Catalog-Marked Free
</div>
> **393 registered providers** across the canonical chat, media, search, local, cloud-agent and system collections, including **153 carrying `hasFree: true` discovery metadata**. The chat model registry covers **239 providers / 3,059 distinct provider-model pairs / 1,475 raw model IDs**; the separate free-budget catalog has **465 per-model rows**, **34 recurring pools** and **51 recurring/keyless free-forever providers**. These are different denominators by design; definitions and pool-deduped calculations live in the [Provider Reference](docs/reference/PROVIDER_REFERENCE.md) and [Free Tiers](docs/reference/FREE_TIERS.md).
> **394 registered providers** across the canonical chat, media, search, local, cloud-agent and system collections, including **153 carrying `hasFree: true` discovery metadata**. The chat model registry covers **239 providers / 3,059 distinct provider-model pairs / 1,475 raw model IDs**; the separate free-budget catalog has **465 per-model rows**, **34 recurring pools** and **51 recurring/keyless free-forever providers**. These are different denominators by design; definitions and pool-deduped calculations live in the [Provider Reference](docs/reference/PROVIDER_REFERENCE.md) and [Free Tiers](docs/reference/FREE_TIERS.md).
<div align="center">
@@ -1318,7 +1323,7 @@ Métricas canônicas em 2026-10-18: **1.976 vídeos únicos** · **20.220.289 vi
<tr><td nowrap><b>Language</b></td><td>TypeScript 6.0 — <b>100% TypeScript</b> across <code>src/</code> and <code>open-sse/</code> (zero <code>any</code> in core since v2.0)</td></tr>
- **feat(systemone):** `POST /v1/systemone` can serve `ollama-local/<model>` decisions models on the local Ollama of the existing `ollama-local` connection (its base URL, default `http://localhost:11434/v1`, never a request field), with Ollama's own limits checked before any upstream call (2–26 candidates per choice/score question, at most 64 questions, no chat sampling fields, raw base64 images only, 64 KiB / 32 MiB body cap); opt-in through the `SYSTEMONE_OLLAMA_LOCAL_BACKEND_ENABLED` feature flag (default off) ([#14667](https://github.com/diegosouzapw/OmniRoute/pull/14667)) — thanks @PixmaNts
- **feat(routing):** new `jev` combo strategy — you order the providers, one TypeSafe System One `choice` call admits the winner plus up to 4 fallbacks (options at or above 0.15 confidence) for each request; a missing key, timeout or low confidence falls open to your own order, live session pins skip the call, and the combo editor shows a privacy note because the latest user message is sent to TypeSafe. The TypeSafe call is opt-in through the `COMBO_JEV_STRATEGY_ENABLED` feature flag (default off): a stored TypeSafe key alone never sends traffic, and with the flag off a jev combo keeps your order ([#15279](https://github.com/diegosouzapw/OmniRoute/pull/15279)) — thanks @miguelenes
- Use registered local-provider URLs for model discovery and synchronized embedding routes, and align Docker Model Runner's default with its engine-neutral OpenAI endpoint. Docker Model Runner embedding requests now accept keyless connections while preserving configured credentials and per-model capability checks. (#16670)
- **feat(systemone):** `POST /v1/systemone` can serve TypeSafe Jev and Cloudflare Clef / Clef-flash on Cloudflare Workers AI through the existing `cloudflare-ai` connection (`cloudflare-ai/jev`, `cloudflare-ai/clef`, `cloudflare-ai/clef-flash`, alias `cf/`), as a new `systemOneRegistry` backend, opt-in through the `SYSTEMONE_CLOUDFLARE_BACKEND_ENABLED` feature flag (default off) ([#16676](https://github.com/diegosouzapw/OmniRoute/pull/16676)) — thanks @xiaoyaner0201
- feat(codex): add global and per-connection Ultrafast defaults scoped to GPT-6 Astra and GPT-6.1 Sol, while preserving explicit request and API-key precedence. (#16678)
- **feat(dashboard):** "New models" inbox — model sync records each provider's listing (first sync seeds a baseline) and the Providers toolbar shows newly added models with an unread badge, grouped by provider, with mark-as-read ([#16864](https://github.com/diegosouzapw/OmniRoute/pull/16864)) — thanks @ErfanBagheri404
- **feat(search):** Keenable web search and fetch provider (`keenable-search`, alias `keenable`): keyless by default, with an optional API key that only lifts the per-IP rate limits. Serves `/v1/search` (web only, fallback-only so it never displaces a configured paid provider) and `/v1/web/fetch` (Markdown only, capped at 100,000 characters) ([#17920](https://github.com/diegosouzapw/OmniRoute/pull/17920)) — thanks @ilya-bogin-keenable
- **feat(dashboard):** "Quota check" toggle for OpenAI- and Anthropic-compatible nodes reads a standard `/credits` balance into Provider Limits; `anthropic-compatible-*` keys now use the configurable quota fetcher, which goes through the SSRF-guarded outbound fetch ([#18350](https://github.com/cheaper-inference/OmniRoute/pull/18350)) — thanks @MWGE22629
- **feat(providers):** custom JSON API provider nodes — an OpenAI-compatible node with `apiType: "custom-json"` fills a JSON request template (`{{prompt}}`, `{{messages}}`, `{{model}}`, `{{request.<path>}}`; substitution only) for any JSON business endpoint, reads the reply from a response path and returns it in the client's format; business requests are never replayed (no retry, no account or combo fallback). API-only for now, see `docs/guides/CUSTOM_JSON_API.md` ([#18353](https://github.com/cheaper-inference/OmniRoute/pull/18353)) — thanks @lyccccy
- **feat(dashboard):** the OpenAI-compatible Add and Edit provider modals offer the **Custom JSON API** type — HTTP method, auth (bearer, API key header or none), a request-template editor with simple fields or full JSON, the response path and a "Send test request" button — validated in the browser with the same schema the server uses ([#18359](https://github.com/cheaper-inference/OmniRoute/pull/18359)) — thanks @lyccccy
- **feat(pii):** opt-in reversible PII vault (`PII_REVERSIBLE_VAULT_ENABLED`, default off, needs `PII_REDACTION_ENABLED`): request PII becomes per-request surrogate tokens instead of irreversible placeholders, and the chat handler restores the original values in 2xx responses (SSE split across events and JSON, tool arguments and reasoning included). Providers, fusion judges, logs and caches only see tokens; error bodies keep the tokens; memory, idempotency and semantic-cache writes are skipped for masked turns ([#19326](https://github.com/cheaper-inference/OmniRoute/pull/19326), builds on [#18017](https://github.com/cheaper-inference/OmniRoute/pull/18017)) — thanks @Ardem2025
- **test(sse):** Distinguish malformed SSE from valid upstream error frames in the non-streaming regression suites, and verify both initial and fallback errors retain their status, diagnostic and receipt.
- **fix(ci):** Audit all five independent lockfiles with explicit incomplete results, reject missing/invalid OSV measurements, align OpenCode CI with supported Node releases, and reproduce plugin installs from their lockfiles.
- **fix(ci):** Compare OpenAPI contracts against immutable event commits, preventing false removals after the base advances and rejecting incomplete required measurements.
- **fix(ci):** Execute a versioned Release-Green static profile with audit, mutation and i18n checks; reject incomplete scanner measurements and report terminal test failures ahead of expected fixture errors.
- Restore the approved Video Bridge FU-07 material-gain thresholds and fail closed on unbound or incomplete FU-07/FU-09 evidence; require independent candidate/corpus/model-revision-bound receipts, preserve digest-only observations, and expose conservative advanced-policy readiness without automatically promoting experimental modes.
- **fix(ci):** Verify retained release-acceptance evidence against its declared SHA-256 instead of trusting hash syntax alone; missing, changed or unsafe file references remain unverified. Supplied-plan reports explicitly do not certify the complete release pipeline (#17856).
- fix(sse): Codex mid-request 429 failover now selects the replacement account through the quota preflight, so it no longer rotates onto a quota-exhausted account (#18425)
- **fix(providers):** `/v1/models` no longer advertises the local-CLI no-auth providers `auggie` (`aug/*`) and `zcode` (`zc/*`) when their binary cannot be resolved on the host running the server (`AUGGIE_BIN`/`ZCODE_BIN` override, installer paths, PATH); the check runs once per catalog build with a 60 s cache, an explicit connection row keeps the provider listed, and `devin-cli-agentic` / `codex-app-server` stay listed ([#18753](https://github.com/cheaper-inference/OmniRoute/issues/18753))
- fix(dashboard): provider quota "Resets in" countdowns now follow a shared 30-second clock instead of being frozen by React Compiler memoization (#18772)
- fix(providers): always publish the bare master `auto` router in the OpenCode v2 plugin default view instead of dropping it through the per-owner showcase cap (#19016)
- **fix(sse):** the chat ingest byte budget now charges every chunk of a body sent without Content-Length and the decoded size of compressed bodies, and decompression stops at the budget room instead of expanding first
- Route the GitLab, GHE Copilot, CLIProxyAPI, 9Router, Dario, GLM, GitHub Copilot auto, NLP Cloud and 1min.ai upstream calls through the provider dispatch guard, so their redirects are followed by hand and checked on every hop.
- Persist only the `apiKeyHealth` slice when a key changes health, so request-local values no longer land on the shared connection, and stop the rotator from handing back a sticky key that is in 429 cooldown.
- Keep the `private_key` credential pattern linear, so a body of repeated PEM BEGIN headers no longer blocks the event loop when credential redaction is on.
- Run request-blocking plugin hooks on every call, so a hook that denies or rewrites a request still applies above the per-plugin rate limit, which now covers fire-and-forget hooks only.
- Keep replayed tool-call reasoning inside the API key and session that produced it, so a reused tool call id such as `call_0` cannot return another caller's reasoning.
- Accept a caller-supplied SearXNG `provider_options.baseUrl` only for public hosts, on every hop and DNS answer; loopback and LAN instances are configured on the stored connection.
- Require a dashboard session or a manage-scoped key on `/api/agent-skills/generate`, `/api/skills/marketplace/install` and `/api/skills/skillssh/install` even when login is disabled.
- **fix(sse):** token counting no longer blocks the event loop on long runs of one character class or heavy CJK input; it switches to a linear estimate and keeps the exact count for ordinary text
- **fix(quality):** the test impact map is written one entry per line inside `sources`/`artifacts` and read line by line from a Buffer (`readTestImpactMap`), so `check-forgotten-sibling-tests` and `select-impacted-tests` no longer hit V8's 512 MiB string limit. The release map had reached 536.8 MB, 77 KB under the ceiling, and PRs that added tests failed Fast Quality Gates with "Cannot create a string longer than 0x1fffffe8 characters" (#19329).
- **test(dashboard):** move the #19337 "forwards supportsVision and max_output_tokens" case to the no-connection import block. Since #19254 a provider with a connection imports through the model sync, so the case never reached `POST /api/provider-models` and kept `release/v3.8.54` red (#19329).
- **fix(dashboard):** clear the request detail "copied" reset timers on unmount. Left running, the 2 s timer fired after the sheet (and, in Vitest, jsdom) was gone and threw "window is not defined" as an unhandled error, failing the whole UI job while every test passed (#19329).
- **test(video):** document the explicit source directory for isolated live validation, keep private preparation under the same `/tmp` root required by both consumers even when the runner overrides `TMPDIR`, and parse source environment files with Node's native parser instead of an undeclared dependency ([#16083](https://github.com/diegosouzapw/OmniRoute/pull/16083)).
- Reject preloaded database bindings before private preparation mutates client keys, authenticate the isolated STT owner explicitly, and enforce one-shot dispatch even for concurrent requests. Component errors use the canonical sanitized envelope.
- **quality:** add an exact-commit production-source inventory and independent verifier for the unified-coverage denominator, including never-imported sources and rejecting reduced or forged scope receipts. This is inventory infrastructure only; coverage collectors, CI thresholds, and release acceptance are unchanged ([#16177](https://github.com/diegosouzapw/OmniRoute/pull/16177)).
- **docs:** Document the live API-key, resolved-target and combo-routing surfaces separately from the reserved domain policy/combo/container contracts ([#17337](https://github.com/cheaper-inference/OmniRoute/pull/17337), refs #17187)
- **ci(workflows):** the VPS deploy now accepts a `workflow_run` only from this repository, a trusted event and a release ref, publishing and opencode workflows no longer restore a package-manager cache, and the Semgrep image is pinned by digest ([#18165](https://github.com/cheaper-inference/OmniRoute/pull/18165))
- **ci:** pin every remaining GitHub Action in `.github/workflows` to the commit SHA of its tag (tag kept as a comment for Dependabot), drop the unused checkout credential in `base-ci-repair` and `wiki-sync`, and remove the redundant workflow-level `issues: write` from `nightly-compat` — zizmor findings 216 → 13 ([#19321](https://github.com/cheaper-inference/OmniRoute/pull/19321))
- **chore(release):** stop feature PRs from writing values that depend on the base. The `package.json` description (and `flake.nix`) now say "hundreds of providers" instead of the exact count, and the docs-counts gate rejects a provider count there instead of requiring the live one (25 open PRs conflicted on that line alone). Stryker's `tap.testFiles` is no longer a hand-kept list: `stryker.conf.json` became `stryker.conf.mjs`, which computes the list at load time from `mutate` with the same import rule `check:mutation-test-coverage --strict` enforces (shared in `scripts/quality/mutation-test-files.mjs`); the 109 former entries the rule does not select stay pinned, so the resolved list matches the old 775 unique paths exactly. `stryker.disablebail.json` became `stryker.disablebail.mjs`, which spreads the base config — Stryker 10 ignored its `"extends"` key, so the redundancy run never got the base config. ([#20157](https://github.com/cheaper-inference/OmniRoute/pull/20157))
- **feat(ci):** derived numbers are resolved at release, not in every PR. `check:docs-counts` gains a `pr` mode for feature PRs (diff against the PR base: it fails only a managed number the PR wrote or a required claim it removed, never a base that moved) and keeps today's strict comparison as the `release` mode; a facts-collection timeout is now an infrastructure error (exit 2) instead of a false drift. New `npm run facts` (every derived number as JSON), the committed snapshot `docs/reference/derived-facts.json` that the README SVG generators read, and `npm run release:refresh-derived [--check]`, which rewrites every derived value in one pass. Release-Green reports the strict view as drift instead of opening a base-red, and a nightly workflow keeps one `chore/derived-refresh` PR with the refreshed values. ([#20161](https://github.com/cheaper-inference/OmniRoute/pull/20161))
- **chore(docs):** the agent-instruction files no longer carry derived counts. `AGENTS.md`, `llm.txt` (and its 66 mirrors), the bs `AGENTS.md` fork, `open-sse/services/AGENTS.md`, `agentSkills.ts`, `skills/README.md` and the skills point to the source (`ROUTING_STRATEGY_VALUES`, `DEFAULT_WEIGHTS`, the migrations directory) and to `npm run facts` instead of provider, migration, MCP-tool, scope, strategy, scoring-factor and mode-pack counts that every provider PR rewrote (on 2026-11-13, 37 open PRs edited the count lines of `AGENTS.md` and 36 those of `llm.txt`). A new STRICT invariant in `check:docs-counts` keeps a count from coming back, in both gate modes. ([#20162](https://github.com/cheaper-inference/OmniRoute/pull/20162))
- **chore(ci):** derived files get one writer. The new `check:pr-derived-paths` (job PR Test Policy) flags a feature PR that carries files a refresh owns — the families in `config/quality/derived-paths/*.json` — and allows writer branches (`release/v*`, `docs/i18n-*`, `chore/i18n-*`, `chore/derived-*`) and PRs that touch one family only; it runs advisory (`--warn`, with a check annotation) until the open PRs are cleaned up. `scripts/check/lib/gateMode.mjs` resolves the `pr`/`release` mode every derived-content gate shares (`--mode`, then `OMNIROUTE_GATE_MODE`, then the Actions event). `check:test-masking` lists the gate-mode conditional skips in a report-only block.
- **chore(i18n):** translation mirrors are derived files: a feature PR edits only the English source, and the `docs/i18n/**` mirrors are rewritten by the translation wave and the release. `check:docs-sync` skips the 66 `llm.txt` mirror copies and the translated `CHANGELOG.md` checks in PR mode (strict in release mode, and in PR mode for a writer branch or, when the diff base resolves, a change that edits mirrors; in PR mode the `llm.txt` mirrors must still agree with each other or with the root, so a hand edit fails even in a depth-1 checkout); the pre-commit hook runs it with `--mode=pr`; the scheduled `i18n-mirror-refresh.yml` now also syncs stale `llm.txt` mirrors; six mirror-content unit tests assert only up-to-date mirrors in PR mode through `tests/_helpers/mirrorFreshness.ts`; `scripts/i18n/sync-llm-mirrors.mjs` exports `syncLlmMirrors()` and gains `--dry-run`
- **chore(i18n):** a feature PR now adds or rewrites UI and CLI strings in `en.json` only; the other locales are completed once per release. The completeness gates (`check-key-completeness` UI and CLI, `check-new-key-coverage`, `check-ui-value-drift`, `check-translation-ratio`, the locale-parity part of `check:cli-i18n`) and the parity assertions of `cli-i18n-catalog`, `i18n-pt-br` and `i18n-vi-completeness` skip in pr mode and stay strict in release mode (release PR, pushes to main, local runs). `config/quality/derived-paths/translation.json` declares the translation family for `check:pr-derived-paths`. `sync-ui-keys.mjs` gains the programmatic `syncUiKeys()` for `release:refresh-derived`, plus `--rewritten-since=<ref>` (re-queues translations of rewritten English) and explicit `--prune-extra` / `--keep-extra`
- **chore(ci):** generated files and derived baselines stay out of feature PRs — `PROVIDER_REFERENCE.md`, the twelve generated README SVGs, the fully generated agent skills and `config/quality/e2e-timings.json` are rewritten by the release refresh, not by each PR; `check:agent-skills-sync`, the SVG byte-compare tests, the e2e-timings completeness test and `--require-tighten` judge only what a feature PR itself edited (release mode unchanged); the new `check:generated-artifacts` judges an SVG or timings file a PR edits with full history (fail-closed without a base), `check:test-masking` reports gate-mode conditional skips, and `.gitattributes` collapses the generated diffs
- **quality:** add opt-in original-source coverage capture for Node/tsx and isolated Vitest Node/UI workers, independent start/completion ledgers, and counter composition with zero-hit production sources. JSON and LCOV share the same verified union; missing or incompatible receipts and results below the unchanged 60/60/60/60 floor fail closed. This remains shadow infrastructure, not full CI or release acceptance, and does not replace the current coverage ratchet.
"description":"Quality baselines that are pure measurements of the tree and that no gate asks a feature PR to edit (the obligation was moved to release mode or never existed). They are rewritten by the release refresh or a nightly job. Policy files (allowlists, gate-manifest, admission policies, provenance) and baselines a feature PR must legitimately edit together with code (typecheck/file-size/complexity ceilings, quality-baseline.json, eslint-suppressions.json) are deliberately NOT here. Plan 2026-11-13, phase 5.",
"why":"Relative weights for the Playwright shard packer. A spec without an entry already gets the median weight at run time; the completeness test (tests/unit/balance-e2e-shards.test.ts) runs in release mode only.",
"description":"Files written by a generator from the catalog/OpenAPI/registries. A feature PR changes the source (providers.ts, openapi.yaml, the skill catalog, the free-tier catalog); the generated copy is rewritten once by the release refresh (release:refresh-derived) or a nightly refresh PR, so sibling PRs stop conflicting on it. A PR that changes only a generator and its output (the companions below) is still allowed. Plan 2026-11-13, phase 5.",
"writers":["release/v*","chore/derived-*"],
"companions":[
"changelog.d/**",
"scripts/docs/gen-provider-reference.ts",
"scripts/docs/gen-readme-*.mjs",
"scripts/docs/readme-*.mjs",
"tests/unit/docs/readme-*.test.ts",
"docs/diagrams/README.md",
"scripts/skills/**",
"src/lib/agentSkills/**",
"tests/unit/agentSkills-*.test.ts",
"tests/unit/agent-skills-*.test.ts"
],
"categories":[
{
"id":"derived-facts",
"paths":["docs/reference/derived-facts.json"],
"why":"Snapshot of every derived number (provider total, MCP tools, routing strategies, free-tier tokens, ...) the README diagrams and the counts gate read between releases; written only by the release refresh or the nightly refresh PR (plan 2026-11-13, phase 1).",
"refreshedBy":"npm run release:refresh-derived (or npm run facts)"
},
{
"id":"provider-reference",
"paths":["docs/reference/PROVIDER_REFERENCE.md"],
"why":"Generated from src/shared/constants/providers.ts (whole catalog + totals + version/date header): every provider PR rewrote it, 30 of 321 open PRs on 2026-11-13.",
"refreshedBy":"npm run gen:provider-reference (release:refresh-derived)"
},
{
"id":"readme-diagrams",
"paths":[
"docs/diagrams/readme-hero.svg",
"docs/diagrams/free-tier-budget.svg",
"docs/diagrams/works-zero-config.svg",
"docs/diagrams/promise-pillars.svg",
"docs/diagrams/why-pain-fix.svg",
"docs/diagrams/tier-cascade.svg",
"docs/diagrams/strategies-grid.svg",
"docs/diagrams/resilience-layers.svg",
"docs/diagrams/comparison-table.svg",
"docs/diagrams/privacy-local.svg",
"docs/diagrams/cli-terminal.svg",
"docs/diagrams/compression-pipeline.svg"
],
"why":"Generated by scripts/docs/gen-readme-*.mjs (README_DIAGRAMS in gen-readme-diagrams.mjs) from live catalogs and counts; 26-28 open PRs rewrote the hero, comparison, pillars and terminal cards. Hand-drawn SVGs (pool-fair-share, combo-always-on, public/images/tier-flow-*) and the Mermaid exports are not in this list.",
"refreshedBy":"npm run docs:readme-diagrams (release:refresh-derived)"
},
{
"id":"agent-skill-references",
"paths":["skills/*/references/**"],
"why":"skills/<id>/references/endpoints.md is written entirely by src/lib/agentSkills/generator.ts from docs/openapi.yaml.",
"why":"SKILL.md files with no hand-written custom block: the generator writes every byte. SKILL.md files that carry a <!-- skill:custom-start --> block are hand-edited too and stay out of this list (tests/unit/derived-paths-generated-family.test.ts keeps the list exact).",
"description":"Everything translated from an English source: the dashboard and CLI catalogs of the non-English locales, the docs/i18n mirrors with their hash ledger, and the real-translation ratchet measured on them. A feature PR edits only the English source (src/i18n/messages/en.json, bin/cli/locales/en.json, the English docs); these files are rewritten once per release by release:refresh-derived, by a translation wave, or by the scheduled mirror-refresh PR. The compact error-boundary catalogs (src/i18n/global-error-messages) are companions, not a category: they are regenerated from the catalogs on every build, a translation-only PR may carry them, and a feature PR that edits en.json publicSystem.globalError must still be able to regenerate them.",
"why":"A feature PR adds or rewrites keys in en.json only; at runtime the dashboard falls back to English (src/i18n/request.ts deepMergeFallback) until the locales are completed. Catalog edits carried by feature PRs conflicted on every merge (48 open PRs touched the same ~43 catalogs on 2026-11-13).",
"refreshedBy":"release:refresh-derived → syncUiKeys({ catalog: \"ui\", pruneExtra: true, rewrittenSinceRef, translate: true }) in scripts/i18n/sync-ui-keys.mjs (CLI: node scripts/i18n/sync-ui-keys.mjs --rewritten-since=<ref> --translate-markers --batch-size=40), or a translation wave branch"
},
{
"id":"cli-locale-catalogs",
"paths":["bin/cli/locales/*.json"],
"except":["bin/cli/locales/en.json"],
"why":"A feature PR adds CLI strings to bin/cli/locales/en.json only; the CLI falls back to English until the locales are completed.",
"why":"The 66 translated mirrors of the English docs and their hash ledger are rewritten from the English source; a feature PR edits the English doc only.",
"refreshedBy":"npm run i18n:run -- --files=<doc> on a translation wave branch (docs/i18n-*), the scheduled i18n-mirror-refresh workflow (chore/i18n-mirror-refresh), or release:refresh-derived"
"why":"The real-translation ratchet is measured on the locale catalogs, so it only moves when they do; on a feature PR the ratio gate runs in release mode (SKIP) and there is nothing for the PR to tighten.",
"refreshedBy":"npm run i18n:check-ratio:update after the catalogs are refreshed (release:refresh-derived or a translation wave)"
{"recordType": "manifest", "schemaVersion": 1, "expectedAssetCount": 146, "auditedCommit": "959ff4dd89fc8bbe373c86210e90c1f49c81863c", "auditedAt": "2026-11-08", "scope": "Every regular file directly under public/providers at the audited commit.", "statusSemantics": {"proven": "Immutable source plus byte-exact or SVG path-data match.", "probable": "Repository evidence suggests provenance, but no immutable upstream match is proven.", "unresolved": "No sufficient immutable provenance evidence is recorded."}, "enforcement": "All physical files, hashes, magic MIME values, statuses, and duplicate aliases are blocking. Probable and unresolved statuses are recorded but non-blocking in schema version 1.", "legalScope": "Provenance records source matching only; it does not establish copyright or trademark clearance."}
{"recordType": "manifest", "schemaVersion": 1, "expectedAssetCount": 146, "auditedCommit": "895c0f3571a9265a757f27c8700a1a4b971b0092", "auditedAt": "2026-11-08", "scope": "Every regular file directly under public/providers at the audited commit.", "statusSemantics": {"proven": "Immutable source plus byte-exact or SVG path-data match.", "probable": "Repository evidence suggests provenance, but no immutable upstream match is proven.", "unresolved": "No sufficient immutable provenance evidence is recorded."}, "enforcement": "All physical files, hashes, magic MIME values, statuses, and duplicate aliases are blocking. Probable and unresolved statuses are recorded but non-blocking in schema version 1.", "legalScope": "Provenance records source matching only; it does not establish copyright or trademark clearance."}
{"recordType":"asset","path":"public/providers/chatgpt-logo-black.svg","mediaType":"image/svg+xml","sha256":"b8b9aba7ba591f54bf1805f422bc23f32c44ee993643cc378cc77f766061f7a1","provenanceStatus":"probable","source":null,"upstreamLicenseClaim":null,"trademarkClearance":null,"evidenceNote":"Retrieved byte-for-byte on 2026-09-30 from https://developers.openai.com/assets/siwc/sign-in-buttons/chatgpt-logo-black.svg, referenced by the official SIWC button examples at https://developers.openai.com/siwc/website. Used to identify the ChatGPT sign-in provider. Official URL is mutable; no immutable Git/npm provenance or independent rights clearance is claimed."}
{"recordType":"asset","path":"public/providers/chatgpt-logo-white.svg","mediaType":"image/svg+xml","sha256":"568ce2e8701934856aaafc0ed1c3d0300f6c2ff384d0ae743dd1dea08570e12c","provenanceStatus":"probable","source":null,"upstreamLicenseClaim":null,"trademarkClearance":null,"evidenceNote":"Retrieved byte-for-byte on 2026-09-30 from https://developers.openai.com/assets/siwc/sign-in-buttons/chatgpt-logo-white.svg, referenced by the official SIWC button examples at https://developers.openai.com/siwc/website. Used to identify the ChatGPT sign-in provider. Official URL is mutable; no immutable Git/npm provenance or independent rights clearance is claimed."}
{"recordType": "asset", "path": "public/providers/360ai.svg", "mediaType": "image/svg+xml", "sha256": "59366fe04a4336518b8277b430f4a464a91e7ec944c9cf6f40a945c74002386d", "provenanceStatus": "proven", "source": {"kind": "npm", "url": "https://registry.npmjs.org/@lobehub/icons/-/icons-5.10.0.tgz", "ref": "5.10.0", "path": "package/es/Ai360/components/Color.js", "integrity": "sha512-CIpjkISCLRK7haDtSugGFd0o3odaJts8ewJOkUiEFtns3xvsqbl8i24eowBnjw+yMDQVQyNONlhqTD58YC6Ljg==", "packageShasum": "add1baced073a60157d39c7820b8d5c1928a1054", "match": "svg-path-data", "matchDetail": "All 5/5 local SVG path d values match the pinned Color component."}, "upstreamLicenseClaim": {"value": "MIT", "assertedBy": "@lobehub/icons@5.10.0 package/LICENSE", "evidence": "https://registry.npmjs.org/@lobehub/icons/-/icons-5.10.0.tgz#package/LICENSE", "independentlyVerified": true, "scope": "Pinned package distribution only; no trademark clearance."}, "trademarkClearance": null, "evidenceNote": "All local SVG path data matches the pinned LobeHub Color component. This proves source provenance only, not trademark clearance."}
"scope":"Explicit local full-observer static commands. Workflow shell is not an argv source. Runtime suites, coverage artifacts, external checks, publication and deployment require separate evidence.",
"sourceJobs":[
"lint",
"quality-gate",
"quality-extended",
"docs-sync-strict",
"pr-test-policy",
"i18n-ui-coverage",
"i18n-glossary-zhcn"
],
"exclusions":[
{
"alias":"check:pr-evidence",
"reason":"Requires the pull request body; evaluated by hosted admission."
},
{
"alias":"check:ai-attribution",
"reason":"PR event metadata is evaluated by hosted admission; commit-message hooks remain active."
},
{
"alias":"check:codeql-ratchet",
"reason":"Reads remote CodeQL state and requires hosted security permissions."
},
{
"alias":"check:pr-derived-paths",
"reason":"Judges a pull request's own diff against its base (pr mode, advisory); release mode prints SKIP by design."
"command":"npm run check:docs-sync && npm run check:docs-frontmatter && npm run check:docs-counts && npm run check:env-doc-sync && npm run check:deprecated-versions && npm run check:doc-links && npm run check:fabricated-docs"
-Reserved policy-evaluation contract: `src/domain/policyEngine.ts`; the request path enforces API-key policy through `src/shared/utils/apiKeyPolicy.ts` and resolved-target authorization through `src/sse/handlers/chat/resolvedModelPolicy.ts`
prefixes, and wildcard model targets to concrete execution plans
-Reserved combo resolver: `src/domain/comboResolver.ts` — standalone selection contract; live combo routing is implemented in `open-sse/services/combo.ts`
inspect their applicable checks and receipts independently. The prose
inventory below is a reference, not proof that a gate actually ran.
inspect their applicable checks and receipts independently. The full observer's static
commands are declared in `config/quality/release-green-static-profile.json`, including
`audit:deps`, mutation-test selection and translation checks. The loader validates npm
commands against package.json and modeled CI/Quality declarations; it rejects drift
instead of executing shell tokens as arguments. Required scanner SKIP/INCOMPLETE output
cannot establish PASS. The profile records its external exclusions and does not replace
hosted coverage, test matrices, package or deployment evidence. The prose inventory below
is a reference, not proof that a gate actually ran.
Scripts live under `scripts/check/` (policy gates) and `scripts/quality/` (ratchet engine).
The CI source of truth is `.github/workflows/ci.yml`.
@@ -130,7 +151,7 @@ Runs on every PR to `main`. Blocks merge on failure.
| `check:model-lifecycle` | The three hand-maintained routing tables stay consistent with the checked-in lifecycle snapshot (#11503): `FITNESS_TABLE` (`taskFitness.ts`) scores no retired id that `REGISTRY` can route; every `BUILT_IN_ALIASES` target is present in `REGISTRY` and absent from the retired-id snapshot; every retired id still in `REGISTRY` is forwarded or listed in `allowedRetiredInCatalog`; and no `DEFAULT_DEGRADATION_MAP` source or target appears retired in that snapshot. This does not prove that a model is currently served by a live upstream. Offline — compares against `config/quality/model-lifecycle.json`, refreshed by hand with `npm run quality:refresh-model-lifecycle` (network; not wired into CI). `allowedRetiredInCatalog` is a burn-down ratchet: add an entry only with a tracking issue. | Yes |
| `check:fetch-targets` | Every `fetch("/api/...")` in client-side `src/` resolves to a real `route.ts` | Yes |
| `check:deps` | All `npm install`-able deps across every `package.json` in the repo are in `dependency-allowlist.json`; new unpinned or slopsquatted packages flagged | Yes |
| `audit:deps` | npm audit of all five independent lockfiles (root, Electron, OpenCode plugins v1/v2 and provider). Critical advisories block; high advisories remain visible warnings. Missing/failed audits are INCOMPLETE and block; per-scope lock hashes and reports are retained. | Yes |
| `check:licenses` | SPDX license allowlist for production dependencies | Yes |
| `check:tracked-artifacts` | No build artifacts / committed `node_modules` symlinks (also runs in husky pre-commit; pre-push is intentionally light — #6716) | Yes |
@@ -145,7 +166,7 @@ Runs on every PR to `main`. Blocks merge on failure.
| `check:route-guard-membership` | Every route that spawns a child process is classified by `isLocalOnlyPath()` (Hard Rules #15/#17) | Yes |
| `check:test-discovery` | Every `*.test.ts` / `*.spec.ts` file in the repo is collected by at least one test runner (ratchet: orphan list in `test-discovery-baseline.json` can only shrink) | Yes |
| `check:test-tla-order` | No `node:test` file under `tests/unit` registers a test, hits a top-level `await`, then registers more (#18045; ratchet: `test-tla-order-allowlist.json` can only shrink) | Yes |
| `check:agent-skills-sync` | Generated agent-skills artifacts match their source catalog (no drift) |
| `check:agent-skills-sync` | Generated agent-skills artifacts match their source catalog (no drift). Release mode checks every skill; a feature PR (`pr` mode) checks only the skills whose generated text it edits — see [Generated files and derived baselines](#generated-files-and-derived-baselines-written-at-release) |
| `check:provider-asset-provenance` | Provider logos/assets carry a recorded provenance entry |
| `lint:json` | JSON config files parse and satisfy the repo lint rules |
| `check:vuln-ratchet` | Dependency vulnerabilities (osv-scanner) do not regress — skips if binary absent | **Advisory** |
| `check:vuln-ratchet` | Dependency vulnerabilities (osv-scanner) do not regress — `--ratchet` fails as INCOMPLETE (exit 2) if unmeasured | **Advisory** |
| `check:workflows` | Workflow lint (actionlint + zizmor); missing/broken scanners, invalid reports or missing ratchet baseline fail as INCOMPLETE. Valid findings follow the selected strict/advisory/ratchet policy | Execution required; zizmor ratchet blocking in CI |
| `check:openapi-breaking` | Breaking changes to the public API contract (`openapi.yaml`) vs the base branch (oasdiff) — emits `openapiBreaking=N`; skips if oasdiff absent or base spec unresolvable | **Advisory** |
| `check:openapi-breaking` | Public API contract against pinned event commits (PR merge-base, push before, merge-group base; scheduled/manual checkout first parent); required measurement fails closed | **Blocking with --ratchet** |
### Job: `docs-sync-strict`
@@ -206,43 +227,212 @@ Runs on every PR to `main`. Blocks merge on failure.
| ↳ `check:docs-counts` | Counts in prose (provider count, migration count, etc.) are within the ratchet window of the real counts | Yes |
| ↳ `check:docs-sync` | CHANGELOG / OpenAPI version consistency; release mode also the 66 `llm.txt` mirrors and translated CHANGELOG sections (PR mode: mirrors agree) | Yes |
| ↳ `check:docs-counts` | Counts in prose (provider count, migration count, etc.). Two modes: `pr` on feature PRs, `release` elsewhere — see "Derived values" below | Yes |
| ↳ `check:env-doc-sync` | Every env var in `.env.example` is documented in a docs table, and vice versa | Yes |
| ↳ `check:deprecated-versions` | No deprecated version strings in docs | Yes |
| ↳ `check:doc-links` | Internal markdown links in docs resolve to real files (`[text]`/`(path)` form) | Yes |
| ↳ `check:fabricated-docs` | Routes, env vars, CLI commands, hook names, and file paths cited in docs exist in the codebase. Hard gate via `--strict`; soft-fail without flag. | Yes (via `--strict` in CI) |
| `check:cli-i18n` | CLI command strings are present in all i18n locale files | Yes |
| `check:cli-i18n` | CLI `t()` keys exist in `bin/cli/locales/en.json` (both modes); pt-BR / zh-CN / zh-TW parity with `en.json` in release mode only | Yes |
| `check:openapi-coverage` | OpenAPI spec covers at least a ratcheted floor of real routes | Yes |
| `check:openapi-security-tiers` | Security tier annotations in `openapi.yaml` are consistent with `routeGuard.ts` classifications | **Advisory** |
| `check:openapi-routes` | Every path in `openapi.yaml` resolves to a real `route.ts` (anti-hallucination) | Yes |
| `check:docs-symbols` | Every `/api/...` reference in `docs/**/*.md` resolves to a real `route.ts` (anti-hallucination) | Yes |
| `i18n translation drift` | Untranslated keys in i18n locale files — warn only | **Advisory** |
| `i18n translation drift` | `docs/i18n/**` mirrors vs `.i18n-state.json` — advisory on PRs (mirrors are refreshed by the translation wave), strict on push and nightly | **Advisory**on PRs |
#### Translation mirrors are derived files (PR mode vs release mode)
A feature PR edits only English sources. The `docs/i18n/<locale>/**` mirrors (including the 66
`llm.txt` copies and the translated `CHANGELOG.md` files) and `.i18n-state.json` are rewritten in
one step by the translation wave (`docs/i18n-*` / `chore/i18n-*` branches, the scheduled
`i18n-mirror-refresh.yml`) and by the release (`npm run release:sync-changelog-i18n`). The mirror
gates therefore run in two modes, resolved by `scripts/check/lib/gateMode.mjs` (`--mode=pr|release`,
then `OMNIROUTE_GATE_MODE`, then the Actions event; a local run is `release`):
-`check:docs-sync` — release mode runs every check. PR mode keeps the package.json/OpenAPI version,
the root CHANGELOG headings and the superseded-docs guard, and prints
`SKIP reason=pr-mode` for the `llm.txt` mirror copies and the translated CHANGELOG sections —
unless the PR writes mirrors: a head branch declared as a writer of the `docs/i18n/**` family in
`config/quality/derived-paths/*.json` runs both checks strictly, and, when the diff base
resolves, a change whose own diff edits `docs/i18n/<locale>/llm.txt` or `CHANGELOG.md` runs that
check strictly. The diff base does not resolve in a depth-1 checkout (the `docs-sync-strict`
job), so PR mode also runs one check that needs no base: every `llm.txt` mirror must exist, keep
its `---` separator and carry either the root body or the body most mirrors share. A base that
moved leaves all mirrors equally stale and passes; a hand edit to one mirror fails. The
translated `CHANGELOG.md` files have no such check in a depth-1 PR checkout.
- The pre-commit hook runs `check-docs-sync.mjs --mode=pr`: a commit is judged on what it does.
Without the flag a local run is release mode, and one merged PR that edits the root `llm.txt`
would block every later commit on that base until the wave ran. The same rule holds for any
mode-aware gate a Husky hook runs: the hook passes `--mode=pr`, and the strict verdict stays
with the release-mode runs (the release PR, pushes to `main`, a plain local run).
- Mirror-content unit tests (`tests/_helpers/mirrorFreshness.ts`: `cycle-docs-mirror-contract`,
`docs/*-locales`) — release mode asserts every locale. PR mode asserts only the mirrors that are
current with the English source according to `.i18n-state.json` (whole-file hash, or the recorded
section hash of the section the test pins) and skips the stale ones with a reason. The
`target_hash` provenance checks run for every locale in both modes. Freshness is per `## `
section, the unit `run-translation.mjs` hashes; a long section (the gate inventory of this file
is about half of it) means any edit in it leaves those mirrors stale, and their PR-mode
assertions skip until the next wave. An anchor the English source no longer contains falls back
to the whole-file comparison.
-`i18n translation drift` — advisory on PRs, strict on push, nightly and the release cut, so a
stale mirror cannot ship in a release.
`scripts/i18n/sync-llm-mirrors.mjs` (also exported as `syncLlmMirrors()`, with `--dry-run`)
rewrites the `llm.txt` mirrors; the release refresh, the translation wave and the scheduled
`i18n-mirror-refresh.yml` run it (the refresh detects stale `llm.txt` mirrors with a dry run, since
the drift report does not list them, and syncs them before `check:docs-all`).
The twelve README SVGs under `docs/diagrams/` are generated (`scripts/docs/gen-readme-<name>.mjs`;
`npm run docs:readme-diagrams` regenerates all of them). Each has a byte-compare unit test
(`tests/unit/docs/readme-*-svg.test.ts`, job `test-unit`) that fails when the committed file is
stale, and `check:docs-counts` reads canonical numbers from their `<text>` nodes — which is why the
stale in release mode; in a PR, `check:generated-artifacts` judges an SVG the PR edits and the base's
drift is left to the release refresh (see [Generated files and derived baselines](#generated-files-and-derived-baselines-written-at-release)) — and `check:docs-counts` reads canonical numbers from their `<text>` nodes — which is why the
outlining step keeps every outlined string in the file as invisible `<text>`. The SVG canonical-numbers check reads the files listed in
| `release` | Every check, strict equality against the facts collected from the tree (the behaviour the gate always had): a stale count, version, coverage floor or SVG number is a STRICT drift | Yes |
| `pr` | Only what the change did, diffed against the PR base with the same claim extractors: (1) a managed value that did not exist in the base for that check and file ("PR edited a managed number — restore the line to the base text"); (2) a required claim the base carried and the head lost. Content invariants that need no facts run as in release mode; release-only checks are listed and skipped | No |
The agent-instruction files carry **no** derived count at all: `AGENTS.md`, `llm.txt` (and its
`docs/i18n/*/llm.txt` copies), the bs `AGENTS.md` fork, `open-sse/services/AGENTS.md`,
`src/shared/constants/agentSkills.ts`, `skills/README.md` and every `skills/*/SKILL.md` point to the
source (for example `ROUTING_STRATEGY_VALUES` in `src/shared/constants/routingStrategies.ts`) and to
`npm run facts` instead. The invariant "No derived counts (agent-instruction file …)" fails a count
there (providers, migrations, MCP tools and scopes, routing strategies, scoring factors, mode packs)
in both modes, so the release refresh never has to rewrite an instruction file.
In `pr` mode the writer branches may edit managed values: `chore/derived-*` (the nightly refresh
PR), `release/v*`, and the translation waves `docs/i18n-*` and `chore/i18n-*`
| Feature PR — `ci.yml` job `docs-sync-strict`, `quality.yml` step "Docs accuracy" | `pr` (automatic); the job passes the base as `BASE_SHA` and checks out with `fetch-depth: 2` |
| `merge_group`, `omni-queue/**` candidates, the merge train's full gate list | `pr` |
| Release-Green (`scripts/quality/validate-release-green.mjs`) | HARD items run with `OMNIROUTE_GATE_MODE=pr` ("did the base break?"); the DRIFT item `derived-refresh` runs `npm run release:refresh-derived -- --check` (strict view, never opens a base-red) |
| Release (`/generate-release` phases 0a and 1; the skill wiring is a separate owner-approved change) | `npm run release:refresh-derived` writes the derived files; the release PR's own checks then run in `release` mode |
| `nightly-derived-refresh.yml` (daily, highest `release/vX.Y.Z`, skipped under release-freeze) | `npm run release:refresh-derived -- --profile=nightly`; on a diff it keeps ONE PR open from `chore/derived-refresh`; never merges |
The commands behind it:
-`npm run facts` prints every derived number as JSON (`scripts/release/facts.mjs`).
`--key=code.mcpTools` prints one value, `--snapshot` reads the committed snapshot instead of
the live tree. Exit 2 when the facts cannot be collected.
-`npm run release:refresh-derived` (`scripts/release/refresh-derived.mjs`) recomputes the derived
files in one pass, in this order (step ids for `--only=`): `provider-reference`
(`docs/reference/PROVIDER_REFERENCE.md`), `facts` (the snapshot), `numbers` (the counts gate's
rewrite plan applied to the docs, then carried to their `docs/i18n/` mirrors),
`readme-diagrams`, `skills` (generated `SKILL.md`), `e2e-timings` (skipped until the tree
ships `syncE2eTimings`), `ui-keys` (prunes keys `en.json` dropped and, with
`--rewritten-since=<ref>` — default `origin/main` — re-queues English values rewritten since
the last release) and `llm-mirrors`. The
`changelog` step is opt-in (`--with-changelog`, release profile only). `--profile=nightly`
never touches a version claim. With `-- --check` it writes nothing and exits 1 when any file
would change or a managed value needs a manual edit (listing both); exit 2 on an
infrastructure failure. `--json` prints the result as JSON.
-`docs/reference/derived-facts.json` is the snapshot of the facts the last refresh used. Only
the refresh writes it. The README SVG generators read it, and PR-time unit tests compare the
committed docs and generated files with it — never with the live code. The suite's single
live comparison is "the release refresh closes the cycle" in
`tests/unit/check-docs-counts-sync.test.ts`: with the live facts, the refresh's rewrite plan
applied in memory leaves no STRICT drift it does not report, and re-planning changes nothing.
To reproduce locally (a local run defaults to `release`):
```bash
npm run check:docs-counts # release: strict, live facts
node scripts/check/check-docs-counts-sync.mjs --mode=pr # what a feature PR is judged on
OMNIROUTE_GATE_MODE=pr BASE_REF="origin/release/v$(node -p "require('./package.json').version")" npm run check:docs-counts
npm run release:refresh-derived -- --check # what the release would rewrite
```
Without a resolvable base (no `BASE_SHA`/`BASE_REF`, no local `origin/release/v<version>`) a local
`pr` run prints a warning and skips the diff instead of failing.
| `check-ui-value-drift` (inline) | A rewritten English **value** leaves no stale translation behind | Yes |
| `check-new-key-coverage` (inline) | A **new** English key is translated in every locale — a `__MISSING__:` marker is rejected | Yes |
| `check-translation-ratio` | Real-translation ratio per locale (identical-to-English / placeholder / missing leaves outside the allowlist) must not exceed `config/quality/i18n-translation-baseline.json` + slack | **Advisory** |
| `check:ui-icu` | Every message of every UI catalog compiles with `IntlMessageFormat` | Yes (both modes) |
| `check-ui-value-drift` (inline) | A rewritten English **value** leaves no stale translation behind | Yes (release mode only) |
| `check-new-key-coverage` (inline) | A **new** English key is translated in every locale — a `__MISSING__:` marker is rejected | Yes (release mode only) |
| `check-key-completeness` (inline) | Every UI catalog (and, with `--catalog=cli`, every CLI catalog) carries exactly the key set of its `en.json`; in `pr` mode, each catalog the PR changed against itself at the merge base | Yes (both modes) |
| `check-translation-ratio` | Real-translation ratio per locale (identical-to-English / placeholder / missing leaves outside the allowlist) must not exceed `config/quality/i18n-translation-baseline.json` + slack | Yes (release mode only) |
Needs `fetch-depth: 0` — the value-drift gate diffs `en.json` against the merge base.
**Two modes (since 2026-11-13).** A feature PR adds or rewrites keys in `en.json` (and
`bin/cli/locales/en.json`) and touches no other locale; `check:pr-derived-paths` (job
`pr-test-policy`, family `config/quality/derived-paths/translation.json`) fails a feature PR that
does. The other locales are completed once per release by `release:refresh-derived`, which calls
`syncUiKeys()` in `scripts/i18n/sync-ui-keys.mjs` (add missing keys, prune dropped ones, mark
translations of rewritten English with `rewrittenSinceRef`, translate), or by a translation wave.
The gates read the mode from `scripts/check/lib/gateMode.mjs`: in `pr` mode (feature PRs,
`merge_group`, `omni-queue/**`) the release-mode gates above print `SKIP reason=pr-mode` and exit
0; in `release` mode (the release PR, pushes to `main`, `workflow_dispatch`, local runs) they are
strict as before, and on the release PR the diff-aware ones get `BASE_REF=origin/main`, so they
judge every key the cycle added or rewrote. Preview the feature-PR verdict locally with
`--mode=pr`.
A PR that still changes locale catalogs in `pr` mode (a translation wave, the release refresh, a
translation-only fix) is not skipped: `check-key-completeness` judges each catalog it changed
against the same catalog at the merge base (`scripts/i18n/lib/touched-catalogs.mjs`) and fails on
a key the catalog lost, a key `en.json` lacks, a real translation turned into a `__MISSING__:`
marker or into the English text, or a value that no longer interpolates the placeholders/tags of
an English string the PR did not touch. A catalog new in the PR must carry the whole `en.json` key
set. That covers, for the catalogs a PR touches, what the ratio and CLI-parity gates would see.
The locale-parity unit tests (`cli-i18n-catalog`, `i18n-pt-br`, `i18n-vi-completeness`,
`i18n-placeholder-parity`) follow the same modes through `tests/_helpers/localeParityMode.ts`: in
`pr` mode they skip key-parity assertions and leave to the release refresh the placeholder parity
of keys whose English changed since the merge base (every key when the unit-test job's shallow
checkout cannot read it). That helper is the **only** sanctioned mode-conditional skip:
`check:test-masking` counts `.skip(` and `{ skip: true }` but not the computed
`{ skip: "<reason>" }` it returns, so `tests/unit/locale-parity-mode.test.ts` pins the list of
tests allowed to use it — adding one is a reviewed edit to that list.
| `generated` | `docs/reference/PROVIDER_REFERENCE.md`; the twelve generated README SVGs; `skills/*/references/**`; the `SKILL.md` files that have no custom block | `gen:provider-reference`, `docs:readme-diagrams`, `generate-agent-skills.mjs --apply` |
| `check:agent-skills-sync` | every skill must equal the generator output | only the skills whose generated text (outside the custom block) or `references/` the PR edits; otherwise `SKIP reason=pr-mode` |
| `check:generated-artifacts` (README SVGs + e2e timings; needs full history) | every SVG equals its generator; every spec has a timings entry | only the artifacts the PR edits; the rest `SKIP reason=pr-mode`; no diff base → every artifact judged (fail-closed) |
| README SVG byte-compare tests (`tests/unit/docs/readme-*-svg.test.ts`) | every SVG | only an SVG the PR edits, when the base resolves; `test-unit`'s shallow PR checkout has no base, so there the test skips with `SKIP reason=base-unresolved` and `check:generated-artifacts` owns the comparison |
| e2e timings completeness (`tests/unit/balance-e2e-shards.test.ts`) | every spec has an entry | same rule as the SVG tests (a new spec runs with the median weight) |
| `check-quality-ratchet.mjs --require-tighten` | un-banked improvement fails (unless `_policy`) | improvement reported, never a failure; a regression still fails |
Release mode keeps the verdicts, exit codes and messages these checks had before the split; at most
one line is added, naming the resolved mode (`[agent-skills-sync] mode=release (auto: local run)`).
The tests skip through node:test's `{ skip: releaseOnlyUnlessTouched(...) }` option, which
`check:test-masking` lists in a report-only block (it is neither `.skip(` nor `{ skip: true }`, so it
does not count as a hard skip). `check:generated-artifacts` runs where the base is resolvable: job
`lint` (`fetch-depth: 0`), right after `check:agent-skills-sync`. Locally,
`npm run check:generated-artifacts -- --mode=pr` shows what that step judges on a PR. The provider-total
cross-check of `check:docs-counts` ("Provider reference total (doc vs live modules)") is part of the
counts gate and follows that gate's own modes.
Not in a family, on purpose: policy files decided by people (`gate-manifest.json`, the allowlists,
`admission-policy.json`, `provider-assets-provenance.jsonl`, `model-lifecycle.json`) and ceilings a
feature PR may have to edit together with code (`quality-baseline.json` metric entries, the
typecheck/file-size/complexity baselines, `eslint-suppressions.json` — pruned by the pre-commit
ESLint run when a PR fixes a frozen violation). `src/i18n/routeNamespaces.generated.json` is also
generated but stays in feature PRs: the app imports it at run time, so it cannot wait for a refresh.
## Banking Ratchet Shrinks — the downward direction (#8584)
The ratchet is only half automatic, and it is the wrong half. **Raising** a cap is a
@@ -626,7 +873,7 @@ Each candidate was validated against the live gate state on 2026-06-17 (trust-bu
several "obvious" merges turned out to hide debt and are **not** clean drop-ins.
- **`check:docs-sync` runs twice** — standalone in the `lint` job and again inside `check:docs-all` (`docs-sync-strict`) and the husky pre-commit hook. ✅ **DONE** — standalone `lint` invocation removed.
- **CVE scanning** — ❌ **NOT a clean merge.**`audit:deps`hard-fails on any high/critical CVE; `check:vuln-ratchet` (osv) only fails on a _regression_ vs baseline (currently 1 MODERATE). Different semantics — dropping `audit:deps` would lose the absolute high/critical gate. Keep both.
- **CVE scanning** — ❌ **NOT a clean merge.**`audit:deps`blocks critical advisories and incomplete audits across all five lockfiles, while reporting high advisories as warnings under the current policy; `check:vuln-ratchet` (osv) only fails on a _regression_ vs the checked-in baseline and rejects missing measurements when required. Different semantics — dropping `audit:deps` would lose the absolute critical gate and the independent package audit receipts. Keep both.
- **Cycle detection** — ✅ **DONE** (#15159 G-01/G-02). The old text here called `check:cycles` "the green, curated" gate and justified keeping it blocking because `check:circular-deps` (dpdm) reported 91 cycles. That green was a **false green**: `check:cycles` scanned 5 subdirectories (450 files), matched only static `import|export … from`, and dropped every `@/` and `@omniroute/open-sse/` specifier, so it could not see the dynamic-import + alias cycles that dominated the repo. Fixed: the gate now walks `src` + `open-sse` (5023 files), collects specifiers from the TypeScript AST (so `import("…")` counts and type-position `typeof import("…")` does not), and resolves tsconfig `paths`. It finds **14** cycles, not 0. Because 14 pre-existing cycles cannot be fixed in a gate PR, `check:cycles` is now a **ratchet** (`--ratchet`, ceiling `metrics.cycles.value = 14` in `quality-baseline.json`, `direction: down`) — it blocks any _regression_ and the count can only fall. CI runs `npm run check:cycles:ratchet`. Burn-down rides with **A-01**. `check:circular-deps` (dpdm) stays advisory as the broader second opinion.
- **Complexity** — ✅ **DONE** (`check:complexity-ratchets` / `eslint.complexity-ratchets.config.mjs`): one ESLint walk, counts by ruleId so cyclomatic+max-lines and cognitive baselines stay independent; individual `check:complexity` / `check:cognitive-complexity` remain for local `--update`.
- **`/api` anti-hallucination** — ✅ **DONE** (`check:api-docs-refs` + `scripts/check/lib/apiRoutes.mjs`): one FS inventory of `src/app/api`, openapi-routes + docs-symbols still report independently; individuals remain for local runs.
@@ -661,9 +908,13 @@ its branch is cut and translates for days while the base keeps adding keys; the
key itself, so both siblings stayed silent when batch 1 (#13044) landed 43 keys short in nine
locales and batch 2 (#13660) 10 keys short in eight (2026-09-15). Fix a red with
`node scripts/i18n/sync-ui-keys.mjs --locale=<codes> --translate-markers`; an `extra` leaf
means the source dropped it — delete it from the locale. `--warn` reports without failing.
means the source dropped it — `sync-ui-keys` drops it (`--prune-extra`, the default). `--warn`
reports without failing.
`--catalog=cli` runs the same comparison over `bin/cli/locales` (`npm run i18n:check-keys:cli`);
both steps live in job `i18n-ui-coverage`.
both steps live in job `i18n-ui-coverage`. The absolute check is release mode only: a feature PR
sees `SKIP reason=pr-mode` and the fix runs in the release refresh or a translation wave, never in
a feature PR; a PR that changes locale catalogs has each of them judged against the merge base
instead (see "Two modes" under job `i18n-ui-coverage`).
#### `check-new-key-coverage` — new-key i18n gate
@@ -690,7 +941,9 @@ documented deferral — the runtime falls back to correct English — until eigh
2026-09-16 added 61 keys and stamped the marker into all 65 locales instead of translating: this
gate accepted every one, nothing blocked the PRs, and the blocking real-translation ratio gate
then failed on the release tip for everybody (pt-BR 3.2 % > 2.5 % + 0.5). A marker is now judged
as an absent translation. Fix a red with
as an absent translation. Release mode only since 2026-11-13: a feature PR sees
`SKIP reason=pr-mode`, and on the release PR (`BASE_REF=origin/main`) the gate judges every key
the cycle added. Fix a red in the release refresh or a translation wave with
`node scripts/i18n/sync-ui-keys.mjs --locale=<codes> --translate-markers --batch-size=40`, or
all locales in parallel with `npm run i18n:translate-new-keys` (`scripts/i18n/translate-new-keys.sh`,
detached-safe, refuses to start without the `OMNIROUTE_TRANSLATION_*` env). A key that must stay
| `PROVIDER_REFERENCE.md` | **Auto-generated** catalog of 393 providers (regen: `npm run gen:provider-reference`) |
| `PROVIDER_REFERENCE.md` | **Auto-generated** catalog of 394 providers (regen: `npm run gen:provider-reference`) |
### Subsystem deep-dives
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.