Files
OmniRoute/docs
Markus Hartung 0ff7d88869 fix(i18n): restore Google Translate codes in the locale table; guard the id←in alias in config-reading tests
Regenerating the "Supported Locales" table from config/i18n.json filled the
4th column with the locale code, overwriting four verified-correct values.
Restored from `googleTl` in scripts/i18n/generate-multilang.mjs: `he` → `iw`,
`phi` → `tl`, `pt-BR` → `pt`, `uk-UA` → `uk`. The other 38 rows were checked
against the same source and already agreed; the header text, the column
widths and every other cell are untouched, so `insertI18nGuideRow`'s anchor
keeps working (add-locale --dry-run exits 0 and still inserts `el` in place).

The `id` → `in` alias is the sole reason retiring a shipped locale is safe,
but unlike its three siblings it had no config-reading regression guard:

- tests/unit/i18n-config.test.ts pins LOCALE_ALIASES["id"] alongside uk-UA,
  phi and zh-TW.
- tests/unit/cli-i18n-catalog.test.ts covers OMNIROUTE_LANG=in → id in the
  existing config-alias test.
- tests/unit/i18n-resolve-requested-locale.test.ts adds one case built on the
  real LOCALES/LOCALE_ALIASES from src/i18n/config.ts (the existing fixture
  tests stay), asserting a saved NEXT_LOCALE=in cookie still lands on `id`.

All three fail when the alias is removed from config/i18n.json (verified).

Also: the "docs/i18n/README.md Is Auto-Generated" note no longer claims the
index is regenerated by `generate-multilang.mjs docs` — it is maintained by
`npm run i18n:add-locale` (row insertion) and by hand otherwise.
2026-09-02 11:09:58 -03:00
..
2026-06-29 08:40:06 -03:00

title, version, lastUpdated
title version lastUpdated
OmniRoute Documentation 3.8.40 2026-06-28

OmniRoute Documentation

Navigable index of the OmniRoute documentation set. Topics are grouped by intent so you can find what you need quickly.

Looking for the project overview, install steps, or release notes? See the root README.md, ROADMAP.md, CHANGELOG.md, and CONTRIBUTING.md.


For Non-Tech Users

Simple guides for using OmniRoute — no technical background needed.

getting-started/

guides/


For Tech Users

Technical documentation for developers and contributors.

architecture/

How the system is put together — read these to understand the runtime, code layout, and resilience model.

reference/

Lookup material — API surface, environment variables, CLI flags, provider catalog.

frameworks/

Pluggable subsystems exposed to clients, agents, and operators.

routing/

Combo routing, scoring, and replay.

security/

Guardrails, compliance, stealth, and the mandatory patterns for handling public credentials and error messages.

compression/

Prompt compression engines, rules, and language packs.

providers/

Provider-specific integration guides.

comparison/

ops/

Release, deployment, proxies, tunnels, coverage, database, monitoring.

diagrams/

Mermaid sources and exported SVG/PNG diagrams referenced from the docs above. See diagrams/README.md.

i18n/

Translated mirrors of the documentation in 41 locales (plus the English originals — 42 languages in total). See i18n/README.md for the supported language list.

screenshots/

Static screenshots used by the dashboard and the README. Not part of the doc body.


Auto-generated artifacts

  • reference/PROVIDER_REFERENCE.md is generated by scripts/docs/gen-provider-reference.ts from src/shared/constants/providers.ts. Do not edit by hand.
  • The /docs UI is backed by Fumadocs MDX source generation from the subfolders above.