Compare commits

..

222 Commits

Author SHA1 Message Date
diegosouzapw
6441b5b6f3 Merge remote-tracking branch 'origin/release/v3.8.55' into fix/codeql-redos-model-ids
# Conflicts:
#	open-sse/executors/context7-fetch.ts
#	src/shared/utils/modelDisplayName.ts
#	src/sse/services/githubResponsesFallback.ts
2026-11-21 00:23:19 -03:00
Diego Rodrigues de Sa e Souza
696498a972 Merge pull request #20775 from cheaper-inference/fix/plugin-marketplace-auth-config-schema
fix(security): require credential for marketplace install and restrict plugin config keys
2026-11-21 00:21:08 -03:00
Diego Rodrigues de Sa e Souza
4d76573bb1 Merge pull request #20770 from cheaper-inference/fix/om-usage-text-account-scope
fix(security): limit the usage command text to the personal quota for client keys
2026-11-21 00:21:01 -03:00
Diego Rodrigues de Sa e Souza
b748429cf5 Merge pull request #20839 from cheaper-inference/fix/qg-v3855-codeql-parsers-186db2-20261120
fix(security): make model and compression parsing linear
2026-11-20 23:01:11 -03:00
Diego Rodrigues de Sa e Souza
fa2199bde7 Merge branch 'release/v3.8.55' into fix/qg-v3855-codeql-parsers-186db2-20261120 2026-11-20 21:29:04 -03:00
Diego Rodrigues de Sa e Souza
355eb07c36 Merge pull request #18795 from cheaper-inference/chore/i18n-mirror-refresh
docs(i18n): refresh drifted mirrors (scheduled)
2026-11-20 21:27:54 -03:00
Diego Rodrigues de Sa e Souza
6f3b810297 Merge branch 'release/v3.8.55' into chore/i18n-mirror-refresh 2026-11-20 20:07:54 -03:00
diegosouzapw
1bc776ea6c fix(security): make model and compression parsing linear 2026-11-20 20:07:14 -03:00
serenity
186db2e375 fix(usage): late rows in purged rollups, locked-write retry and one-transaction XP (#20226)
* fix(gamification): commit one XP award as a single transaction

An authenticated request ran six autocommit statements per award: addXp inserted
xp_audit_log and upserted xp_action_counts and user_levels, then
updateRewardScores upserted leaderboard for global, weekly and monthly. Each took
the writer lock and its own commit, and a failure between them left XP without a
score or the reverse.

awardXp wraps addXp and the leaderboard upserts in one db.transaction.
emitGamificationEvent and the bonus-XP path (streak_bonus, badge_unlock) use it,
and the leaderboard credit now follows the award directly. Anti-cheat still runs
before any write; the lifetime action counter, one-time badge and streak-bonus
guards, tokens_shared scope and score values are unchanged. No setting or
delayed batch is added, so no award can be lost on shutdown.

Finding: ordata-48.
(cherry picked from commit a6517e5416cfbbb8e692767e68b0548dce931369)

* perf(db): compute the migration 044 key backfill once per connection

The old statement ran two correlated GROUP BY / ORDER BY subqueries for every
usage_history row that missed api_key_name, so the cost was the missing rows
times the history of their connection. The most used name and id of each
connection now go into two temp tables once, and the update joins them. The
values filled are the same: the most used non-empty value wins, a count tie
goes to the greater value, name and id are picked independently, a row with no
connection is not touched, and an unknown connection stays empty. Only installs
that have not run 044 yet see the change.

Finding: ordata-92.
(cherry picked from commit cb61850859b9e571c6cfbc6471349bdbb0048f54)

* fix(usage): retry a locked usage write on a backoff before dropping the row

A usage row that met a locked database was retried once after 1 s, then
dropped with one console.error. The 2 s busy timeout is not waited on the
first attempt, so a second writer process (CLI, desktop host) that holds the
lock for a few seconds lost the billing row.

The usage writer now retries on a 1, 2, 4, 8, 16 s backoff (about 31 s in
all), off the request path as before. Non-lock errors are still logged at
once and never retried. The generic one-retry scheduler used by call logs
and proxy logs is unchanged.

Finding: sub2api-86
(cherry picked from commit 93dd20bdd69b5cc23d836575c93c03172edca1f8)

* fix(quota): a stale exhausted sample with no reset no longer pauses an account

An exhausted quota window that carries no future reset time and was last seen
more than 2 hours ago now reads as unknown, not as reached. A paused account
receives no fresh quota headers, so one old sample kept it paused forever.
A window with a future reset still pauses until that reset, and a window seen
within 2 hours still pauses.

Finding: sub2api-43.
(cherry picked from commit e0b51b8052e42e475e8554d904b3f96223f181a1)

* fix(usage): add a late row to a purged day's rollup instead of replacing it

The retention job rolls usage_history up into daily_usage_summary, then deletes
whole days. The next rollup replaced a day's summary with the raw rows it still
found, so one row that arrived late for a purged day erased that day's earlier
totals (3 requests became 1 in the probe).

The purge now records the day it reached and the highest row id at that time in
one key_value row (no migration). A row below that day with a higher id is late:
the rollup adds it to the day's summary and moves the recorded id forward in the
same transaction. A second rollup that read the same rows finds the mark changed,
rolls back, and reports an error, so the caller keeps its raw rows. Days that are
not purged yet are still recomputed from their raw rows.

Finding: sub2api-82.
(cherry picked from commit 449f4f3b10f117e2e25716abd302ee0641949968)

* chore(changelog): name the new fragments 0000-<slug> for the publisher

* refactor(db): move the usage purge day recording into two helpers

The late-row member adds a branch and a transaction to deleteWholeDaysBefore.
That raises its cognitive complexity from 0 to 1 over the base. Two small helpers
keep the function at its old complexity. No behaviour change.

* docs(changelog): number the fragment (#20226)

* chore: drop derived values the release refresh now owns

Plan 2026-11-13 (derived numbers resolved only at release): feature PRs no longer write values
that depend on the state of the base. This commit restores the lines this PR changed only to
update such values (counts in docs, the llm.txt mirrors, the Stryker test list, the package
description, counts in agent-instruction files) to the text of the PR's merge base, so merging
the current base brings the values `npm run release:refresh-derived` maintains. Every other
change of the PR is untouched.

* test(usage): stop waiting for a MockTimers warning newer Node versions never emit

The retry test waited at the top level for the experimental-feature
warning that the first mock.timers.enable() prints, so a later test that
counts console.error lines would not see it. Node 24 (the CI runtime) no
longer emits that warning, so the wait never settled and the runner
failed the whole file with 'unsettled top-level await'. Wait one
macrotask instead: on versions that still warn, the warning (queued on
process.nextTick) has passed by then; on versions that do not, the wait
ends at once.

* revert(quota): drop the stale-sample no-pause fix from this bundle

Reverts 9a2da1815d (fix(quota): a stale exhausted sample with no reset no
longer pauses an account), with its changelog fragment and test.

Replaced by a separate PR with a per-session/opt-in design (see the PR list); dropped here so the two do not conflict.

* fix(usage): bound late rows to the read max id and check the purge mark on every rollup write

- The late-row branch of the rollup SELECT is bounded by the MAX(id) it read,
  so a row another process commits between the two reads waits for the next
  run instead of being counted now and again after the mark moves to maxId.
- A rollup transaction that only replaces summaries now checks the purge mark
  it classified the days with and rolls back when a purge or a late-row add
  moved it, so a stale read cannot overwrite a day that gained late rows.

* revert(db): drop the migration 044 backfill rewrite from this PR

044 is a merged migration: databases that already recorded it never run the new SQL, and a merged migration keeps its content. Removes the SQL change, its changelog fragment and its test, as the maintainer asked. The other changes in this PR are unchanged.

---------

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
2026-11-20 19:57:56 -03:00
Diego Rodrigues de Sa e Souza
b254710df1 Merge pull request #20817 from cheaper-inference/fix/merge-train-contrib-d-20261120
chore(release): contributor train d of 3 PRs for v3.8.55 (2026-11-20)
2026-11-20 19:47:36 -03:00
Diego Rodrigues de Sa e Souza
baabf7b423 Merge pull request #20785 from cheaper-inference/fix/merge-train-rafa55-c-20261120
chore(release): contributor train c of 10 PRs for v3.8.55 (2026-11-20)
2026-11-20 19:47:08 -03:00
diegosouzapw
707b0f9757 Merge commit '8dd7157b8c0bf2d578ef81f78f1dbbb284836a2f' into docs/qg-v3855-writer-missing-mirrors-20261120 2026-11-20 19:01:16 -03:00
Diego Rodrigues de Sa e Souza
8dd7157b8c Merge pull request #20699 from cheaper-inference/fix/qg-v3855-v8-shard-evidence-20261118
fix(ci): bind V8 coverage to exact shard evidence
2026-11-20 19:00:16 -03:00
diegosouzapw
492d650774 Merge remote-tracking branch 'origin/release/v3.8.55' into fix/plugin-marketplace-auth-config-schema 2026-11-20 18:46:39 -03:00
diegosouzapw
f866adce29 Merge remote-tracking branch 'origin/release/v3.8.55' into fix/om-usage-text-account-scope 2026-11-20 18:46:08 -03:00
diegosouzapw
b03f265540 chore(changelog): number the fragment for #20823 2026-11-20 18:30:47 -03:00
diegosouzapw
909af20270 fix(security): linear model id regexes (CodeQL #1325, #1324, #1296)
Rewrite three regexes that backtracked in O(n^2) on crafted ids with no length cap:
- githubResponsesFallback: /^(?:.*codex.*|gpt-(?:[6-9]|5\.[5-9]).*)$/i becomes a codex
  substring check, an anchored gpt prefix check and an explicit line-terminator reject.
- modelDisplayName VERSION_MARKER: /^v\d+([.\d]*)$/i becomes /^v\d[.\d]*$/i.
- isValidContext7LibraryId: /^\/(.+)\/(.+)$/ becomes /^\/([^/]+)\/([^/]+)$/.

A truth table generated from the base versions is pinned in the new test and passes
unchanged; 50k-char pathological ids now return in milliseconds.
2026-11-20 18:22:39 -03:00
diegosouzapw
c0a9ad1553 Merge #19665 (head 10cff9e8) into contributor train d 2026-11-20 18:04:33 -03:00
diegosouzapw
2d62d6440f Merge #20084 (head 2f6bdc59) into contributor train d 2026-11-20 18:04:26 -03:00
diegosouzapw
bdf1b3248a Merge #20113 (head 1a0c5a69) into contributor train d 2026-11-20 18:04:21 -03:00
diegosouzapw
b2e85375e7 Merge release/v3.8.55 into contributor train c 2026-11-20 18:00:10 -03:00
diegosouzapw
a05f32a9a1 docs(i18n): restore reviewed release gate mirrors 2026-11-20 17:51:17 -03:00
diegosouzapw
bbf2ced076 chore(ci): rebind V8 coverage evidence to the current release 2026-11-20 17:31:49 -03:00
Diego Rodrigues de Sa e Souza
a61261846f Merge pull request #20795 from cheaper-inference/chore/codeql-baseline-2-27-5
chore(quality): temporary codeqlAlerts ceiling for the CodeQL 2.27.5 upgrade
2026-11-20 17:24:27 -03:00
github-actions[bot]
42f63d548f docs(i18n): refresh drifted mirrors (scheduled)
Engine: google. Sources: docs/architecture/QUALITY_GATES.md, docs/ops/BRANCHING_MODEL.md, docs/ops/MERGE_TRAIN.md, docs/ops/RELEASE_CHECKLIST.md, docs/ops/RUNNER_BOX.md. 299 mirror file(s). 31 unit(s) failed and were left as they were.

Run: https://github.com/cheaper-inference/OmniRoute/actions/runs/44793361106
2026-11-20 18:36:39 +00:00
diegosouzapw
1ec3442acc chore(quality): temporary codeqlAlerts ceiling for the CodeQL 2.27.5 upgrade
The default setup moved CodeQL 2.27.4 -> 2.27.5 on 2026-11-20; the release/v3.8.55 JS analysis went 236 -> 339 results with the same 87 rules and no code change, opening 101 alerts at once and failing the codeql ratchet on every PR. Owner-authorized temporary ceiling 6 -> 103 while the security wave triages them; a follow-up lowers it to the measured count.
2026-11-20 13:12:41 -03:00
diegosouzapw
c68f193075 fix(ci): reconcile V8 coverage with Sonar LCOV 2026-11-20 12:39:28 -03:00
Diego Rodrigues de Sa e Souza
07a790f5c1 fix(ci): give the SonarQube scan coverage/lcov.info on pull requests (#20769)
#18336 dropped the lcov reporter from the coverage merge on pull_request while SonarQube was off; once vars.SONARQUBE_ENABLED came back, the scan found no coverage/lcov.info and every PR showed 0.0% coverage on new code. The merge step now writes lcov on a PR when SonarQube is enabled (measured cost: none beyond runner variance), and the sonarqube job fails before the scan when the file is missing. Closes #20725.
2026-11-20 12:12:03 -03:00
diegosouzapw
10cff9e8ca fix(providers): send a numeric Firecrawl wait as the v2 waitFor delay
On the Firecrawl cloud endpoint, a wait_for_selector that is a plain
non-negative integer is now sent as the v2 waitFor delay in milliseconds,
capped at the v2 limit of 60000. Any other value still goes through the
wait action as a CSS selector. Self-hosted base URLs keep the v1 body.

The mapping moves into applyWaitForSelector() so firecrawlFetch does not
grow. Adds the changelog fragment for the v2 scrape migration (#19636).

Grafted from #19799 (numeric waitFor handling and changelog entry), with
the integer-only rule and the 60000 ms clamp from the review.

Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
2026-11-20 11:34:24 -03:00
diegosouzapw
aee0423c29 Merge #20071 (head c594cca6) into rafacpti23 train c 2026-11-20 11:30:10 -03:00
diegosouzapw
67e2b79aa3 Merge #19851 (head 10e1d1be) into rafacpti23 train c 2026-11-20 11:30:03 -03:00
diegosouzapw
c80b0c1b24 Merge #20463 (head d62a0ce8) into rafacpti23 train c 2026-11-20 11:29:58 -03:00
diegosouzapw
b47c4dec93 Merge #20304 (head c09c6f52) into rafacpti23 train c 2026-11-20 11:29:54 -03:00
diegosouzapw
343003808d Merge #20272 (head 3d4ab0b2) into rafacpti23 train c 2026-11-20 11:29:49 -03:00
diegosouzapw
9fef1327bc Merge #20255 (head a05328b9) into rafacpti23 train c 2026-11-20 11:29:47 -03:00
diegosouzapw
bdd89f3b36 Merge #20248 (head 63407581) into rafacpti23 train c 2026-11-20 11:29:44 -03:00
diegosouzapw
14a323a3b8 Merge #19916 (head 36c01108) into rafacpti23 train c 2026-11-20 11:29:39 -03:00
diegosouzapw
32ba6215a7 Merge #19812 (head a2ecc101) into rafacpti23 train c 2026-11-20 11:29:36 -03:00
diegosouzapw
526a4387ad Merge #19807 (head 8761f1c7) into rafacpti23 train c 2026-11-20 11:29:32 -03:00
diegosouzapw
8d4ae3e0ec Merge release/v3.8.55 into fix/firecrawl-v2-scrape 2026-11-20 11:28:21 -03:00
Diego Rodrigues de Sa e Souza
3833e42097 Merge branch 'release/v3.8.55' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-20 11:10:20 -03:00
Diego Rodrigues de Sa e Souza
760357c44a Merge pull request #20772 from cheaper-inference/fix/release-v3.8.55-basereds-20771-combo-timeout
test(ci): stabilize combo target timeout on v3.8.55
2026-11-20 11:06:51 -03:00
diegosouzapw
347fa663eb chore(changelog): name the fragment after PR #20775 2026-11-20 10:23:56 -03:00
diegosouzapw
3924a54945 test(ci): make combo target timeout assertion deterministic 2026-11-20 09:44:38 -03:00
diegosouzapw
dc51d9ddad chore(changelog): name the om-usage text fragment after PR #20770 2026-11-20 09:10:59 -03:00
diegosouzapw
2f6bdc590a Merge release/v3.8.55 into fix/excluded-lockout-retry-after 2026-11-20 09:07:21 -03:00
diegosouzapw
5920565793 fix(security): require credential for marketplace install and restrict plugin config keys
POST /api/plugins/marketplace/install downloads plugin code and may activate it,
so it now requires the management credential in every auth mode
(alwaysRequireAuth), like POST /api/plugins.

PUT /api/plugins/[name]/config now validates the body with
validatePluginConfig(): only keys declared in the plugin's configSchema are
stored, with type, range and enum checks. A plugin without a configSchema has
no configurable keys, so the write is refused with a fixed 400 and nothing is
stored.
2026-11-20 09:00:30 -03:00
diegosouzapw
7415ccd084 fix(sse): skip an excluded account in an account cooldown when reporting a model cooldown
Exclusion is decided before the account-cooldown check, so an account that
the fallback loop just excluded could turn its short model lockout into the
reported model cooldown even while the account itself was cooling down for
much longer, and the caller would retry too early. Count an excluded account
only when it is not in an account cooldown, with the regression test from
#20249.

Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
2026-11-20 08:56:29 -03:00
Diego Rodrigues de Sa e Souza
8f56803041 chore(ci): retire the Mergify merge queue (#20616)
* chore(ci): retire the Mergify merge queue

The owner retired Mergify from the merge process on 2026-11-19.

- .mergify.yml: drop the release and relay-integration queue rules and
  the queue-label cleanup rule; keep the file with commands_restrictions
  that refuse every Mergify command that merges or rewrites a PR, since
  with no configuration Mergify's implicit queue still merges on
  @mergifyio queue.
- dry-run-lts-cut G11 now checks omni-queue: valid config at the source,
  bases managing the release branch, mode live, label present.
- Dated notes on the Mergify-era docs; G11 rows updated.

* docs(changelog): add the fragment for the Mergify retirement (#20616)

* chore(quality): record the retired Mergify contract in the test-masking allowlist (#20616)
2026-11-20 08:53:41 -03:00
Diego Rodrigues de Sa e Souza
0c9e0356f9 fix(release): sync-next-cycle opens a PR instead of pushing to the release branch (#20645)
* fix(release): sync-next-cycle opens a PR instead of pushing to the release branch

release/vX+1 is the default branch and ruleset 21899981 (Require PR on
default branch, no bypass actors) refuses a direct push, so the final
push of the sync-back could never land. The script now pushes the merge
commit to chore/sync-back-main-<sha12> and opens a PR into the release
branch; it never merges it. Re-running after the side branch reached
origin prints the open PR (or opens it) and stops. The old push stays
behind --direct-push (off by default). The sync worktree is detached at
origin/<branch>, so the merge commit never moves a local release branch
ref. The release-green gate and --skip-green-gate are unchanged.

* docs(changelog): add the fragment for #20645

* test(release): compare the sync-back next-steps line exactly (#20645)
2026-11-20 08:50:19 -03:00
diegosouzapw
5855af6172 Merge release/v3.8.55 into fix/excluded-lockout-retry-after 2026-11-20 08:44:10 -03:00
diegosouzapw
9e4dfa1411 fix(security): limit the usage command text to the personal quota for client keys
The text form of the usage command (@@om-usage and the plain
/api/usage/om-usage) now applies the same account rule as the JSON form:
a key without self:account-quota or a management scope sees only its
personal quota, and the shared provider accounts are not read for it.
Keys with self:account-quota, management keys and the environment key
keep the provider quota.
2026-11-20 08:43:56 -03:00
diegosouzapw
cf8baca2eb Merge commit '632d84f569f72893ed148e5b19dd05e2fff1a52a' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-20 08:22:25 -03:00
diegosouzapw
24e8074019 perf(ci): index native coverage by script URL 2026-11-20 08:22:07 -03:00
Diego Rodrigues de Sa e Souza
632d84f569 Merge pull request #20718 from cheaper-inference/chore/derived-refresh
chore(docs): refresh derived numbers on release/v3.8.55
2026-11-20 07:30:23 -03:00
diegosouzapw
ded34718eb Merge commit 'e7d83333dc09fc433af0bc2dc72d0268120f8018' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-20 06:38:38 -03:00
diegosouzapw
c8c3c306b5 fix(ci): inventory incompatible V8 source layouts before rejection
Use the proven failure-only diagnostics without changing coverage admission.
2026-11-20 06:38:22 -03:00
diegosouzapw
fe99346fd5 test(ci): preload native V8 in the Radar export fixture
Port the exact fixture from main in 15ded9592 while preserving its deliberately isolated environment.
2026-11-20 06:34:52 -03:00
Diego Rodrigues de Sa e Souza
17eb087472 Merge branch 'release/v3.8.55' into chore/derived-refresh 2026-11-20 06:10:36 -03:00
Diego Rodrigues de Sa e Souza
e7d83333dc Merge pull request #20543 from cheaper-inference/fix/qg-v3855-proxy-cache-clock-20261118
test(proxy): control the negative cache clock
2026-11-20 06:08:34 -03:00
diegosouzapw
786f6b2318 test(ci): settle cold builds in model catalog route fixtures
Use the existing settlement only for verified build-timeout responses from the original Image and VS Code routes.
2026-11-20 06:01:06 -03:00
diegosouzapw
2c886cdf05 test(ci): accept the exact native coverage URL on Node 22
Port the single test correction from cd8749e407, preserving source identity and all counter assertions.
2026-11-20 05:55:42 -03:00
diegosouzapw
a9e2ba3459 Merge commit 'd1821d0db11dcfe92c2cde3629f06aabecc133dc' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-20 05:16:53 -03:00
diegosouzapw
8ce4563356 fix(ci): use native V8 coordinates for Node script modules
Port the exact main repair in 88ff9ef0c after confirming the source and consumers' test file identities.
2026-11-20 05:16:36 -03:00
diegosouzapw
cd90930aab test(ci): synchronize the OTLP retry timeout fixture
Bind cleanup of each timed-out request to the real collector seeing it before the next attempt.
2026-11-20 05:14:45 -03:00
Diego Rodrigues de Sa e Souza
c54281c65e Merge branch 'release/v3.8.55' into chore/derived-refresh 2026-11-20 04:53:56 -03:00
Diego Rodrigues de Sa e Souza
9f0fabf77c Merge branch 'release/v3.8.55' into fix/qg-v3855-proxy-cache-clock-20261118 2026-11-20 04:53:50 -03:00
Diego Rodrigues de Sa e Souza
d1821d0db1 Merge pull request #20750 from cheaper-inference/docs/i18n-packed-tarball-575c-20261120
docs(i18n): sync packed tarball environment mirrors
2026-11-20 04:52:56 -03:00
diegosouzapw
1b5dc9b650 Merge commit '6a5dadd172195d2e1b39c6904f8f12af32192c91' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-20 04:11:48 -03:00
diegosouzapw
f8ba9806fc fix(ci): preserve native coverage across exporter runner fixtures
Port the same exporter fixture options and test hook type used on main in caddd2bab3.
2026-11-20 04:11:06 -03:00
diegosouzapw
a6a6f0ca34 fix(ci): use native coverage in the extensibility export fixture
(cherry picked from commit d7abdfd827)
2026-11-20 04:10:21 -03:00
Diego Rodrigues de Sa e Souza
1413daeb0a Merge branch 'release/v3.8.55' into fix/qg-v3855-proxy-cache-clock-20261118 2026-11-20 04:08:19 -03:00
diegosouzapw
0b43316d9d Merge commit '6a5dadd172195d2e1b39c6904f8f12af32192c91' into docs/i18n-zh-tw-derived-v3855-e3c1531 2026-11-20 03:27:42 -03:00
diegosouzapw
7fa9592f49 Merge commit '6a5dadd172195d2e1b39c6904f8f12af32192c91' into docs/i18n-packed-tarball-575c-20261120 2026-11-20 03:27:39 -03:00
Diego Rodrigues de Sa e Souza
6a5dadd172 Merge pull request #20735 from cheaper-inference/fix/qg-queue-promisor-retry-20261120
fix(ci): retry a local promisor blob in Omni Queue
2026-11-20 03:25:50 -03:00
diegosouzapw
442a7c8da2 fix(ci): align doctor and catalog native V8 coverage 2026-11-20 03:08:14 -03:00
diegosouzapw
cd5cbe3ba3 Merge commit '4624250231f49ed118fb4522a9d735e4894322c6' into docs/i18n-zh-tw-derived-v3855-e3c1531 2026-11-20 02:22:53 -03:00
diegosouzapw
e16e33f874 Merge commit '4624250231f49ed118fb4522a9d735e4894322c6' into docs/i18n-packed-tarball-575c-20261120 2026-11-20 02:22:53 -03:00
diegosouzapw
72e9012e92 Merge commit '4624250231f49ed118fb4522a9d735e4894322c6' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-20 02:13:17 -03:00
diegosouzapw
e051b9fd66 test(ci): preserve source maps in isolated migration fixtures
(cherry picked from commit e09683bba3)
2026-11-20 02:11:41 -03:00
diegosouzapw
29dcc9115a test(ci): preserve V8 preload in the dashboard probe 2026-11-20 02:10:53 -03:00
Diego Rodrigues de Sa e Souza
9ef9cff64f Merge branch 'release/v3.8.55' into fix/qg-queue-promisor-retry-20261120 2026-11-20 01:57:14 -03:00
Diego Rodrigues de Sa e Souza
4624250231 test(combo): give the shared wait-allowance cases room to survive a stalled loop (#20740)
"different targets share the existing request wait allowance" had two timing
faults with ~110-320 ms of slack each:

- A wait is granted only when (cooldown end - now + 50 ms) <= maxWaitMs. With a
  480 ms cooldown and maxWaitMs 480, a stall that delayed the cooldown write until
  the reread made the first wait ~530 ms, so the first target stopped without
  spending the allowance and the second used it (200 !== 502).
- A stall after the write let the 480 ms cooldown lapse before the reread
  (~160 ms later), with the same result.

The cases now use a 2 s cooldown and, for the budget variant,
maxWaitMs = budgetMs = 2.6 s: any first wait fits (1.4-2.05 s under a 500 ms
stall on either side) and what is left never covers a second one.

Reproduced on the old file with injected stalls (250 ms before the write: the
budget variant fails; 520 ms after it: both fail) and passing on the new one in
all three conditions, together with control runs that give room for two waits
(default limits, and budgetMs 5.2 s): both targets then wait and the request
succeeds (200, four calls), so the 502 still comes from the shared limit.
Full file: 69/69.
2026-11-20 01:54:42 -03:00
diegosouzapw
8fab4e5025 Merge commit 'bd9b1324abb82f0e00066f631b6dd7744e5d975a' into docs/i18n-zh-tw-derived-v3855-e3c1531 2026-11-20 01:40:07 -03:00
diegosouzapw
1b9d8d081f Merge commit 'bd9b1324abb82f0e00066f631b6dd7744e5d975a' into docs/i18n-packed-tarball-575c-20261120 2026-11-20 01:31:15 -03:00
diegosouzapw
e64c56e67a Merge commit 'bd9b1324abb82f0e00066f631b6dd7744e5d975a' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-20 01:18:08 -03:00
Diego Rodrigues de Sa e Souza
bd9b1324ab Merge pull request #20704 from cheaper-inference/fix/qg-v3855-catalog-cold-fixtures-20261119
test(ci): stabilize release catalog, quota, and analytics fixtures
2026-11-20 01:17:17 -03:00
diegosouzapw
0fac8c6c7a fix(ci): exclude proven Node mock wrappers from V8 coverage 2026-11-20 01:09:12 -03:00
diegosouzapw
1a0c5a6902 Merge release/v3.8.55 into fix/dashboard-compact-counts-boundary-20068 2026-11-20 00:45:03 -03:00
diegosouzapw
3d4ab0b2ca chore(changelog): rename #20272 fragment to the <PR>-<slug>.md convention
The fragment was keyed by the issue number (20250-auggie-cli-quiet-flag.md);
changelog.d fragments are keyed by the PR number, so it becomes
20272-auggie-cli-quiet-flag.md with its content unchanged.

Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
2026-11-20 00:31:09 -03:00
diegosouzapw
13f40a68f6 Merge release/v3.8.55 into fix/auggie-cli-remove-quiet-20250 2026-11-20 00:28:29 -03:00
diegosouzapw
3cae2de0be docs(i18n): update packed tarball release checks 2026-11-20 00:26:37 -03:00
diegosouzapw
a2ecc10114 Merge release/v3.8.55 into fix/responses-compaction-chat-translation-19730 2026-11-20 00:20:53 -03:00
diegosouzapw
10e1d1be77 test(providers): drive the Cloudflare Workers AI Check button end to end (#19304)
The node tests in this PR exercise the request-body builder, the schema and
the validator directly; on the current base they pass because the fix (#19384)
is already merged. This jsdom test renders AddApiKeyModal for cloudflare-ai,
types an API key and an Account ID, clicks "Check" and asserts the request to
/api/providers/validate carries the trimmed accountId. It fails with the
#19384 change reverted (the body has no accountId) and passes with it.

The changelog fragment is renamed to the <PR>-<slug> convention and moved to
maintenance: the fix itself already has its entry under #19384, so this PR
only adds regression tests.

Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
2026-11-20 00:06:51 -03:00
Diego Rodrigues de Sa e Souza
a2484981de Merge branch 'release/v3.8.55' into fix/qg-v3855-catalog-cold-fixtures-20261119 2026-11-20 00:04:35 -03:00
Diego Rodrigues de Sa e Souza
89986ee091 Merge branch 'release/v3.8.55' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-20 00:04:33 -03:00
Diego Rodrigues de Sa e Souza
76829115cc Merge branch 'release/v3.8.55' into fix/qg-queue-promisor-retry-20261120 2026-11-20 00:04:31 -03:00
diegosouzapw
a05328b926 Merge release/v3.8.55 into fix/api-key-usage-limits-long-context-20153 2026-11-20 00:03:36 -03:00
diegosouzapw
c6c2ac2480 fix(i18n): translate strict chat history settings 2026-11-20 00:01:51 -03:00
diegosouzapw
7266f1dd4e Merge release/v3.8.55 into fix/cloudflare-workers-ai-validate-account-id-19304 2026-11-20 00:01:08 -03:00
diegosouzapw
c594cca68d Merge release/v3.8.55 into fix-model-display-name-dashed-date 2026-11-19 23:58:39 -03:00
diegosouzapw
d62a0ce8c2 Merge release/v3.8.55 into fix/call-log-worker-win32-file-url-20449 2026-11-19 23:58:39 -03:00
diegosouzapw
8c2b28e674 Merge commit '575c3d49c15b2ff444e39c83a6ee648f19a2923e' into docs/i18n-zh-tw-derived-v3855-e3c1531 2026-11-19 23:57:34 -03:00
diegosouzapw
700fcb22f2 test(sse): isolate Zed readiness classification from wall time 2026-11-19 23:32:20 -03:00
diegosouzapw
66da83b5af Merge commit '77470f3644d4b9cfe1f1ff6b31d8bcbee41bf16d' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-19 23:22:41 -03:00
diegosouzapw
51714c011f fix(ci): preserve native coverage in route memory profiling 2026-11-19 23:21:09 -03:00
diegosouzapw
a1ba41bdfc Merge commit '77470f3644d4b9cfe1f1ff6b31d8bcbee41bf16d' into fix/qg-queue-promisor-retry-20261120 2026-11-19 23:17:09 -03:00
diegosouzapw
55510c9da6 Merge commit '36d6c6a079edd14b0ba18971a5e593e0d2128799' into docs/i18n-zh-tw-derived-v3855-e3c1531 2026-11-19 23:14:59 -03:00
diegosouzapw
51dbcc9982 Merge commit '77470f3644d4b9cfe1f1ff6b31d8bcbee41bf16d' into docs/i18n-zh-tw-derived-v3855-e3c1531 2026-11-19 23:14:58 -03:00
Diego Rodrigues de Sa e Souza
c7276e07e8 Merge branch 'release/v3.8.55' into fix/qg-v3855-catalog-cold-fixtures-20261119 2026-11-19 23:14:19 -03:00
diegosouzapw
50ad62a9ad fix(ci): retain native coverage in shared boundary fixtures 2026-11-19 23:12:43 -03:00
diegosouzapw
5270afefcd fix(ci): preserve V8 layouts in isolated test subprocesses 2026-11-19 22:47:59 -03:00
github-actions[bot]
36d6c6a079 chore(docs): refresh derived numbers on release/v3.8.55
npm run release:refresh-derived -- --profile=nightly on release/v3.8.55: 132 file(s).

Run: https://github.com/cheaper-inference/OmniRoute/actions/runs/44655585758
2026-11-20 01:44:21 +00:00
diegosouzapw
4c3e2d997a fix(ci): retry stale promisor lookups in queue merges 2026-11-19 22:42:23 -03:00
diegosouzapw
5cf0c54eb6 fix(i18n): canonicalize UI and CLI catalog key order 2026-11-19 22:11:43 -03:00
diegosouzapw
04264cea50 Merge commit 'e3c1531afd07d5e06f7ffab658584a7ae2e3627e' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-19 21:48:57 -03:00
diegosouzapw
7dc9e0c806 fix(ci): resolve linked paths for the installed CLI coverage loader 2026-11-19 21:18:54 -03:00
diegosouzapw
2a8675603b fix(ci): preserve native coverage for the installed CLI fixture 2026-11-19 21:15:04 -03:00
diegosouzapw
6911667c26 fix(ci): share native coverage across CLI and tray loaders 2026-11-19 20:30:13 -03:00
diegosouzapw
9b4ca56549 Merge release/v3.8.55 into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-19 20:28:23 -03:00
diegosouzapw
85554d817e Merge commit 'ab180e32fcdf1f78c96f98a617e17c86e34bf5aa' into fix/qg-v3855-catalog-cold-fixtures-20261119 2026-11-19 20:15:36 -03:00
diegosouzapw
5f391e8bdd test(ui): wait for FAL recovery requests 2026-11-19 20:01:15 -03:00
diegosouzapw
f0eb387311 test(ci): distinguish quota limits from request IDs 2026-11-19 19:58:19 -03:00
diegosouzapw
1ebb33cc2f test(ci): verify scoped Codex quota observation timestamps 2026-11-19 19:58:18 -03:00
diegosouzapw
1068297dc2 fix(ci): align native media MCP coverage layout 2026-11-19 19:42:53 -03:00
diegosouzapw
761ca3ec7a Merge commit 'fbd339668384803bc3a9d42370fc413a55e013d5' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-19 19:24:59 -03:00
diegosouzapw
37391ca5c5 test(api): cover resolveModelDisplayName and namespaced ids for dashed release dates
Add the resolveModelDisplayName cases from #20114: an explicit name such as
"Custom Label" wins over a dated snapshot id, and the id passed as its own
name is still derived to "GPT-5". Also cover the namespaced
cmc/openai/gpt-4.1-2025-04-14 id.

Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
2026-11-19 19:19:08 -03:00
diegosouzapw
8989742a3e Merge release/v3.8.55 into fix-model-display-name-dashed-date 2026-11-19 19:12:10 -03:00
diegosouzapw
bdda4c2e0f fix(ci): preserve the native layout in CLI coverage 2026-11-19 19:09:30 -03:00
Diego Rodrigues de Sa e Souza
feb48ab330 Merge branch 'release/v3.8.55' into fix/qg-v3855-catalog-cold-fixtures-20261119 2026-11-19 19:00:02 -03:00
diegosouzapw
3735aa9304 Merge release/v3.8.55 into fix/excluded-lockout-retry-after 2026-11-19 18:53:37 -03:00
diegosouzapw
ef66a01c52 test(db): await API key import fixture worker exit 2026-11-19 18:37:33 -03:00
diegosouzapw
a1d3298bb8 Merge commit '160dfbc5506e15789114a46452d510565ac1bdd2' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-19 18:36:58 -03:00
diegosouzapw
729f8c44cc test(callLogs): prove an unusable module URL never resolves this tree's own worker (#20449)
The existing #20449 case passes on the base too: the entry-relative worker is
found before any module-relative candidate, so the guard is never exercised.
This case leaves only a cwd-relative TypeScript worker, so the base (which
ignores moduleUrl and keeps using the real module directory) returns the
source tree's worker, while the fix skips every module-relative candidate and
probes only the cwd layout.

Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
2026-11-19 18:35:45 -03:00
diegosouzapw
4e34224ba7 chore(changelog): rename #20255 fragment to the <PR>-<slug>.md convention
The fragment was named api-key-usage-limits-long-context-20153.md;
changelog.d fragments are keyed by the PR number first, so it becomes
20255-api-key-usage-limits-long-context.md with its content unchanged.

Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
2026-11-19 18:35:28 -03:00
diegosouzapw
36c01108d8 test(auto-combo): give the #19881 ReDoS timing tests a 2 s budget
The five wall-clock assertions used a 250 ms budget, which a loaded CI runner
can exceed even with the linear fix. The pre-fix regexes take tens of seconds
on the same inputs, so a shared 2 s budget still fails on the old code and
passes on the fix. Also names the changelog fragment after PR #19916, as
changelog.d/README.md asks.
2026-11-19 18:34:53 -03:00
diegosouzapw
15ea600082 Merge release/v3.8.55 into fix/api-key-usage-limits-long-context-20153 2026-11-19 18:34:09 -03:00
diegosouzapw
2ae6770fb5 Merge release/v3.8.55 into fix/call-log-worker-win32-file-url-20449 2026-11-19 18:33:52 -03:00
diegosouzapw
295a31a8a6 Merge release/v3.8.55 into fix/specificity-rules-redos-19881 2026-11-19 18:33:34 -03:00
diegosouzapw
c09c6f524e Merge release/v3.8.55 into feat/task-aware-routing-model-scoping-20294 2026-11-19 18:31:19 -03:00
diegosouzapw
1339e147b2 fix(ci): identify incomplete V8 producer inputs 2026-11-19 18:23:56 -03:00
diegosouzapw
e97f95598d test(ci): align Codex lifecycle child coverage layout 2026-11-19 18:22:06 -03:00
diegosouzapw
1a81ed6664 chore(changelog): name the fragment after PR #19812
changelog.d/README.md asks for <PR-number>-<slug>.md; the fragment carried the
issue number (#19730). Content unchanged.
2026-11-19 18:07:31 -03:00
diegosouzapw
b29692f9b5 Merge release/v3.8.55 into fix/responses-compaction-chat-translation-19730 2026-11-19 18:05:24 -03:00
diegosouzapw
16f070422d test(routing): pin unchanged task-aware routing when no model scope is set (#20294)
Guards the opt-in contract of targetModels/excludedModels: with both lists unset
or empty, every model is still routed by task type and counted in the stats,
and a persisted config written before #20294 (no scoping keys) hydrates without
adding a scope.

Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
2026-11-19 18:04:44 -03:00
diegosouzapw
63407581f7 chore(changelog): rename #20248 fragment to the <PR>-<slug>.md convention
The fragment was named cursor-grok-47-standard-speed-20077.md; changelog.d
fragments are keyed by the PR number first, so it becomes
20248-cursor-grok-47-standard-speed.md with its content unchanged.

Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
2026-11-19 18:02:49 -03:00
diegosouzapw
d0b69c4548 Merge release/v3.8.55 into fix/cursor-grok-47-standard-speed-20077 2026-11-19 17:58:00 -03:00
diegosouzapw
f7dc55db50 Merge release/v3.8.55 into feat/task-aware-routing-model-scoping-20294 2026-11-19 17:48:35 -03:00
diegosouzapw
8761f1c70d chore(changelog): name the fragment after PR #19807
changelog.d/README.md asks for <PR-number>-<slug>.md; the fragment carried the
issue number (#19805). Content unchanged.
2026-11-19 17:35:26 -03:00
Diego Rodrigues de Sa e Souza
e66081afa8 Merge branch 'release/v3.8.55' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-19 17:33:09 -03:00
diegosouzapw
3bd1513ffd Merge release/v3.8.55 into fix/gemini-planning-leak-multi-key-19805 2026-11-19 17:32:52 -03:00
diegosouzapw
aef7582cb6 test(ci): stabilize catalog authorization inventory fixture 2026-11-19 17:23:56 -03:00
diegosouzapw
656cc74c13 Merge commit 'f05732fbfbbf9468a714cf743b5746868032b854' into fix/qg-v3855-catalog-cold-fixtures-20261119 2026-11-19 17:23:31 -03:00
diegosouzapw
039a8807ef test(sse): cover the excluded-account lockout through excludeConnectionIds and add the changelog fragment
The fallback loop can also pass the account that just failed through the
excludeConnectionIds array option, not only the positional argument. Add a
test for that entry point (adapted from #20249, which used the option name
excludedConnectionIds that getProviderCredentials does not read), and add the
changelog fragment for #20083 based on the wording from #20249.

Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
2026-11-19 17:17:22 -03:00
diegosouzapw
a6c7a33067 test(integration): settle the catalog before checking the models route 2026-11-19 17:05:42 -03:00
diegosouzapw
21dc6e9918 Merge commit '6d87faf23640404336404dc101b74125be666258' into fix/qg-v3855-catalog-cold-fixtures-20261119 2026-11-19 17:05:23 -03:00
diegosouzapw
1a910ce4df chore(changelog): rename #20113 fragment to the <PR>-<slug>.md convention
The fragment was named dashboard-fmt-compact-boundary-20068.md; changelog.d
fragments are keyed by the PR number first, so it becomes
20113-dashboard-fmt-compact-boundary.md with its content unchanged.

Co-authored-by: Rafa Martins <rafacpti23@users.noreply.github.com>
2026-11-19 17:04:55 -03:00
diegosouzapw
d99569c275 Merge release/v3.8.55 into fix/excluded-lockout-retry-after 2026-11-19 17:03:39 -03:00
diegosouzapw
4f59754077 Merge release/v3.8.55 into fix/dashboard-compact-counts-boundary-20068 2026-11-19 17:03:11 -03:00
diegosouzapw
fed5dbe257 fix(ci): validate equivalent V8 source-map aliases 2026-11-19 17:00:33 -03:00
diegosouzapw
251aa07308 Merge commit '6d87faf23640404336404dc101b74125be666258' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-19 16:58:22 -03:00
diegosouzapw
98023ecaf9 test(ci): align permission and storage fixtures with coverage 2026-11-19 16:44:07 -03:00
diegosouzapw
a86a33f7fb Merge commit '7c7a369adf9417e152c5cf3f8db048b50d55106f' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-19 16:43:22 -03:00
Diego Rodrigues de Sa e Souza
472a3db39e Merge branch 'release/v3.8.55' into fix/qg-v3855-catalog-cold-fixtures-20261119 2026-11-19 16:37:57 -03:00
diegosouzapw
f51e8cbdb3 test(ci): copy the coverage preload into migration scratch repos 2026-11-19 15:57:23 -03:00
diegosouzapw
092f58b8a5 test(ci): settle the catalog before checking CC-compatible fallbacks 2026-11-19 15:35:29 -03:00
diegosouzapw
f83a5f8ee5 test(ui): await the analytics cache table measurement 2026-11-19 15:27:50 -03:00
diegosouzapw
43a87fe979 test(quota): preserve cold import observations before request timing 2026-11-19 15:27:08 -03:00
diegosouzapw
10bcc437d9 Merge commit '1e6e8dfc21e5e30d9566e72116f853d63b43791e' into fix/qg-v3855-catalog-cold-fixtures-20261119 2026-11-19 15:26:33 -03:00
diegosouzapw
d28c7ccd0a Merge commit '1e6e8dfc21' into fix/qg-v3855-v8-shard-evidence-20261118 2026-11-19 15:23:52 -03:00
diegosouzapw
53ec1b6d67 test(ci): settle one catalog rebuild after invalidation 2026-11-19 15:13:40 -03:00
diegosouzapw
0c02884f2a fix(ci): bind V8 shard coverage to the producing checkout 2026-11-19 15:07:05 -03:00
diegosouzapw
b2bea5284b test(ci): settle the model catalog before checking listing and alias rules 2026-11-19 15:00:42 -03:00
diegosouzapw
cc7ba0e32c test(ci): settle the real catalog before checking combo vision 2026-11-19 15:00:20 -03:00
diegosouzapw
4f680fb550 test(ci): settle the real catalog before checking reasoning tiers 2026-11-19 15:00:01 -03:00
diegosouzapw
774d1f92f0 test(ci): settle cold model catalog fixtures before checking metadata 2026-11-19 14:59:40 -03:00
diegosouzapw
e10ab8d321 Merge remote-tracking branch 'origin/release/v3.8.55' into HEAD 2026-11-19 10:00:24 -03:00
Bojackduy
f9128a1ddb fix(sse): ignore an excluded account's lockout when its own quota is exhausted
Exclusion is decided before any quota check, so an excluded account whose
quota for the model is exhausted could still turn its short lockout into the
reported model cooldown, and the caller would retry too early. Count an
excluded account only when its quota still allows the model, with a
regression test where both accounts are exhausted.
2026-11-19 09:58:59 -03:00
diegosouzapw
17ad4dad93 Merge remote-tracking branch 'origin/release/v3.8.55' into HEAD 2026-11-19 09:14:05 -03:00
diegosouzapw
1b74852d79 Merge remote-tracking branch 'origin/release/v3.8.55' into HEAD 2026-11-19 07:14:49 -03:00
Rafa Martins
df06001d50 refactor(callLogs): split worker module-dir resolution into helpers
Keeps resolveCallLogArtifactWorker under the cyclomatic complexity cap
(15) flagged by the complexity-ratchets new-code gate; lookup order and
fallbacks are unchanged.
2026-11-19 07:05:56 -03:00
diegosouzapw
30d0dd7183 Merge remote-tracking branch 'origin/release/v3.8.55' into HEAD 2026-11-19 06:59:17 -03:00
diegosouzapw
618423e5df Merge remote-tracking branch 'origin/release/v3.8.55' into HEAD 2026-11-19 06:43:26 -03:00
diegosouzapw
8f3d93fbd0 Merge remote-tracking branch 'origin/release/v3.8.55' into HEAD 2026-11-19 03:10:08 -03:00
diegosouzapw
731e72aa3d Merge remote-tracking branch 'origin/release/v3.8.55' into HEAD 2026-11-19 03:07:12 -03:00
diegosouzapw
d8f3898a96 Merge commit 'cc59ad70b2e9a343f26860e0e040281cb433a37a' into fix/qg-v3855-proxy-cache-clock-20261118 2026-11-19 02:56:15 -03:00
Rafa Martins
09173e167c fix(routing): stop a scoped model id from matching a different model it prefixes
targetModels/excludedModels now cover the exact id plus its ":" variants
and "/" children, so scoping openai/gpt-4o no longer captures
openai/gpt-4o-mini (#20294).
2026-11-18 21:09:04 -03:00
diegosouzapw
e431f17823 Merge remote-tracking branch 'origin/release/v3.8.55' into HEAD 2026-11-18 21:05:15 -03:00
Rafa Martins
0aab5edeb4 fix(auto-combo): count code spans in linear time and stop whitespace backtracking (#19881)
The bounded `.{0,N}?` repeats still backtracked when a long whitespace run
followed SELECT, import or if (SELECT plus 140k spaces took ~2 s; if plus
140k spaces did not finish), and they stopped scoring valid spans longer
than the cap.

Count the import/SELECT/${} indicators with a linear scan that keeps the
old greedy one-per-line semantics, and make the if ... then condition start
at a non-space so no two whitespace quantifiers overlap. Each span indicator
is now asserted on its own, including spans past the old caps.
2026-11-18 20:52:11 -03:00
diegosouzapw
80645477f7 Merge remote-tracking branch 'origin/release/v3.8.55' into HEAD 2026-11-18 20:36:10 -03:00
Rafa Martins
e4de8175d9 fix(translator): keep compaction_trigger explicit and restore compaction text by role
- Reject `compaction_trigger` on Chat Completions targets again: Codex remote
  compaction v2 needs exactly one `compaction` output item, which a Chat upstream
  cannot return, so skipping the marker answered with an unusable normal turn
  (and a trigger-only input produced `messages: []`).
- Restore readable compaction items with role-aware text parts (`output_text`
  for assistant), so the Codex normalizer no longer forwards assistant history
  as `input_text`.
- Accept only non-blank string content or a non-empty part array, falling back
  to `text`; other shapes are no longer forwarded as Chat content.
- Split restoreReadableCompactionItem into helpers (complexity ratchet).

Refs #19730
2026-11-18 20:12:58 -03:00
diegosouzapw
7857556efe Merge remote-tracking branch 'origin/release/v3.8.55' into HEAD 2026-11-18 20:03:05 -03:00
diegosouzapw
31be32598e test(proxy): control the negative cache clock 2026-11-18 18:08:40 -03:00
diegosouzapw
ac67a3ab46 Merge release/v3.8.55 into fix/responses-compaction-chat-translation-19730 2026-11-18 15:22:49 -03:00
diegosouzapw
ded449ed40 Merge release/v3.8.55 into fix/gemini-planning-leak-multi-key-19805 2026-11-18 15:20:49 -03:00
diegosouzapw
fa5449e69d fix(ci): verify coverage shard transform provenance 2026-11-18 13:06:32 -03:00
Rafa Martins
b8e1b3e66c fix(callLogs): guard worker path resolution against cross-platform file URLs (#20449) 2026-11-17 23:36:30 -03:00
Rafa Martins
61704fba0a feat(routing): allow scoping task-aware routing to target and excluded models (#20294) 2026-11-15 18:58:51 -03:00
Rafa Martins
fe3f990f2a fix(providers): remove deprecated --quiet flag from Auggie CLI invocation (#20250) 2026-11-15 09:25:37 -03:00
Rafa Martins
9c286a536c fix(cursor): narrow standard Grok 4.7 speed handling to synthetic Cursor models (#20077) 2026-11-15 01:26:58 -03:00
Rafa Martins
bdee7aaff4 fix(backend): skip long-context tier on per-key USD usage limit window sums (#20153) 2026-11-15 01:17:13 -03:00
Rafa Martins
74a1ee515a fix(cursor): restrict grok 4.7 variant regex to cursor- prefixed models (#20077) 2026-11-15 00:41:58 -03:00
Rafa Martins
cc910531f4 fix(cursor): preserve Grok 4.7 standard speed across all non-fast variants (#20077) 2026-11-14 23:59:48 -03:00
Rafa Martins
22cf8baa1a refactor(providers): split consumePlanningLeak into small helpers
The multi-key and solitary-thought branches pushed consumePlanningLeak
over the cognitive-complexity limit (complexity-ratchets new-code 0 -> 1).
Extract classifyUnclosedObject, isSolitaryThought and
classifySolitaryThought; behavior is unchanged (the repeated top-level
comma check in the unclosed branch was already covered by the early
return).

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
2026-11-13 11:05:09 -03:00
diegosouzapw
2456ea6b6b Merge commit '2f2c1957638c59c9f846dc2775488871df28a123' into mb-rafa-20113 2026-11-13 09:43:42 -03:00
diegosouzapw
11352894d8 Merge commit '2f2c1957638c59c9f846dc2775488871df28a123' into mb-rafa-19851 2026-11-13 09:39:18 -03:00
diegosouzapw
bc75d0a683 Merge commit '2f2c1957638c59c9f846dc2775488871df28a123' into mb-rafa-19807 2026-11-13 09:34:40 -03:00
diegosouzapw
51ecc4669e Merge commit '2f2c1957638c59c9f846dc2775488871df28a123' into mb-rafa-19812 2026-11-13 09:31:26 -03:00
diegosouzapw
0c2266f51f Merge commit '2f2c1957638c59c9f846dc2775488871df28a123' into mb-rafa-19916 2026-11-13 09:23:36 -03:00
Rafa Martins
bfed0db59f test(providers): keep the #19304 regression tests on top of #19384
#19384 already landed the same accountId forwarding in the validate
request body, the Zod schema and the route. Merging the base made both
copies coexist (duplicate accountId keys in an object literal and in the
schema), so drop this branch's duplicates and keep the base code; the
regression tests pass against it unchanged.

Co-authored-by: diegosouzapw <8016841+diegosouzapw@users.noreply.github.com>
2026-11-13 08:55:55 -03:00
diegosouzapw
56b87f2dc3 Merge remote-tracking branch 'origin/release/v3.8.54' into mb-rafa-19851 2026-11-13 08:54:36 -03:00
Rafa Martins
3a0f1f9749 fix(dashboard): rollover compact counts at unit rounding boundaries (#20068) 2026-11-12 21:44:19 -03:00
Bojackduy
30a0c10e04 fix(sse): report the excluded account's short lockout as a model cooldown
During fallback, the account that just failed is excluded from the retry and
tagged "excluded", so the #18664 branch (which only checked "modelLocked")
skipped its short retryable lockout. When every other account was
quota-exhausted, the request was reported as "All <provider> accounts have
exhausted their quota" with a reset minutes or days away, and clients backed
off for that long although the healthy account recovered within seconds.

Also consider "excluded" connections in that branch. Excluded connections
without an active retryable lockout are still ignored.

Fixes #20083
2026-11-12 21:12:06 +07:00
Abelo9996
3c9fe154da chore(changelog): number fragment for #20071 2026-11-12 03:59:41 -05:00
Abelo9996
2fa8083b96 fix(api): drop dash-separated release dates from derived model display names 2026-11-12 03:56:58 -05:00
Minxi Hou
3e4bd8818e fix(providers): wait for the selector on a Firecrawl v2 scrape
v2 scrape reads waitFor as a millisecond delay, so the selector string cannot
go there. The v2 actions list has a wait step that blocks until a CSS selector
is visible, which is what the field meant. A self-hosted base URL still speaks
v1 and keeps the selector in waitFor.

Signed-off-by: Minxi Hou <houminxi@gmail.com>
2026-11-11 13:35:25 -05:00
Minxi Hou
ffdda1e5a2 fix(providers): move the Firecrawl scrape call to v2
Firecrawl shuts its v1 API down on 2026-12-10 and answers it with HTTP 410
after that. Search, map and credit usage already call v2. The page fetch and
the dashboard key probe were the two calls still posting to /v1/scrape.

The cloud host now posts to /v2/scrape. v2 scrape rejects maxDepth outright and
treats waitFor as a millisecond delay, so the depth and CSS selector fields
stay on our own request but are no longer forwarded to the cloud. A
self-hosted base URL still speaks v1, so it keeps /v1/scrape and both fields.

Fixes #19636

Signed-off-by: Minxi Hou <houminxi@gmail.com>
2026-11-11 13:35:25 -05:00
Rafa Martins
ce7fa60a99 fix(auto-combo): bound if...then reasoning depth regex pattern (#19881) 2026-11-11 13:13:28 -03:00
Rafa Martins
7e621d822d fix(auto-combo): eliminate quadratic backtracking in specificity regexes (#19881) 2026-11-11 11:25:45 -03:00
Rafa Martins
7ed996ee1d fix(providers): forward accountId to validation endpoint for Cloudflare Workers AI (#19304) 2026-11-11 01:22:05 -03:00
Rafa Martins
8ce5bd184b fix(translator): translate compaction items with content to Chat messages
Closes #19730
2026-11-10 20:32:48 -03:00
Rafa Martins
eab177cf7e fix(providers): preserve multi-key JSON and solitary thought objects in Gemini leak filter
Fixes #19805
2026-11-10 19:52:58 -03:00
720 changed files with 21322 additions and 14442 deletions

View File

@@ -38,6 +38,9 @@ env:
# system TLS). Belt-and-suspenders with tests/_setup/isolateDataDir.ts.
OMNIROUTE_SKIP_SYSTEM_TRUST: "1"
CI_NODE_VERSION: "24"
# The V8 manifests require the producer and aggregator to have the same Node
# patch. A floating major can resolve to different patch versions on runner caches.
CI_V8_NODE_VERSION: "24.22.3"
CI_NODE_24_VERSION: "24"
CI_NODE_26_VERSION: "26"
@@ -1172,7 +1175,7 @@ jobs:
- uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7
with:
package-manager-cache: false
node-version: ${{ env.CI_NODE_VERSION }}
node-version: ${{ env.CI_V8_NODE_VERSION }}
- uses: ./.github/actions/prepare-unit-storage
with:
cache: ${{ github.event_name == 'pull_request' }}
@@ -1192,6 +1195,7 @@ jobs:
- name: Unit tests (shard ${{ matrix.shard }}/8) with V8 coverage
env:
TEST_SHARD: ${{ matrix.shard }}/8
TMPDIR: ${{ runner.temp }}/v8-tsx-${{ github.run_id }}-${{ github.run_attempt }}-${{ matrix.shard }}
# NODE_OPTIONS (nao so o flag em test:unit:ci:shard) porque quem estoura o
# heap e o processo `c8` que embrulha a suite — ele agrega ~577 MB de JSON
# de cobertura bruta. Subir o teto so no node filho deixa o pai no default
@@ -1201,6 +1205,12 @@ jobs:
run: |
trap 'status=$?; { df -h "$GITHUB_WORKSPACE" "$RUNNER_TEMP"; du -sh coverage-shard; } || :; exit "$status"' EXIT
rm -rf coverage-shard coverage-shard-report
# Capture the transforms this producer actually executes; a reused or
# shared TSX cache cannot establish generated-layout provenance.
node scripts/ci/prepare-v8-coverage.mjs init-cache "$TMPDIR" "$TEST_SHARD" "$GITHUB_SHA" "$GITHUB_RUN_ID" "$GITHUB_RUN_ATTEMPT" "$GITHUB_WORKSPACE"
V8_CACHE_PRELOAD="$(node -p 'require("node:url").pathToFileURL(process.argv[1]).href' "$GITHUB_WORKSPACE/scripts/ci/atomic-tsx-cache.mjs")"
V8_NATIVE_PRELOAD="$(node -p 'require("node:url").pathToFileURL(process.argv[1]).href' "$GITHUB_WORKSPACE/scripts/ci/native-worker-v8-layout.mjs")"
OMNIROUTE_CI_SYNC_TSX_CACHE="$TMPDIR" NODE_OPTIONS="$NODE_OPTIONS --import=$V8_CACHE_PRELOAD --import=$V8_NATIVE_PRELOAD" \
npx c8 --merge-async \
--temp-directory=coverage-shard \
--reports-dir=coverage-shard-report \
@@ -1208,11 +1218,23 @@ jobs:
--exclude=tests/** \
--exclude=**/*.test.* \
npm run test:unit:ci:shard
- name: Upload raw shard coverage
if: always()
- name: Package successful shard coverage
env:
TEST_SHARD: ${{ matrix.shard }}/8
TMPDIR: ${{ runner.temp }}/v8-tsx-${{ github.run_id }}-${{ github.run_attempt }}-${{ matrix.shard }}
run: node scripts/ci/prepare-v8-coverage.mjs pack coverage-shard coverage-shard-upload "$TEST_SHARD" "$GITHUB_SHA" "$GITHUB_RUN_ID" "$GITHUB_RUN_ATTEMPT" "$GITHUB_WORKSPACE" "$TMPDIR"
- name: Upload complete shard coverage
uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7
with:
name: coverage-shard-${{ matrix.shard }}
name: coverage-shard-${{ github.run_attempt }}-${{ matrix.shard }}
path: coverage-shard-upload/
compression-level: 0
if-no-files-found: error
- name: Preserve raw coverage from failed shards
if: failure()
uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7
with:
name: failed-unit-coverage-${{ github.run_attempt }}-${{ matrix.shard }}
path: coverage-shard/*.json
if-no-files-found: error
@@ -1315,6 +1337,9 @@ jobs:
# the release gate can still exercise them via workflow_dispatch when needed).
test-coverage:
name: Coverage
permissions:
contents: read
actions: read
runs-on: ubuntu-latest
# 10min was sized before #7114 added the lcov reporter (Codecov/Sonar need it);
# merging 8 shard JSONs + text+json+lcov now takes ~10-12min — three consecutive
@@ -1354,41 +1379,47 @@ jobs:
- uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7
with:
package-manager-cache: false
node-version: ${{ env.CI_NODE_VERSION }}
node-version: ${{ env.CI_V8_NODE_VERSION }}
- uses: ./.github/actions/npm-ci-retry
with:
# PR acceleration is not release-candidate provenance.
cache: ${{ github.event_name == 'pull_request' }}
- name: Select coverage producers for this attempt
id: coverage_selection
env:
GITHUB_TOKEN: ${{ github.token }}
run: |
mkdir -p coverage
node scripts/ci/select-v8-coverage.mjs coverage/coverage-selection.json 8
- name: Download all shard coverage
uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8
with:
pattern: coverage-shard-*
artifact-ids: ${{ steps.coverage_selection.outputs.artifact_ids }}
path: coverage-shards/
merge-multiple: true
merge-multiple: false
- name: Merge + report + gate
# Merging 8 shards of raw v8 coverage is memory-heavy. `--merge-async`
# keeps the V8 coverage merge incremental instead of loading every raw
# JSON blob into one in-memory merge, which avoids Node heap OOMs.
# lcov only outside pull_request (2026-10-26): its sole consumer on a PR was the
# informational Codecov upload below (SonarQube is off: vars.SONARQUBE_ENABLED is
# unset), and the PR gate only needs the json/text summaries. The step took ~21 min
# on a measured PR against the org's 20-job hosted cap.
# Verify and merge each raw report in order without storing a second
# raw copy. c8 reads the aggregate for source mapping and reporting.
# lcov on a PR only when SonarQube runs (#20725). #18336 (2026-10-26) dropped it on
# pull_request because its only PR consumer was the informational Codecov upload while
# SonarQube was off; once vars.SONARQUBE_ENABLED came back the `sonarqube` job scanned
# with no coverage/lcov.info and every PR showed 0.0% coverage on new code. Without
# Sonar the PR gate still only needs the json/text summaries, so lcov stays skipped.
env:
NODE_OPTIONS: --max-old-space-size=8192
EVENT_NAME: ${{ github.event_name }}
SONARQUBE_ENABLED: ${{ vars.SONARQUBE_ENABLED }}
RUN_HEAD_SHA: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || github.sha }}
run: |
LCOV_REPORTER=()
if [ "$EVENT_NAME" != "pull_request" ]; then LCOV_REPORTER=(--reporter=lcov); fi
if [ "$EVENT_NAME" != "pull_request" ] || [ "${SONARQUBE_ENABLED:-}" = "true" ]; then
LCOV_REPORTER=(--reporter=lcov)
fi
mkdir -p coverage
first_coverage_file=""
if [ -d coverage-shards ]; then
first_coverage_file="$(find coverage-shards -maxdepth 1 -type f -name '*.json' -print -quit)"
fi
if [ -z "$first_coverage_file" ]; then
echo "::error::No raw coverage shard data was downloaded."
find . -maxdepth 3 -type f | sort
exit 1
fi
# Retained producers keep their original attempts. The receipt binds all
# eight job/artifact identities and the aggregate sent to c8.
node scripts/ci/prepare-v8-coverage.mjs prepare coverage-shards coverage-shards-verified 8 "$GITHUB_SHA" "$GITHUB_RUN_ID" "$GITHUB_RUN_ATTEMPT" "$GITHUB_WORKSPACE" coverage/coverage-selection.json "$RUN_HEAD_SHA" "$GITHUB_REPOSITORY" > coverage/coverage-preparation.json
cat coverage/coverage-preparation.json
# Gate aligned to the project's local coverage bar: `npm run test:coverage`
# gates at 60/60/60/60, so CI must match it (the previous CI floor of 40
# silently undershot the local bar — a real drift). Real merged coverage is
@@ -1396,7 +1427,7 @@ jobs:
# coverage ratchet (quality-baseline.json) layers "must not drop vs baseline"
# on top of this floor.
npx c8 report \
--temp-directory coverage-shards \
--temp-directory coverage-shards-verified \
--reports-dir coverage \
--merge-async \
--reporter=text-summary \
@@ -1406,6 +1437,7 @@ jobs:
--exclude=**/*.test.* \
--check-coverage \
--statements 60 --lines 60 --functions 60 --branches 60
node scripts/ci/prepare-v8-coverage.mjs verify-report coverage
- name: Build coverage summary
if: always()
run: |
@@ -1456,6 +1488,8 @@ jobs:
path: |
coverage/coverage-summary.json
coverage/coverage-report.md
coverage/coverage-selection.json
coverage/coverage-preparation.json
coverage/lcov.info
if-no-files-found: warn
@@ -1484,6 +1518,17 @@ jobs:
with:
name: coverage-report
path: coverage/
# Without lcov.info the scan still "succeeds" and publishes 0.0% coverage on new code
# (#20725): fail here, naming the cause, instead of letting the quality gate blame the PR.
- name: Require coverage/lcov.info for the scan
if: ${{ github.event_name == 'pull_request' && env.SONAR_TOKEN != '' && env.SONAR_HOST_URL != '' }}
run: |
if [ ! -s coverage/lcov.info ]; then
echo "::error::coverage/lcov.info is missing or empty after downloading coverage-report; SonarQube would report 0% coverage on new code. Check the lcov reporter in the test-coverage job's merge step (#20725)."
ls -la coverage || true
exit 1
fi
echo "coverage/lcov.info: $(wc -l < coverage/lcov.info) lines"
- name: Explain SonarQube skip
if: ${{ github.event_name != 'pull_request' || env.SONAR_TOKEN == '' || env.SONAR_HOST_URL == '' }}
run: |

3444
.i18n-state.json generated

File diff suppressed because it is too large Load Diff

View File

@@ -1,122 +1,53 @@
# Mergify merge queue — WS3.4/D5 of the v3.8.49 quality/velocity master plan.
# Mergify — merge queue RETIRED by the owner's decision of 2026-11-19.
#
# WHY: ~85-100 active PR authors/month and 300+ PRs/week peaks, all merged by ONE
# identity. The manual merge-train validated batches by hand; this queue automates
# it with batching + automatic batch bisection (a red batch of N costs ~log2(N)
# revalidations instead of N). Mergify Open Source plan: free, unlimited, public repo.
# History: the Mergify `release` queue (WS3.4/D5 of the v3.8.49 quality/velocity master plan:
# owner-applied `queue` label, serial squash, checks_timeout 240 min) and the opt-in
# `relay-integration` queue landed release PRs until 2026-11-19 (last Mergify merge: #19538,
# 2026-11-15). Their rules, and the rule that removed the `queue` label after a merge, are in
# git history. Release PRs are now merged by hand under the repository ruleset "Require green
# gates on the active release" (`Gate / CI` + `Gate / Quality`) until omni-queue runs in live
# mode, and through omni-queue after that (docs/ops/OMNI_QUEUE.md).
#
# GOVERNANCE (non-negotiable, mirrors CLAUDE.md Hard Rules #21/#22 + the owner's
# pre-merge ⭐ gate):
# • A PR enters the queue ONLY via the `queue` label — applied by the owner (or a
# session acting for the owner) AFTER the pre-merge ⭐ report/decision. The label
# IS the merge approval; Mergify only executes it.
# • During a release-freeze (open issue labeled `release-freeze`), do NOT label PRs
# targeting the frozen branch — the freeze is a human-honored coordination signal
# the queue cannot see. Retarget to the active release/vX+1 first (Hard Rule #21).
# • Never label a PR another session is actively working (Hard Rule #22b).
# • Fallback path if Mergify misbehaves or the OSS plan changes: the manual
# merge-train runbook (docs/ops/MERGE_TRAIN.md) — remove labels, proceed by hand.
# WHY this file is kept instead of deleted: the Mergify GitHub App is still installed, and
# Mergify documents that "With no Mergify configuration, your queue already ... Merges
# automatically when your required checks pass" once someone comments `@mergifyio queue`
# (docs.mergify.com/merge-queue/setup). The docs do not say what that command does on a config
# without `queue_rules`, so the commands that would merge or rewrite a pull request are
# refused here: each condition list below is `closed` AND `-closed`, which no pull request can
# match. `commands_restrictions` is read whatever Mergify products are enabled
# (docs.mergify.com/configuration/file-format). `refresh` and `dequeue` keep their defaults:
# they neither merge nor push.
#
# Contract: tests/unit/mergify-queue-config.test.ts. Do not add `queue_rules`,
# `merge_protections_settings` or a merging `pull_request_rules` action back: two queues would
# act on the same release PRs.
# Auto-enqueue (current Mergify model, 2026): auto_merge_conditions in
# merge_protections_settings — the rules-based queue action / autoqueue path is
# deprecated (EOL 2026-07-16). The owner-applied `queue` label IS the approval.
merge_protections_settings:
auto_merge_conditions:
- label = queue
queue_rules:
- name: release
# Any current or future release branch — the reason GitHub's native queue was
# rejected (no wildcard support on personal-account repos).
queue_conditions:
- base~=^release/v\d+\.\d+\.\d+$
- label=queue
- -draft
- -conflict
# A reviewed integration candidate must never be squashed by this queue,
# including when its second approval label is missing or its ref changed.
- -label=integration-reviewed
- -head~=^fix/relay-integration-candidate-
# "Everything that ran is green, nothing still running, AND the always-on
# anchor check succeeded" — robust to the path-filtered fast-gates (docs-only
# PRs skip code jobs; matrix shard names vary) while never fail-open: a PR with
# zero checks cannot vacuously merge, because `Merge integrity` runs on EVERY
# non-draft PR (quality.yml) and must be an affirmative success. Review approval
# is intentionally NOT a condition here: the owner-applied `queue` label IS the
# approval in this repo's single-maintainer model (see governance header).
merge_conditions:
# "Zero failures" — EXCEPT the advisory "Build (advisory)" job (quality.yml):
# continue-on-error by design, and its GH-hosted Turbopack build hangs
# recurrently mid-"Creating an optimized production build" (100% failure rate
# across every sampled PR since the job was added 2026-07-27, always killed by
# a runner timeout/shutdown signal, never a real compile error). Any OTHER
# failure still blocks (anti-fail-open kept). The prior dast-smoke exception
# (#7225) was dropped here: dast-smoke's hang (#7226) has been dormant for
# weeks (0 failures in the last 30 runs; 2 all-time, none since 2026-07-13) —
# carrying its tolerance forward would mask problems it no longer causes.
- or:
- "#check-failure=0"
- and:
- "#check-failure=1"
- check-failure=Build (advisory)
- "#check-pending=0"
- "#check-success>=1"
- check-success=Merge integrity (changelog + generated skills)
- check-success=Gate / CI
- check-success=Gate / Quality
# NO batching: 'Merge Queue Batch' requires a paid Mergify tier (live finding
# 2026-07-15 — the queue command fails with "Cannot use Merge Queue batch" on
# the free plan; #7220). Serial queue (1 PR at a time) still automates the train.
# Rail G11 (v3.8.54) asks for batch_size ~5: it stays BLOCKED on that tier —
# adding batch_size/batch_max_wait_time here would dequeue EVERY PR again. Do not
# re-add them unless the Mergify subscription is upgraded (owner decision).
#
# checks_timeout = 2 x p95 wall-clock of the quality.yml workflow (the fast-gates
# that run on PR -> release/**), measured over the last 100 successful runs
# (2026-09-28 .. 2026-10-08, createdAt -> updatedAt, so runner queueing counts):
# mean 34.5 min · p50 1.8 min · p90 101.0 min · p95 119.75 min · max 468.6 min
# (bimodal: path-filtered docs-only runs ~2 min vs full runs ~72 min median).
# 2 x 119.75 = 239.5 -> rounded up to 240 min. A PR whose checks are still
# pending past this is dequeued instead of blocking the serial queue forever.
# Re-measure with: gh run list --workflow quality.yml --status success
# --limit 100 --json createdAt,updatedAt (contract: tests/unit/mergify-queue-config.test.ts).
checks_timeout: 240 min
# Squash keeps the one-commit-per-PR history the CHANGELOG reconciliation expects.
merge_method: squash
# One already-composed PR, NOT Mergify's paid multi-PR batching feature.
# Activation requires this configuration to land on the default branch first.
# See docs/ops/RELAY_INTEGRATION_QUEUE.md for ownership, admission and readback.
- name: relay-integration
queue_conditions:
- base=release/v3.8.52
- head=fix/relay-integration-candidate-20261015
- author=diegosouzapw
- label=queue
- label=integration-reviewed
- -draft
- -conflict
merge_conditions:
- or:
- "#check-failure=0"
- and:
- "#check-failure=1"
- check-failure=Build (advisory)
- "#check-pending=0"
- "#check-success>=1"
- check-success=Merge integrity (changelog + generated skills)
- check-success=Gate / CI
- check-success=Gate / Quality
checks_timeout: 240 min
# Preserve the reviewed original PR heads; rebasing or squash would lose them.
update_method: merge
merge_method: merge
pull_request_rules:
- name: clean up the queue label after merge
commands_restrictions:
queue:
conditions:
- merged
actions:
label:
remove:
- queue
- closed
- -closed
requeue:
conditions:
- closed
- -closed
rebase:
conditions:
- closed
- -closed
update:
conditions:
- closed
- -closed
squash:
conditions:
- closed
- -closed
backport:
conditions:
- closed
- -closed
copy:
conditions:
- closed
- -closed

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "ገደቡ አዎንታዊ ኢንቲጀር መሆን አለበት።",
"error": "ስህተት፦ {message}",
"serverOffline": "የOmniRoute አገልጋይ ከመስመር ውጭ ነው። በዚህ ያስጀምሩት፦ omniroute serve",
"authRequired": "ማረጋገጫ ያስፈልጋል። OMNIROUTE_API_KEY ያዘጋጁ ወይም ይህን ያስኪዱ፦ omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} ይደረግ ነበር",
"cancelled": "ተሰርዟል።",
"jsonOpt": "ውጤቱን እንደ JSON አቅርብ",
"yesOpt": "የማረጋገጫ ጥያቄውን ዝለል"
"yesOpt": "የማረጋገጫ ጥያቄውን ዝለል",
"positiveIntegerRequired": "ገደቡ አዎንታዊ ኢንቲጀር መሆን አለበት።"
},
"setup": {
"title": "የOmniRoute ማዋቀር",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "يجب أن يكون الحد عددًا صحيحًا موجبًا.",
"error": "خطأ: {message}",
"serverOffline": "خادم OmniRoute غير متصل. ابدأ بالأمر: omniroute serve",
"authRequired": "المصادقة مطلوبة. عيّن OMNIROUTE_API_KEY أو شغّل: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[محاكاة] سيتم: {action}",
"cancelled": "تم الإلغاء.",
"jsonOpt": "إخراج بتنسيق JSON",
"yesOpt": "تخطي رسالة التأكيد"
"yesOpt": "تخطي رسالة التأكيد",
"positiveIntegerRequired": "يجب أن يكون الحد عددًا صحيحًا موجبًا."
},
"setup": {
"title": "إعداد OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Limit müsbət tam ədəd olmalıdır.",
"error": "Xəta: {message}",
"serverOffline": "OmniRoute serveri oflayndır. Başladın: omniroute serve",
"authRequired": "Autentifikasiya tələb olunur. OMNIROUTE_API_KEY təyin edin və ya işə salın: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulyasiya] ediləcəkdi: {action}",
"cancelled": "Ləğv edildi.",
"jsonOpt": "JSON formatında çıxış",
"yesOpt": "Təsdiq sorğusunu keç"
"yesOpt": "Təsdiq sorğusunu keç",
"positiveIntegerRequired": "Limit müsbət tam ədəd olmalıdır."
},
"setup": {
"title": "OmniRoute Quraşdırılması",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Ограничението трябва да е положително цяло число.",
"error": "Грешка: {message}",
"serverOffline": "Сървърът OmniRoute е офлайн. Стартирайте с: omniroute serve",
"authRequired": "Необходима е автентикация. Задайте OMNIROUTE_API_KEY или изпълнете: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[симулация] ще извърши: {action}",
"cancelled": "Отменено.",
"jsonOpt": "Изход като JSON",
"yesOpt": "Пропускане на потвърждение"
"yesOpt": "Пропускане на потвърждение",
"positiveIntegerRequired": "Ограничението трябва да е положително цяло число."
},
"setup": {
"title": "Настройка на OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "সীমা একটি ধনাত্মক পূর্ণসংখ্যা হতে হবে।",
"error": "ত্রুটি: {message}",
"serverOffline": "OmniRoute সার্ভার অফলাইনে আছে। এটি চালু করুন: omniroute serve",
"authRequired": "প্রমাণীকরণ প্রয়োজন। OMNIROUTE_API_KEY সেট করুন অথবা চালান: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} করা হতো",
"cancelled": "বাতিল করা হয়েছে।",
"jsonOpt": "JSON হিসেবে আউটপুট দিন",
"yesOpt": "নিশ্চিতকরণের প্রম্পট এড়িয়ে যান"
"yesOpt": "নিশ্চিতকরণের প্রম্পট এড়িয়ে যান",
"positiveIntegerRequired": "সীমা একটি ধনাত্মক পূর্ণসংখ্যা হতে হবে।"
},
"setup": {
"title": "OmniRoute সেটআপ",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Limit mora biti pozitivan cijeli broj.",
"error": "Greška: {message}",
"serverOffline": "OmniRoute server nije dostupan. Pokrenite ga komandom: omniroute serve",
"authRequired": "Potrebna je autentifikacija. Postavite OMNIROUTE_API_KEY ili pokrenite: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] bi izvršio {action}",
"cancelled": "Otkazano.",
"jsonOpt": "Izlaz kao JSON",
"yesOpt": "Preskoči potvrdu"
"yesOpt": "Preskoči potvrdu",
"positiveIntegerRequired": "Limit mora biti pozitivan cijeli broj."
},
"setup": {
"title": "OmniRoute Setup",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Limit musí být kladné celé číslo.",
"error": "Chyba: {message}",
"serverOffline": "Server OmniRoute je offline. Spusťte: omniroute serve",
"authRequired": "Vyžaduje se ověření. Nastavte OMNIROUTE_API_KEY nebo spusťte: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulace] by provedlo: {action}",
"cancelled": "Zrušeno.",
"jsonOpt": "Výstup jako JSON",
"yesOpt": "Přeskočit potvrzení"
"yesOpt": "Přeskočit potvrzení",
"positiveIntegerRequired": "Limit musí být kladné celé číslo."
},
"setup": {
"title": "Nastavení OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Grænse skal være et positivt heltal.",
"error": "Fejl: {message}",
"serverOffline": "OmniRoute-serveren er offline. Start med: omniroute serve",
"authRequired": "Godkendelse kræves. Sæt OMNIROUTE_API_KEY eller kør: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulering] ville: {action}",
"cancelled": "Annulleret.",
"jsonOpt": "Output som JSON",
"yesOpt": "Spring bekræftelse over"
"yesOpt": "Spring bekræftelse over",
"positiveIntegerRequired": "Grænse skal være et positivt heltal."
},
"setup": {
"title": "Opsætning af OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Der Grenzwert muss eine positive ganze Zahl sein.",
"error": "Fehler: {message}",
"serverOffline": "OmniRoute-Server ist offline. Starten mit: omniroute serve",
"authRequired": "Authentifizierung erforderlich. OMNIROUTE_API_KEY setzen oder ausführen: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[Simulation] würde: {action}",
"cancelled": "Abgebrochen.",
"jsonOpt": "Ausgabe als JSON",
"yesOpt": "Bestätigung überspringen"
"yesOpt": "Bestätigung überspringen",
"positiveIntegerRequired": "Der Grenzwert muss eine positive ganze Zahl sein."
},
"setup": {
"title": "OmniRoute-Einrichtung",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Το όριο πρέπει να είναι θετικός ακέραιος.",
"error": "Σφάλμα: {message}",
"serverOffline": "Ο διακομιστής OmniRoute είναι εκτός σύνδεσης. Εκκινήστε τον με: omniroute serve",
"authRequired": "Απαιτείται έλεγχος ταυτότητας. Ορίστε το OMNIROUTE_API_KEY ή εκτελέστε: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[δοκιμαστική εκτέλεση] θα {action}",
"cancelled": "Ακυρώθηκε.",
"jsonOpt": "Έξοδος ως JSON",
"yesOpt": "Παράλειψη προτροπής επιβεβαίωσης"
"yesOpt": "Παράλειψη προτροπής επιβεβαίωσης",
"positiveIntegerRequired": "Το όριο πρέπει να είναι θετικός ακέραιος."
},
"setup": {
"title": "Εγκατάσταση OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "El límite debe ser un número entero positivo.",
"error": "Error: {message}",
"serverOffline": "El servidor OmniRoute está offline. Inícielo con: omniroute serve",
"authRequired": "Autenticación requerida. Configure OMNIROUTE_API_KEY o ejecute: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulación] haría: {action}",
"cancelled": "Cancelado.",
"jsonOpt": "Salida como JSON",
"yesOpt": "Omitir confirmación"
"yesOpt": "Omitir confirmación",
"positiveIntegerRequired": "El límite debe ser un número entero positivo."
},
"setup": {
"title": "Configuración de OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Limiit peab olema positiivne täisarv.",
"error": "Viga: {message}",
"serverOffline": "OmniRoute server on offline. Käivita see käsuga: omniroute serve",
"authRequired": "Autentimine on nõutav. Määra OMNIROUTE_API_KEY või käivita: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[testkäivitus] tehakse {action}",
"cancelled": "Tühistatud.",
"jsonOpt": "Väljund JSON-formaadis",
"yesOpt": "Jäta kinnitusküsimus vahele"
"yesOpt": "Jäta kinnitusküsimus vahele",
"positiveIntegerRequired": "Limiit peab olema positiivne täisarv."
},
"setup": {
"title": "OmniRoute seadistus",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "حد باید یک عدد صحیح مثبت باشد.",
"error": "خطا: {message}",
"serverOffline": "سرور OmniRoute آفلاین است. با این دستور راه‌اندازی کنید: omniroute serve",
"authRequired": "احراز هویت لازم است. OMNIROUTE_API_KEY را تنظیم کنید یا اجرا کنید: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[شبیه‌سازی] اقدام می‌شد: {action}",
"cancelled": "لغو شد.",
"jsonOpt": "خروجی به صورت JSON",
"yesOpt": "رد کردن تأیید"
"yesOpt": "رد کردن تأیید",
"positiveIntegerRequired": "حد باید یک عدد صحیح مثبت باشد."
},
"setup": {
"title": "راهاندازی OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Rajan on oltava positiivinen kokonaisluku.",
"error": "Virhe: {message}",
"serverOffline": "OmniRoute-palvelin on offline. Käynnistä komennolla: omniroute serve",
"authRequired": "Todennus vaaditaan. Aseta OMNIROUTE_API_KEY tai suorita: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulointi] tekisi: {action}",
"cancelled": "Peruutettu.",
"jsonOpt": "Tulosta JSON-muodossa",
"yesOpt": "Ohita vahvistuspyyntö"
"yesOpt": "Ohita vahvistuspyyntö",
"positiveIntegerRequired": "Rajan on oltava positiivinen kokonaisluku."
},
"setup": {
"title": "OmniRoute-asennus",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "La limite doit être un entier positif.",
"error": "Erreur : {message}",
"serverOffline": "Le serveur OmniRoute est hors ligne. Démarrez avec : omniroute serve",
"authRequired": "Authentification requise. Définissez OMNIROUTE_API_KEY ou exécutez : omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulation] ferait : {action}",
"cancelled": "Annulé.",
"jsonOpt": "Sortie au format JSON",
"yesOpt": "Ignorer la confirmation"
"yesOpt": "Ignorer la confirmation",
"positiveIntegerRequired": "La limite doit être un entier positif."
},
"setup": {
"title": "Configuration d’OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Ní mór teorainn a bheith ina slánuimhir dhearfach.",
"error": "Earráid: {message}",
"serverOffline": "Tá freastalaí OmniRoute as líne. Tosaigh le: omniroute serve",
"authRequired": "Fíordheimhniú ag teastáil. Socraigh OMNIROUTE_API_KEY nó rith: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[triail thuras] dhéanfadh {action}",
"cancelled": "Cealaithe.",
"jsonOpt": "Aschur mar JSON",
"yesOpt": "Scipeáil an契ordheimhniú"
"yesOpt": "Scipeáil an契ordheimhniú",
"positiveIntegerRequired": "Ní mór teorainn a bheith ina slánuimhir dhearfach."
},
"setup": {
"title": "Socrú OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "મર્યાદા સકારાત્મક પૂર્ણાંક હોવી જોઈએ.",
"error": "ભૂલ: {message}",
"serverOffline": "OmniRoute સર્વર ઑફલાઇન છે. તેને આ કમાન્ડથી શરૂ કરો: omniroute serve",
"authRequired": "પ્રમાણીકરણ જરૂરી છે. OMNIROUTE_API_KEY સેટ કરો અથવા આ કમાન્ડ ચલાવો: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} કરાશે",
"cancelled": "રદ કરવામાં આવ્યું.",
"jsonOpt": "JSON તરીકે આઉટપુટ કરો",
"yesOpt": "પુષ્ટિકરણ પ્રોમ્પ્ટ છોડો"
"yesOpt": "પુષ્ટિકરણ પ્રોમ્પ્ટ છોડો",
"positiveIntegerRequired": "મર્યાદા સકારાત્મક પૂર્ણાંક હોવી જોઈએ."
},
"setup": {
"title": "OmniRoute સેટઅપ",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Dole ne iyakar ta zama cikakkiyar lamba wadda ta fi sifili.",
"error": "Kuskure: {message}",
"serverOffline": "Sabar OmniRoute ba ta kan layi. Kunna ta da: omniroute serve",
"authRequired": "Ana buƙatar tantancewa. Saita OMNIROUTE_API_KEY ko gudanar da: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] za a {action}",
"cancelled": "An soke.",
"jsonOpt": "Fitar da sakamako a matsayin JSON",
"yesOpt": "Tsallake tambayar tabbatarwa"
"yesOpt": "Tsallake tambayar tabbatarwa",
"positiveIntegerRequired": "Dole ne iyakar ta zama cikakkiyar lamba wadda ta fi sifili."
},
"setup": {
"title": "Saitin OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "הגבלה חייבת להיות מספר שלם חיובי.",
"error": "שגיאה: {message}",
"serverOffline": "שרת OmniRoute אינו מקוון. הפעילו אותו באמצעות: omniroute serve",
"authRequired": "נדרש אימות. הגדירו את OMNIROUTE_API_KEY או הריצו: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[הרצה-יבשה] הפעולה שהייתה מתבצעת: {action}",
"cancelled": "בוטל.",
"jsonOpt": "פלט בפורמט JSON",
"yesOpt": "דילוג על בקשת האישור"
"yesOpt": "דילוג על בקשת האישור",
"positiveIntegerRequired": "הגבלה חייבת להיות מספר שלם חיובי."
},
"setup": {
"title": "הגדרת OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "सीमा एक धनात्मक पूर्णांक होनी चाहिए.",
"error": "त्रुटि: {message}",
"serverOffline": "OmniRoute सर्वर ऑफलाइन है। शुरू करें: omniroute serve",
"authRequired": "प्रमाणीकरण आवश्यक है। OMNIROUTE_API_KEY सेट करें या चलाएं: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[अनुकरण] करेगा: {action}",
"cancelled": "रद्द किया गया।",
"jsonOpt": "JSON के रूप में आउटपुट",
"yesOpt": "पुष्टि छोड़ें"
"yesOpt": "पुष्टि छोड़ें",
"positiveIntegerRequired": "सीमा एक धनात्मक पूर्णांक होनी चाहिए."
},
"setup": {
"title": "OmniRoute सेटअप",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Ograničenje mora biti pozitivan cijeli broj.",
"error": "Greška: {message}",
"serverOffline": "OmniRoute poslužitelj je izvan mreže. Pokrenite ga s: omniroute serve",
"authRequired": "Potrebna je autentifikacija. Postavite OMNIROUTE_API_KEY ili pokrenite: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[probni-unos] bi {action}",
"cancelled": "Otkazano.",
"jsonOpt": "Ispis kao JSON",
"yesOpt": "Preskoči upit za potvrdu"
"yesOpt": "Preskoči upit za potvrdu",
"positiveIntegerRequired": "Ograničenje mora biti pozitivan cijeli broj."
},
"setup": {
"title": "OmniRoute Postavljanje",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "A limitnek pozitív egész számnak kell lennie.",
"error": "Hiba: {message}",
"serverOffline": "Az OmniRoute szerver offline. Indítsa el: omniroute serve",
"authRequired": "Hitelesítés szükséges. Állítsa be az OMNIROUTE_API_KEY-t vagy futtassa: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[szimuláció] végrehajtaná: {action}",
"cancelled": "Törölve.",
"jsonOpt": "JSON formátumú kimenet",
"yesOpt": "Megerősítés kihagyása"
"yesOpt": "Megerősítés kihagyása",
"positiveIntegerRequired": "A limitnek pozitív egész számnak kell lennie."
},
"setup": {
"title": "OmniRoute beállítása",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Սահմանը պետք է լինի դրական ամբողջ թիվ։",
"error": "Սխալ՝ {message}",
"serverOffline": "OmniRoute սերվերն անցանց է։ Գործարկեք այն հետևյալ հրամանով՝ omniroute serve",
"authRequired": "Պահանջվում է նույնականացում։ Սահմանեք OMNIROUTE_API_KEY-ը կամ գործարկեք՝ omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] կկատարվեր՝ {action}",
"cancelled": "Չեղարկված է։",
"jsonOpt": "Արտածել JSON ձևաչափով",
"yesOpt": "Բաց թողնել հաստատման հարցումը"
"yesOpt": "Բաց թողնել հաստատման հարցումը",
"positiveIntegerRequired": "Սահմանը պետք է լինի դրական ամբողջ թիվ։"
},
"setup": {
"title": "OmniRoute-ի կարգավորում",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Batas harus berupa bilangan bulat positif.",
"error": "Kesalahan: {message}",
"serverOffline": "Server OmniRoute sedang offline. Mulai dengan: omniroute serve",
"authRequired": "Autentikasi diperlukan. Setel OMNIROUTE_API_KEY atau jalankan: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulasi] akan: {action}",
"cancelled": "Dibatalkan.",
"jsonOpt": "Keluaran sebagai JSON",
"yesOpt": "Lewati konfirmasi"
"yesOpt": "Lewati konfirmasi",
"positiveIntegerRequired": "Batas harus berupa bilangan bulat positif."
},
"setup": {
"title": "Penyiapan OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Oke ga-abụrịrị ọnụọgụ zuru ezu karịrị efu.",
"error": "Njehie: {message}",
"serverOffline": "Sava OmniRoute anọghị n'ịntanetị. Jiri nke a malite ya: omniroute serve",
"authRequired": "Achọrọ njirimara. Tọọ OMNIROUTE_API_KEY ma ọ bụ mee: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] a ga-eme {action}",
"cancelled": "Akagbuola.",
"jsonOpt": "Wepụta dị ka JSON",
"yesOpt": "Mafee ajụjụ nkwenye"
"yesOpt": "Mafee ajụjụ nkwenye",
"positiveIntegerRequired": "Oke ga-abụrịrị ọnụọgụ zuru ezu karịrị efu."
},
"setup": {
"title": "Ntọala OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Il limite deve essere un numero intero positivo.",
"error": "Errore: {message}",
"serverOffline": "Il server OmniRoute è offline. Avviarlo con: omniroute serve",
"authRequired": "Autenticazione richiesta. Impostare OMNIROUTE_API_KEY o eseguire: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulazione] eseguirebbe: {action}",
"cancelled": "Annullato.",
"jsonOpt": "Output come JSON",
"yesOpt": "Salta la conferma"
"yesOpt": "Salta la conferma",
"positiveIntegerRequired": "Il limite deve essere un numero intero positivo."
},
"setup": {
"title": "Configurazione di OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "制限は正の整数である必要があります。",
"error": "エラー: {message}",
"serverOffline": "OmniRouteサーバーはオフラインです。起動: omniroute serve",
"authRequired": "認証が必要です。OMNIROUTE_API_KEYを設定するか実行してください: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[シミュレーション] 実行予定: {action}",
"cancelled": "キャンセルしました。",
"jsonOpt": "JSON形式で出力",
"yesOpt": "確認をスキップ"
"yesOpt": "確認をスキップ",
"positiveIntegerRequired": "制限は正の整数である必要があります。"
},
"setup": {
"title": "OmniRoute セットアップ",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "ლიმიტი უნდა იყოს დადებითი მთელი რიცხვი.",
"error": "შეცდომა: {message}",
"serverOffline": "OmniRoute სერვერი გამორთულია. გაუშვით ბრძანებით: omniroute serve",
"authRequired": "საჭიროა ავთენტიფიკაცია. დააყენეთ OMNIROUTE_API_KEY ან გაუშვით: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] შესრულდებოდა: {action}",
"cancelled": "გაუქმებულია.",
"jsonOpt": "გამოტანა JSON ფორმატში",
"yesOpt": "დადასტურების მოთხოვნის გამოტოვება"
"yesOpt": "დადასტურების მოთხოვნის გამოტოვება",
"positiveIntegerRequired": "ლიმიტი უნდა იყოს დადებითი მთელი რიცხვი."
},
"setup": {
"title": "OmniRoute-ის დაყენება",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "ដែនកំណត់ត្រូវតែជាចំនួនគត់វិជ្ជមាន។",
"error": "កំហុស៖ {message}",
"serverOffline": "ម៉ាស៊ីនមេ OmniRoute មិនដំណើរការ។ ចាប់ផ្ដើមវាដោយ៖ omniroute serve",
"authRequired": "ទាមទារការផ្ទៀងផ្ទាត់អត្តសញ្ញាណ។ កំណត់ OMNIROUTE_API_KEY ឬដំណើរការ៖ omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] នឹង {action}",
"cancelled": "បានបោះបង់។",
"jsonOpt": "បញ្ចេញលទ្ធផលជា JSON",
"yesOpt": "រំលងសារស្នើឱ្យបញ្ជាក់"
"yesOpt": "រំលងសារស្នើឱ្យបញ្ជាក់",
"positiveIntegerRequired": "ដែនកំណត់ត្រូវតែជាចំនួនគត់វិជ្ជមាន។"
},
"setup": {
"title": "ការដំឡើង OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "ಮಿತಿಯು ಧನಾತ್ಮಕ ಪೂರ್ಣಾಂಕವಾಗಿರಬೇಕು.",
"error": "ದೋಷ: {message}",
"serverOffline": "OmniRoute ಸರ್ವರ್ ಆಫ್ಲೈನ್ನಲ್ಲಿದೆ. ಇದನ್ನು ಪ್ರಾರಂಭಿಸಲು: omniroute serve",
"authRequired": "ದೃಢೀಕರಣ ಅಗತ್ಯವಿದೆ. OMNIROUTE_API_KEY ಹೊಂದಿಸಿ ಅಥವಾ ಇದನ್ನು ಚಲಾಯಿಸಿ: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[ಡ್ರೈ-ರನ್] {action} ಮಾಡಲಾಗುತ್ತಿತ್ತು",
"cancelled": "ರದ್ದುಗೊಳಿಸಲಾಗಿದೆ.",
"jsonOpt": "JSON ಆಗಿ ಔಟ್ಪುಟ್ ಮಾಡಿ",
"yesOpt": "ದೃಢೀಕರಣ ಪ್ರಾಂಪ್ಟ್ ಅನ್ನು ಬಿಟ್ಟುಬಿಡಿ"
"yesOpt": "ದೃಢೀಕರಣ ಪ್ರಾಂಪ್ಟ್ ಅನ್ನು ಬಿಟ್ಟುಬಿಡಿ",
"positiveIntegerRequired": "ಮಿತಿಯು ಧನಾತ್ಮಕ ಪೂರ್ಣಾಂಕವಾಗಿರಬೇಕು."
},
"setup": {
"title": "OmniRoute ಸೆಟಪ್",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "한도는 양의 정수여야 합니다.",
"error": "오류: {message}",
"serverOffline": "OmniRoute 서버가 오프라인입니다. 시작: omniroute serve",
"authRequired": "인증이 필요합니다. OMNIROUTE_API_KEY를 설정하거나 실행하세요: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[시뮬레이션] 실행 예정: {action}",
"cancelled": "취소되었습니다.",
"jsonOpt": "JSON으로 출력",
"yesOpt": "확인 건너뛰기"
"yesOpt": "확인 건너뛰기",
"positiveIntegerRequired": "한도는 양의 정수여야 합니다."
},
"setup": {
"title": "OmniRoute 설정",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Riba turi būti teigiamas sveikasis skaičius.",
"error": "Klaida: {message}",
"serverOffline": "OmniRoute serveris nepasiekiamas. Paleiskite jį naudodami komandą: omniroute serve",
"authRequired": "Reikalingas autentifikavimas. Nustatykite OMNIROUTE_API_KEY arba vykdykite komandą: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] būtų atliktas veiksmas: {action}",
"cancelled": "Atšaukta.",
"jsonOpt": "Išvesti JSON formatu",
"yesOpt": "Praleisti patvirtinimo užklausą"
"yesOpt": "Praleisti patvirtinimo užklausą",
"positiveIntegerRequired": "Riba turi būti teigiamas sveikasis skaičius."
},
"setup": {
"title": "OmniRoute sąranka",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Ierobežojumam ir jābūt pozitīvam veselam skaitlim.",
"error": "Kļūda: {message}",
"serverOffline": "OmniRoute serveris nedarbojas. Startējiet to ar: omniroute serve",
"authRequired": "Nepieciešama autentifikācija. Iestatiet OMNIROUTE_API_KEY vai palaidiet: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[testrežīms] veiktu {action}",
"cancelled": "Atcelts.",
"jsonOpt": "Izvade JSON formātā",
"yesOpt": "Izlaist apstiprinājuma pieprasījumu"
"yesOpt": "Izlaist apstiprinājuma pieprasījumu",
"positiveIntegerRequired": "Ierobežojumam ir jābūt pozitīvam veselam skaitlim."
},
"setup": {
"title": "OmniRoute iestatīšana",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "പരിധി ഒരു പോസിറ്റീവ് പൂർണ്ണസംഖ്യയായിരിക്കണം.",
"error": "പിശക്: {message}",
"serverOffline": "OmniRoute സെർവർ ഓഫ്ലൈനാണ്. ഇത് ആരംഭിക്കാൻ: omniroute serve",
"authRequired": "പ്രാമാണീകരണം ആവശ്യമാണ്. OMNIROUTE_API_KEY സജ്ജമാക്കുക അല്ലെങ്കിൽ പ്രവർത്തിപ്പിക്കുക: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} ചെയ്യുമായിരുന്നു",
"cancelled": "റദ്ദാക്കി.",
"jsonOpt": "JSON ആയി ഔട്ട്പുട്ട് ചെയ്യുക",
"yesOpt": "സ്ഥിരീകരണ നിർദ്ദേശം ഒഴിവാക്കുക"
"yesOpt": "സ്ഥിരീകരണ നിർദ്ദേശം ഒഴിവാക്കുക",
"positiveIntegerRequired": "പരിധി ഒരു പോസിറ്റീവ് പൂർണ്ണസംഖ്യയായിരിക്കണം."
},
"setup": {
"title": "OmniRoute സജ്ജീകരണം",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "मर्यादा सकारात्मक पूर्णांक असणे आवश्यक आहे.",
"error": "त्रुटी: {message}",
"serverOffline": "OmniRoute सर्व्हर ऑफलाइन आहे. तो सुरू करण्यासाठी चालवा: omniroute serve",
"authRequired": "प्रमाणीकरण आवश्यक आहे. OMNIROUTE_API_KEY सेट करा किंवा हे चालवा: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} केले असते",
"cancelled": "रद्द केले.",
"jsonOpt": "JSON स्वरूपात आउटपुट द्या",
"yesOpt": "पुष्टीकरण प्रॉम्प्ट वगळा"
"yesOpt": "पुष्टीकरण प्रॉम्प्ट वगळा",
"positiveIntegerRequired": "मर्यादा सकारात्मक पूर्णांक असणे आवश्यक आहे."
},
"setup": {
"title": "OmniRoute सेटअप",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Had mestilah integer positif.",
"error": "Ralat: {message}",
"serverOffline": "Pelayan OmniRoute di luar talian. Mulakannya dengan: omniroute serve",
"authRequired": "Pengesahan diperlukan. Tetapkan OMNIROUTE_API_KEY atau jalankan: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] akan {action}",
"cancelled": "Dibatalkan.",
"jsonOpt": "Output sebagai JSON",
"yesOpt": "Langkau gesaan pengesahan"
"yesOpt": "Langkau gesaan pengesahan",
"positiveIntegerRequired": "Had mestilah integer positif."
},
"setup": {
"title": "Persediaan OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Il-limitu għandu jkun numru sħiħ pożittiv.",
"error": "Żball: {message}",
"serverOffline": "is-servizz OmniRoute huwa offline. Bda' b: omniroute serve",
"authRequired": "Jintalab awtentikazzjoni. Agħżel OMNIROUTE_API_KEY jew skurri: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] se jaġixx {action}",
"cancelled": "Kkanċellat.",
"jsonOpt": "Output bħala JSON",
"yesOpt": "Qabżu l-prompt ta' konferma"
"yesOpt": "Qabżu l-prompt ta' konferma",
"positiveIntegerRequired": "Il-limitu għandu jkun numru sħiħ pożittiv."
},
"setup": {
"title": "Twaqqif ta' OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "ကန့်သတ်ချက်သည် အပေါင်းကိန်းပြည့်ဖြစ်ရမည်။",
"error": "အမှား: {message}",
"serverOffline": "OmniRoute ဆာဗာ အော့ဖ်လိုင်းဖြစ်နေသည်။ စတင်ရန်: omniroute serve",
"authRequired": "စစ်မှန်ကြောင်း အတည်ပြုရန် လိုအပ်သည်။ OMNIROUTE_API_KEY ကို သတ်မှတ်ပါ သို့မဟုတ် ဤအမိန့်ကို လုပ်ဆောင်ပါ: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} လုပ်ဆောင်မည်",
"cancelled": "ပယ်ဖျက်လိုက်သည်။",
"jsonOpt": "JSON အဖြစ် ထုတ်ပေးရန်",
"yesOpt": "အတည်ပြုချက် တောင်းခံမှုကို ကျော်ရန်"
"yesOpt": "အတည်ပြုချက် တောင်းခံမှုကို ကျော်ရန်",
"positiveIntegerRequired": "ကန့်သတ်ချက်သည် အပေါင်းကိန်းပြည့်ဖြစ်ရမည်။"
},
"setup": {
"title": "OmniRoute စနစ်ထည့်သွင်းခြင်း",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "सीमा सकारात्मक पूर्णांक हुनुपर्छ।",
"error": "त्रुटि: {message}",
"serverOffline": "OmniRoute सर्भर अफलाइन छ। यसरी सुरु गर्नुहोस्: omniroute serve",
"authRequired": "प्रमाणीकरण आवश्यक छ। OMNIROUTE_API_KEY सेट गर्नुहोस् वा चलाउनुहोस्: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] ले {action} गर्ने थियो",
"cancelled": "रद्द गरियो।",
"jsonOpt": "JSON का रूपमा आउटपुट गर्नुहोस्",
"yesOpt": "पुष्टि प्रम्प्ट छोड्नुहोस्"
"yesOpt": "पुष्टि प्रम्प्ट छोड्नुहोस्",
"positiveIntegerRequired": "सीमा सकारात्मक पूर्णांक हुनुपर्छ।"
},
"setup": {
"title": "OmniRoute सेटअप",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Limiet moet een positief geheel getal zijn.",
"error": "Fout: {message}",
"serverOffline": "OmniRoute-server is offline. Start met: omniroute serve",
"authRequired": "Authenticatie vereist. Stel OMNIROUTE_API_KEY in of voer uit: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulatie] zou: {action}",
"cancelled": "Geannuleerd.",
"jsonOpt": "Uitvoer als JSON",
"yesOpt": "Bevestiging overslaan"
"yesOpt": "Bevestiging overslaan",
"positiveIntegerRequired": "Limiet moet een positief geheel getal zijn."
},
"setup": {
"title": "OmniRoute-installatie",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Grensen må være et positivt heltall.",
"error": "Feil: {message}",
"serverOffline": "OmniRoute-serveren er offline. Start med: omniroute serve",
"authRequired": "Autentisering kreves. Angi OMNIROUTE_API_KEY eller kjør: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulering] ville: {action}",
"cancelled": "Avbrutt.",
"jsonOpt": "Utdata som JSON",
"yesOpt": "Hopp over bekreftelse"
"yesOpt": "Hopp over bekreftelse",
"positiveIntegerRequired": "Grensen må være et positivt heltall."
},
"setup": {
"title": "Oppsett av OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "ସୀମା ଏକ ସକାରାତ୍ମକ ପୂର୍ଣ୍ଣ ସଂଖ୍ୟା ହେବା ଆବଶ୍ୟକ।",
"error": "ତ୍ରୁଟି: {message}",
"serverOffline": "OmniRoute ସର୍ଭର ଅଫ୍‌ଲାଇନ୍ ଅଛି। ଏହାକୁ ଆରମ୍ଭ କରନ୍ତୁ: omniroute serve",
"authRequired": "ପ୍ରମାଣୀକରଣ ଆବଶ୍ୟକ। OMNIROUTE_API_KEY ସେଟ୍ କରନ୍ତୁ କିମ୍ବା ଚଲାନ୍ତୁ: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} କରାଯାଇଥାନ୍ତା",
"cancelled": "ବାତିଲ୍ କରାଗଲା।",
"jsonOpt": "JSON ଭାବେ ଆଉଟ୍‌ପୁଟ୍ କରନ୍ତୁ",
"yesOpt": "ନିଶ୍ଚିତକରଣ ପ୍ରମ୍ପ୍ଟ ଏଡ଼ାନ୍ତୁ"
"yesOpt": "ନିଶ୍ଚିତକରଣ ପ୍ରମ୍ପ୍ଟ ଏଡ଼ାନ୍ତୁ",
"positiveIntegerRequired": "ସୀମା ଏକ ସକାରାତ୍ମକ ପୂର୍ଣ୍ଣ ସଂଖ୍ୟା ହେବା ଆବଶ୍ୟକ।"
},
"setup": {
"title": "OmniRoute ସେଟ୍‌ଅପ୍",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "ਸੀਮਾ ਇੱਕ ਸਕਾਰਾਤਮਕ ਪੂਰਨ ਅੰਕ ਹੋਣੀ ਚਾਹੀਦੀ ਹੈ।",
"error": "ਗਲਤੀ: {message}",
"serverOffline": "OmniRoute ਸਰਵਰ ਆਫ਼ਲਾਈਨ ਹੈ। ਇਸਨੂੰ ਇਸ ਕਮਾਂਡ ਨਾਲ ਚਾਲੂ ਕਰੋ: omniroute serve",
"authRequired": "ਪ੍ਰਮਾਣੀਕਰਨ ਲੋੜੀਂਦਾ ਹੈ। OMNIROUTE_API_KEY ਸੈੱਟ ਕਰੋ ਜਾਂ ਇਹ ਚਲਾਓ: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} ਕੀਤਾ ਜਾਵੇਗਾ",
"cancelled": "ਰੱਦ ਕੀਤਾ ਗਿਆ।",
"jsonOpt": "ਆਉਟਪੁੱਟ JSON ਵਜੋਂ ਦਿਓ",
"yesOpt": "ਪੁਸ਼ਟੀਕਰਨ ਪ੍ਰੌਂਪਟ ਛੱਡੋ"
"yesOpt": "ਪੁਸ਼ਟੀਕਰਨ ਪ੍ਰੌਂਪਟ ਛੱਡੋ",
"positiveIntegerRequired": "ਸੀਮਾ ਇੱਕ ਸਕਾਰਾਤਮਕ ਪੂਰਨ ਅੰਕ ਹੋਣੀ ਚਾਹੀਦੀ ਹੈ।"
},
"setup": {
"title": "OmniRoute ਸੈੱਟਅੱਪ",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Ang limitasyon ay dapat na isang positibong integer.",
"error": "Error: {message}",
"serverOffline": "Offline ang OmniRoute server. Simulan ito gamit ang: omniroute serve",
"authRequired": "Kinakailangan ang authentication. Itakda ang OMNIROUTE_API_KEY o patakbuhin ang: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] isasagawa sana ang {action}",
"cancelled": "Kinansela.",
"jsonOpt": "I-output bilang JSON",
"yesOpt": "Laktawan ang prompt sa pagkumpirma"
"yesOpt": "Laktawan ang prompt sa pagkumpirma",
"positiveIntegerRequired": "Ang limitasyon ay dapat na isang positibong integer."
},
"setup": {
"title": "Pag-setup ng OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Limit musi być dodatnią liczbą całkowitą.",
"error": "Błąd: {message}",
"serverOffline": "Serwer OmniRoute jest offline. Uruchom: omniroute serve",
"authRequired": "Wymagane uwierzytelnienie. Ustaw OMNIROUTE_API_KEY lub uruchom: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[symulacja] wykonałoby: {action}",
"cancelled": "Anulowano.",
"jsonOpt": "Wyjście jako JSON",
"yesOpt": "Pomiń potwierdzenie"
"yesOpt": "Pomiń potwierdzenie",
"positiveIntegerRequired": "Limit musi być dodatnią liczbą całkowitą."
},
"setup": {
"title": "Konfiguracja OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "O limite deve ser um número inteiro positivo.",
"error": "Erro: {message}",
"serverOffline": "Servidor OmniRoute offline. Inicie com: omniroute serve",
"authRequired": "Autenticação necessária. Configure OMNIROUTE_API_KEY ou execute: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulação] faria: {action}",
"cancelled": "Cancelado.",
"jsonOpt": "Saída em JSON",
"yesOpt": "Pular confirmação"
"yesOpt": "Pular confirmação",
"positiveIntegerRequired": "O limite deve ser um número inteiro positivo."
},
"setup": {
"title": "Configuração do OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "O limite deve ser um número inteiro positivo.",
"error": "Erro: {message}",
"serverOffline": "O servidor OmniRoute está offline. Inicie com: omniroute serve",
"authRequired": "Autenticação necessária. Defina OMNIROUTE_API_KEY ou execute: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulação] faria: {action}",
"cancelled": "Cancelado.",
"jsonOpt": "Saída em JSON",
"yesOpt": "Ignorar confirmação"
"yesOpt": "Ignorar confirmação",
"positiveIntegerRequired": "O limite deve ser um número inteiro positivo."
},
"setup": {
"title": "Configuração do OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Limita trebuie să fie un număr întreg pozitiv.",
"error": "Eroare: {message}",
"serverOffline": "Serverul OmniRoute este offline. Porniți cu: omniroute serve",
"authRequired": "Autentificare necesară. Setați OMNIROUTE_API_KEY sau rulați: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulare] ar face: {action}",
"cancelled": "Anulat.",
"jsonOpt": "Ieșire ca JSON",
"yesOpt": "Omite confirmarea"
"yesOpt": "Omite confirmarea",
"positiveIntegerRequired": "Limita trebuie să fie un număr întreg pozitiv."
},
"setup": {
"title": "Configurare OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Лимит должен быть положительным целым числом.",
"error": "Ошибка: {message}",
"serverOffline": "Сервер OmniRoute отключён. Запустите: omniroute serve",
"authRequired": "Требуется аутентификация. Установите OMNIROUTE_API_KEY или выполните: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[симуляция] выполнит: {action}",
"cancelled": "Отменено.",
"jsonOpt": "Вывод в формате JSON",
"yesOpt": "Пропустить подтверждение"
"yesOpt": "Пропустить подтверждение",
"positiveIntegerRequired": "Лимит должен быть положительным целым числом."
},
"setup": {
"title": "Настройка OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "සීමාව ධන නිඛිලයක් විය යුතුය.",
"error": "දෝෂය: {message}",
"serverOffline": "OmniRoute සේවාදායකය නොබැඳියි. එය ආරම්භ කිරීමට: omniroute serve",
"authRequired": "සත්යාපනය අවශ්යයි. OMNIROUTE_API_KEY සකසන්න හෝ මෙය ධාවනය කරන්න: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} කරනු ඇත",
"cancelled": "අවලංගු කරන ලදී.",
"jsonOpt": "JSON ලෙස ප්රතිදානය කරන්න",
"yesOpt": "තහවුරු කිරීමේ විමසුම මඟ හරින්න"
"yesOpt": "තහවුරු කිරීමේ විමසුම මඟ හරින්න",
"positiveIntegerRequired": "සීමාව ධන නිඛිලයක් විය යුතුය."
},
"setup": {
"title": "OmniRoute පිහිටුවීම",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Limit musí byť kladné celé číslo.",
"error": "Chyba: {message}",
"serverOffline": "Server OmniRoute je offline. Spustite: omniroute serve",
"authRequired": "Vyžaduje sa overenie. Nastavte OMNIROUTE_API_KEY alebo spustite: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulácia] by vykonalo: {action}",
"cancelled": "Zrušené.",
"jsonOpt": "Výstup ako JSON",
"yesOpt": "Preskočiť potvrdenie"
"yesOpt": "Preskočiť potvrdenie",
"positiveIntegerRequired": "Limit musí byť kladné celé číslo."
},
"setup": {
"title": "Nastavenie OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Omejitev mora biti pozitivno celo število.",
"error": "Napaka: {message}",
"serverOffline": "Strežnik OmniRoute ne deluje. Zaženite ga z ukazom: omniroute serve",
"authRequired": "Zahtevano je preverjanje pristnosti. Nastavite OMNIROUTE_API_KEY ali zaženite: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[poskusni zagon] izvedlo bi se dejanje: {action}",
"cancelled": "Preklicano.",
"jsonOpt": "Izpis v obliki JSON",
"yesOpt": "Preskoči poziv za potrditev"
"yesOpt": "Preskoči poziv za potrditev",
"positiveIntegerRequired": "Omejitev mora biti pozitivno celo število."
},
"setup": {
"title": "Nastavitev OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Ограничење мора бити позитиван цео број.",
"error": "Грешка: {message}",
"serverOffline": "OmniRoute сервер је offline. Покрените га помоћу: omniroute serve",
"authRequired": "Потребна је аутентификација. Подесите OMNIROUTE_API_KEY или покрените: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[пробно покретање] би {action}",
"cancelled": "Отказано.",
"jsonOpt": "Прикажи као JSON",
"yesOpt": "Прескочи потврду"
"yesOpt": "Прескочи потврду",
"positiveIntegerRequired": "Ограничење мора бити позитиван цео број."
},
"setup": {
"title": "OmniRoute подешавање",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Gränsen måste vara ett positivt heltal.",
"error": "Fel: {message}",
"serverOffline": "OmniRoute-servern är offline. Starta med: omniroute serve",
"authRequired": "Autentisering krävs. Ange OMNIROUTE_API_KEY eller kör: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simulering] skulle: {action}",
"cancelled": "Avbruten.",
"jsonOpt": "Utdata som JSON",
"yesOpt": "Hoppa över bekräftelse"
"yesOpt": "Hoppa över bekräftelse",
"positiveIntegerRequired": "Gränsen måste vara ett positivt heltal."
},
"setup": {
"title": "OmniRoute-konfiguration",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Kikomo lazima kiwe nambari kamili chanya.",
"error": "Hitilafu: {message}",
"serverOffline": "Seva ya OmniRoute haiko mtandaoni. Ianzishe kwa: omniroute serve",
"authRequired": "Uthibitishaji unahitajika. Weka OMNIROUTE_API_KEY au endesha: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] ingefanya {action}",
"cancelled": "Imeghairiwa.",
"jsonOpt": "Toa matokeo kama JSON",
"yesOpt": "Ruka kidokezo cha uthibitishaji"
"yesOpt": "Ruka kidokezo cha uthibitishaji",
"positiveIntegerRequired": "Kikomo lazima kiwe nambari kamili chanya."
},
"setup": {
"title": "Usanidi wa OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "வரம்பு நேர்மறை முழு எண்ணாக இருக்க வேண்டும்.",
"error": "பிழை: {message}",
"serverOffline": "OmniRoute சேவையகம் ஆஃப்லைனில் உள்ளது. இதைக் கொண்டு தொடங்கவும்: omniroute serve",
"authRequired": "அங்கீகாரம் தேவை. OMNIROUTE_API_KEY-ஐ அமைக்கவும் அல்லது இதை இயக்கவும்: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} செய்யப்படும்",
"cancelled": "ரத்துசெய்யப்பட்டது.",
"jsonOpt": "JSON ஆக வெளியிடு",
"yesOpt": "உறுதிப்படுத்தல் கேள்வியைத் தவிர்"
"yesOpt": "உறுதிப்படுத்தல் கேள்வியைத் தவிர்",
"positiveIntegerRequired": "வரம்பு நேர்மறை முழு எண்ணாக இருக்க வேண்டும்."
},
"setup": {
"title": "OmniRoute அமைப்பு",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "పరిమితి తప్పనిసరిగా ధనాత్మక పూర్ణాంకం అయి ఉండాలి.",
"error": "లోపం: {message}",
"serverOffline": "OmniRoute సర్వర్ ఆఫ్లైన్లో ఉంది. దీన్ని ఇలా ప్రారంభించండి: omniroute serve",
"authRequired": "ప్రమాణీకరణ అవసరం. OMNIROUTE_API_KEY సెట్ చేయండి లేదా దీన్ని అమలు చేయండి: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} చేస్తుంది",
"cancelled": "రద్దు చేయబడింది.",
"jsonOpt": "JSONగా అవుట్పుట్ చేయండి",
"yesOpt": "నిర్ధారణ ప్రాంప్ట్ను దాటవేయండి"
"yesOpt": "నిర్ధారణ ప్రాంప్ట్ను దాటవేయండి",
"positiveIntegerRequired": "పరిమితి తప్పనిసరిగా ధనాత్మక పూర్ణాంకం అయి ఉండాలి."
},
"setup": {
"title": "OmniRoute సెటప్",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "ขีดจำกัดต้องเป็นจำนวนเต็มบวก",
"error": "ข้อผิดพลาด: {message}",
"serverOffline": "เซิร์ฟเวอร์ OmniRoute ออฟไลน์ เริ่มด้วย: omniroute serve",
"authRequired": "ต้องการการยืนยันตัวตน ตั้งค่า OMNIROUTE_API_KEY หรือรัน: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[จำลอง] จะทำ: {action}",
"cancelled": "ยกเลิกแล้ว",
"jsonOpt": "ส่งออกเป็น JSON",
"yesOpt": "ข้ามการยืนยัน"
"yesOpt": "ข้ามการยืนยัน",
"positiveIntegerRequired": "ขีดจำกัดต้องเป็นจำนวนเต็มบวก"
},
"setup": {
"title": "ตั้งค่า OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Limit pozitif bir tam sayı olmalıdır.",
"error": "Hata: {message}",
"serverOffline": "OmniRoute sunucusu çevrimdışı. Başlatın: omniroute serve",
"authRequired": "Kimlik doğrulama gerekli. OMNIROUTE_API_KEY ayarlayın veya çalıştırın: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[simülasyon] yapılacaktı: {action}",
"cancelled": "İptal edildi.",
"jsonOpt": "JSON olarak çıktı",
"yesOpt": "Onayı atla"
"yesOpt": "Onayı atla",
"positiveIntegerRequired": "Limit pozitif bir tam sayı olmalıdır."
},
"setup": {
"title": "OmniRoute Kurulumu",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Ліміт має бути додатним цілим числом.",
"error": "Помилка: {message}",
"serverOffline": "Сервер OmniRoute відключено. Запустіть: omniroute serve",
"authRequired": "Потрібна автентифікація. Встановіть OMNIROUTE_API_KEY або виконайте: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[симуляція] виконає: {action}",
"cancelled": "Скасовано.",
"jsonOpt": "Вивести у форматі JSON",
"yesOpt": "Пропустити підтвердження"
"yesOpt": "Пропустити підтвердження",
"positiveIntegerRequired": "Ліміт має бути додатним цілим числом."
},
"setup": {
"title": "Налаштування OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "حد ایک مثبت صحیح عدد ہونی چاہیے۔",
"error": "خرابی: {message}",
"serverOffline": "OmniRoute سرور آف لائن ہے۔ اسے اس کمانڈ سے شروع کریں: omniroute serve",
"authRequired": "توثیق درکار ہے۔ OMNIROUTE_API_KEY سیٹ کریں یا یہ کمانڈ چلائیں: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[آزمائشی اجرا] {action} کیا جاتا",
"cancelled": "منسوخ کر دیا گیا۔",
"jsonOpt": "JSON کی صورت میں آؤٹ پٹ دیں",
"yesOpt": "تصدیقی پیغام کو چھوڑ دیں"
"yesOpt": "تصدیقی پیغام کو چھوڑ دیں",
"positiveIntegerRequired": "حد ایک مثبت صحیح عدد ہونی چاہیے۔"
},
"setup": {
"title": "OmniRoute سیٹ اپ",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Limit musbat butun son boʻlishi kerak.",
"error": "Xato: {message}",
"serverOffline": "OmniRoute serveri oflayn. Uni quyidagi buyruq bilan ishga tushiring: omniroute serve",
"authRequired": "Autentifikatsiya talab qilinadi. OMNIROUTE_API_KEY ni sozlang yoki quyidagi buyruqni bajaring: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] {action} bajarilgan bo‘lardi",
"cancelled": "Bekor qilindi.",
"jsonOpt": "JSON formatida chiqarish",
"yesOpt": "Tasdiqlash so‘rovini o‘tkazib yuborish"
"yesOpt": "Tasdiqlash so‘rovini o‘tkazib yuborish",
"positiveIntegerRequired": "Limit musbat butun son boʻlishi kerak."
},
"setup": {
"title": "OmniRoute sozlamalari",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Giới hạn phải là số nguyên dương.",
"error": "Lỗi: {message}",
"serverOffline": "Máy chủ OmniRoute đang offline. Khởi động với: omniroute serve",
"authRequired": "Cần xác thực. Đặt OMNIROUTE_API_KEY hoặc chạy: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[mô phỏng] sẽ: {action}",
"cancelled": "Đã hủy.",
"jsonOpt": "Xuất dưới dạng JSON",
"yesOpt": "Bỏ qua xác nhận"
"yesOpt": "Bỏ qua xác nhận",
"positiveIntegerRequired": "Giới hạn phải là số nguyên dương."
},
"setup": {
"title": "Thiết lập OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "Iye ààlà gbọ́dọ̀ jẹ́ odidi nọ́ńbà rere.",
"error": "Àṣìṣe: {message}",
"serverOffline": "Sẹ́fà OmniRoute kò sí lórí ayélujára. Bẹ̀rẹ̀ rẹ̀ pẹ̀lú: omniroute serve",
"authRequired": "Ìfàṣẹsí jẹ́ dandan. Ṣètò OMNIROUTE_API_KEY tàbí ṣiṣẹ́: omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "[dry-run] yóò {action}",
"cancelled": "A ti fagilé.",
"jsonOpt": "Ṣe àbájáde gẹ́gẹ́ bí JSON",
"yesOpt": "Fo ìbéèrè ìmúdájú"
"yesOpt": "Fo ìbéèrè ìmúdájú",
"positiveIntegerRequired": "Iye ààlà gbọ́dọ̀ jẹ́ odidi nọ́ńbà rere."
},
"setup": {
"title": "Ìṣètò OmniRoute",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "限制必须是正整数。",
"error": "错误:{message}",
"serverOffline": "OmniRoute 服务器已离线。请启动:omniroute serve",
"authRequired": "需要认证。请设置 OMNIROUTE_API_KEY 或运行:omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "【模拟】将执行:{action}",
"cancelled": "已取消。",
"jsonOpt": "以 JSON 格式输出",
"yesOpt": "跳过确认"
"yesOpt": "跳过确认",
"positiveIntegerRequired": "限制必须是正整数。"
},
"setup": {
"title": "OmniRoute 设置",

View File

@@ -1,6 +1,5 @@
{
"common": {
"positiveIntegerRequired": "限制必須是正整數。",
"error": "錯誤:{message}",
"serverOffline": "OmniRoute 伺服器已離線。請啟動:omniroute serve",
"authRequired": "需要認證。請設定 OMNIROUTE_API_KEY 或執行:omniroute setup",
@@ -13,7 +12,8 @@
"dryRun": "【模擬】將執行:{action}",
"cancelled": "已取消。",
"jsonOpt": "以 JSON 格式輸出",
"yesOpt": "跳過確認"
"yesOpt": "跳過確認",
"positiveIntegerRequired": "限制必須是正整數。"
},
"setup": {
"title": "OmniRoute 設定",

View File

@@ -0,0 +1 @@
- feat(routing): allow scoping task-aware routing to specific target or excluded models/combos via `targetModels` and `excludedModels` in TaskRoutingConfig (#20294)

View File

@@ -0,0 +1 @@
- Merge verified coverage shards in their original reporting order and write a single aggregate for c8, reducing temporary disk use on CI runners.

View File

@@ -0,0 +1 @@
- Move the Firecrawl cloud scrape call and the dashboard key probe from `/v1/scrape` to `/v2/scrape` before the 2026-12-10 v1 shutdown (#19636): a CSS `wait_for_selector` becomes a v2 `wait` action, a plain integer becomes the `waitFor` delay in milliseconds (capped at 60000), and `maxDepth` is no longer sent to the cloud endpoint. Self-hosted base URLs stay on `/v1/scrape` with the previous body.

View File

@@ -0,0 +1 @@
- **fix(providers):** preserve multi-key JSON payloads and solitary thought objects in Gemini leak filter instead of stripping structured responses to 0 chars ([#19805](https://github.com/cheaper-inference/OmniRoute/issues/19805)) — thanks @ctrindade0503

View File

@@ -0,0 +1 @@
- **fix(translator):** translate Responses `compaction` input items carrying readable content or text into standard Chat messages (assistant summaries keep `output_text` parts) instead of rejecting them. Previously, compaction items without `ocx1:` bridge encryption were rejected with `400 unsupported_feature`, causing combo fallbacks to fail for Responses-native clients. Remote compaction (`compaction_trigger`) still fails explicitly on Chat Completions targets, since they cannot return the required `compaction` output item ([#19730](https://github.com/cheaper-inference/OmniRoute/issues/19730)).

View File

@@ -0,0 +1 @@
- **auto-combo**: Count the `import … from`, `SELECT … FROM` and `${…}` code indicators in `detectCodeComplexity` with a linear scan, and stop the `if … then` pattern in `detectReasoningDepth` from backtracking across long whitespace runs, eliminating quadratic backtracking on long lines without dropping long valid spans (#19881)

View File

@@ -0,0 +1 @@
- **fix(api):** derived model display names drop dash-separated release dates, so `gpt-5-2025-08-07` reads `GPT-5` instead of `GPT-5.2025 08.07`. (fixes #20070) ([#20071](https://github.com/cheaper-inference/OmniRoute/pull/20071))

View File

@@ -0,0 +1 @@
- **fix(sse):** Consider fallback-excluded accounts with short retryable model lockouts when checking remaining accounts for quota exhaustion, returning the short lockout cooldown instead of a multi-hour quota reset; an excluded account that is in an account cooldown or whose own quota for the model is exhausted is still ignored ([#20084](https://github.com/cheaper-inference/OmniRoute/pull/20084), [#20083](https://github.com/cheaper-inference/OmniRoute/issues/20083)) — thanks @bojackduy and @rafacpti23

View File

@@ -0,0 +1 @@
- Roll over compact count formatting (`fmtCompact`) to `M` and `B` at rounding boundaries (e.g. 999,950 to `1.0M` and 999,999,999 to `1.0B`) to prevent displaying `1000.0K` or `1000.0M` in analytics and dashboard counts (#20068).

View File

@@ -0,0 +1 @@
- **fix(gamification):** One XP award (audit row, action counter, level row and the global, weekly and monthly leaderboard scores) is now a single SQLite transaction instead of six separate commits per authenticated request, and a failure part-way no longer leaves XP without a score. ([#20226](https://github.com/cheaper-inference/OmniRoute/pull/20226))

View File

@@ -0,0 +1 @@
- **fix(usage):** A usage row that arrives late for a day the retention job already rolled up and deleted is now added to that day's summary. Before, the next rollup replaced the day's totals with the late row alone and the earlier requests vanished from the analytics. The job records the day it purged to and the highest row id it counted, in one settings row (no migration). ([#20226](https://github.com/cheaper-inference/OmniRoute/pull/20226))

View File

@@ -0,0 +1 @@
- **fix(usage):** A usage row whose write meets a locked database (for example a second writer process on the same file) is now retried on a backoff for about 31 seconds before it is dropped, not once after one second, so a billed request no longer ends with no usage row. ([#20226](https://github.com/cheaper-inference/OmniRoute/pull/20226))

View File

@@ -0,0 +1 @@
- Allow standard-speed Grok 4.7 variants (`medium`, `low`, `xhigh`) and bare effort aliases to use standard speed by omitting `ModelDetails` and setting `reasoning_effort`, preventing Cursor from falling back to `grok-4.7-high-fast` (#20077).

View File

@@ -0,0 +1 @@
- Skip per-request long-context pricing tier on aggregated window token sums in per-key USD usage limits (`apiKeyUsageLimits.ts`), preventing false threshold trips from overstating spend (~5x) and prematurely blocking keys (#20153).

View File

@@ -0,0 +1 @@
- **fix(providers):** remove the deprecated `--quiet` flag from the Auggie CLI invocation arguments ([#20250](https://github.com/cheaper-inference/OmniRoute/issues/20250)). Auggie CLI 1.2+ removed the `--quiet` option, which previously caused all requests to fail with `Error: Unknown option: --quiet` and a 502 status code.

View File

@@ -0,0 +1 @@
- **fix(callLogs):** guard call-log artifact worker path resolution when build-time `import.meta.url` is not a valid local file URL on Windows ([#20449](https://github.com/cheaper-inference/OmniRoute/issues/20449))

View File

@@ -0,0 +1 @@
- **fix(release):** `scripts/release/sync-next-cycle.mjs` no longer pushes the sync-back straight to the release branch, which ruleset 21899981 refuses on the default branch: it pushes the merge commit to `chore/sync-back-main-<sha12>` and opens a PR into the release branch (land it as a merge commit), re-runs find the open PR instead of creating another, and the old push stays behind `--direct-push` ([#20645](https://github.com/cheaper-inference/OmniRoute/pull/20645))

View File

@@ -0,0 +1 @@
- Apply the same account rule to the text form of the usage command (`@@om-usage`): keys without `self:account-quota` or a management scope see only their personal quota, and the shared provider accounts are not read for them.

View File

@@ -0,0 +1 @@
- **fix(security):** Marketplace plugin installs need a management credential in every auth mode, and plugin config writes only accept the keys the plugin declares in its config schema (a plugin without a schema has no writable config)

View File

@@ -1 +0,0 @@
- **fix(api):** The API-only port (`API_PORT`) refuses a request path that contains a dot segment (`.` or `..`, literal or percent-encoded) or a fragment marker before it applies its route allowlist, for plain requests and WebSocket upgrades. The port relays a path exactly as it validated it ([#20793](https://github.com/cheaper-inference/OmniRoute/pull/20793))

View File

@@ -0,0 +1 @@
- **fix(security):** GitHub Copilot Responses-only inference, model display names and the Context7 library id check use linear regexes, so a long crafted model or library id no longer blocks the event loop for seconds (CodeQL js/polynomial-redos #1325, #1324, #1296)

View File

@@ -0,0 +1 @@
- **fix(ci):** Preserve all eight V8 coverage shards with lossless transport, verified manifests and explicit checkout-path relocation before the native c8 report. Bind generated TSX code and source maps from exclusive producer caches before projecting a proven filename layout, and archive the preparation receipt. Support partial reruns by selecting successful producer jobs and immutable artifact IDs while retaining their original attempts. Reject incomplete, duplicate, corrupted or unproven evidence and empty coverage without changing coverage thresholds.

View File

@@ -0,0 +1 @@
- **test(providers):** regression tests for the Cloudflare Workers AI "Check" button sending the Account ID to `/api/providers/validate` (#19304, fixed in #19384) ([#19851](https://github.com/cheaper-inference/OmniRoute/pull/19851)) — thanks @rafacpti23

View File

@@ -0,0 +1 @@
- **chore(ci):** retire the Mergify merge queue: `.mergify.yml` drops the `release` and `relay-integration` queues, the auto-merge label condition and the label-cleanup rule, and refuses the Mergify commands that merge or rewrite a pull request; rail gate G11 of `release:dry-run-lts-cut` now checks omni-queue (valid config, release branch managed, mode `live`, label present) ([#20616](https://github.com/cheaper-inference/OmniRoute/pull/20616))

View File

@@ -0,0 +1 @@
- **fix(ci):** SonarCloud gets `coverage/lcov.info` on pull requests again — the coverage merge skipped the lcov reporter on PRs since #18336, so every PR showed 0.0% coverage on new code; the SonarQube job now also fails clearly when the file is missing ([#20769](https://github.com/cheaper-inference/OmniRoute/pull/20769))

View File

@@ -1,6 +1,7 @@
{
"_comment": "Allowlist anti-slopsquatting (check-deps.mjs). Toda dep nova exige adicao EXPLICITA aqui apos verificar que e legitima.",
"_justifications": {
"@bcoe/v8-coverage": "V8 coverage report utilities (bcoe/v8-coverage), pinned at 1.0.2 for the development-only shard aggregation in PR #20515. The npm tarball and SHA-512 integrity match the existing transitive c8 dependency on both base branches.",
"@msgpack/msgpack": "Official MessagePack JavaScript implementation (msgpack/msgpack-javascript, ISC), required by Fal's documented specialized realtime protocol. Version 3.1.3 name, repository, license and SHA-512 tarball integrity verified against the npm registry on 2026-11-03 for PR #18849; no additional runtime dependency is introduced by this correction.",
"@agentclientprotocol/sdk": "Official Agent Client Protocol TypeScript SDK (agentclientprotocol/typescript-sdk, Apache-2.0). Exact 1.4.0 registry tarball and integrity verified for the registered native Gemini ACP launcher.",
"@fontsource/ibm-plex-mono": "Self-hosted Keak type ramp for the vendored CI UI Kit (fontsource, OFL fonts; same no-CDN reasoning as Material Symbols #3695). KEA-7886 — CI UI Kit runtime dependency.",
@@ -34,6 +35,7 @@
"@atjsh/llmlingua-2",
"@aws-sdk/client-bedrock-runtime",
"@axe-core/playwright",
"@bcoe/v8-coverage",
"@cyclonedx/cyclonedx-npm",
"@dnd-kit/core",
"@dnd-kit/sortable",

View File

@@ -157,12 +157,13 @@
"dedicatedGate": true
},
"codeqlAlerts": {
"value": 6,
"value": 103,
"direction": "down",
"dedicatedGate": true,
"_rebaseline_2026_08_06_base_grew": "Base branch file-size drift: translator-openai-to-gemini.test.ts grew 1619->1622 (test assertions for Gemini translator compatibility). CodeQL alert (js/insufficient-password-hash in raycast.ts) is pre-existing base-red; incremented baseline to match.",
"_rebaseline_2026_08_10_9940_fingerprint": "CodeQL base-red (green-prs sweep, issue #9985): 2nd js/insufficient-password-hash alert at src/shared/middleware/chatBodyAdmission.ts:265,269 introduced by #9940 (per-connection virtual admission lanes). Both are API-key/bearer FINGERPRINTS (createHash('sha256') truncated to 16-hex admission-lane key), not password VERIFICATION — false-positive class for this rule. Reproduces on release/v3.8.50 tip. Owner-authorized rebaseline 1->2; revisit at v3.9.0.",
"_rebaseline_2026_08_11_merge_storm_drift": "2 -> 9. Drift from the 2026-08-11 authorized merge storm (99 PRs into release/v3.8.50): js/insufficient-password-hash in open-sse/executors/chatgpt-web-codex/storageState.ts x3 + conol-web.ts (PRs #8949/#8974 — Chromium browser-profile credential storage SKUs that CodeQL flags under the password-hash rule; same fingerprint/credential-cache false-positive class already rebaselined in #9940/2026-08-06), js/stack-trace-exposure (chatgpt-web-codex.ts, #8949 debug logging), js/double-escaping (environment.ts, #8949), js/insecure-randomness (tinycms.ts, #9435). None introduced by this base-fix PR. Owner-authorized rebaseline (2026-08-11); revisit hardening at v3.9.0."
"_rebaseline_2026_08_11_merge_storm_drift": "2 -> 9. Drift from the 2026-08-11 authorized merge storm (99 PRs into release/v3.8.50): js/insufficient-password-hash in open-sse/executors/chatgpt-web-codex/storageState.ts x3 + conol-web.ts (PRs #8949/#8974 — Chromium browser-profile credential storage SKUs that CodeQL flags under the password-hash rule; same fingerprint/credential-cache false-positive class already rebaselined in #9940/2026-08-06), js/stack-trace-exposure (chatgpt-web-codex.ts, #8949 debug logging), js/double-escaping (environment.ts, #8949), js/insecure-randomness (tinycms.ts, #9435). None introduced by this base-fix PR. Owner-authorized rebaseline (2026-08-11); revisit hardening at v3.9.0.",
"_rebaseline_2026_11_20_codeql_2_27_5": "6 -> 103. Tool upgrade, not code: the default setup moved CodeQL 2.27.4 -> 2.27.5 on 2026-11-20 and the release/v3.8.55 JS analysis went 236 -> 339 results with the same 87 rules (760357c4 only touched a test file). 101 alerts were created together at 14:07:12Z (path-injection 34, polynomial-redos 30, request-forgery 22, unvalidated-dynamic-method-call 6, regex-injection 6, resource-exhaustion 3). Owner-authorized temporary ceiling (2026-11-20) to unblock merges while the security wave triages them (dismiss false positives with justification, fix real defects); a follow-up PR lowers the value to the measured count."
},
"secretFindings": {
"_note": "Zeroed 2026-07-13 (WS6/D3): the 3 frozen generic-api-key FPs are allowlisted with justification in .gitleaks.toml — any NEW finding regresses the ratchet.",

View File

@@ -348,5 +348,6 @@
"@omniroute/opencode-plugin/tests/log-level.test.ts": "the v1 plugin no longer fetches /api/combos/auto on refresh; the retired fetcher 404 test and its import are removed with the source (21 to 19). Remaining level coverage unchanged.",
"@omniroute/opencode-plugin/tests/config-shim.test.ts": "the v1 plugin no longer fetches /api/combos/auto on refresh; the retired twin-wins case and its fixtures are removed with the static publication block (162 to 159). Remaining builder coverage unchanged.",
"tests/unit/stepfun-mono-fallback-and-sidebar-hydration-7743.test.ts": "ec27d84e (KEA-7886, F4, 2026-10-21): the legacy DashboardLayout and its synchronous localStorage collapse initializer were removed; the one dropped assert pinned that initializer. The replacement block pins the kit shell contract instead: no localStorage read in the layout files and the server passing the ci_sidebar_state cookie as sidebarDefaultOpen (3 new asserts in place of the old structure). Net count 9 -> 8 is the realignment, not a weakening. Release-green base-red #17219 (2026-10-24).",
"tests/unit/ui/rtl-logical-classes.test.tsx": "ec27d84e (KEA-7886, F4, 2026-10-21): the legacy mobile sidebar drawer (.dashboard-sidebar-mobile, start-0/-translate-x-full RTL rules) was removed with the legacy shell; its six drawer cases were replaced by the Kit shell block in the same file, which asserts the kit Sidebar Sheet anchoring by side. Net 21 -> 19 is the realignment, not a weakening. Release-green base-red #17219 (2026-10-24)."
"tests/unit/ui/rtl-logical-classes.test.tsx": "ec27d84e (KEA-7886, F4, 2026-10-21): the legacy mobile sidebar drawer (.dashboard-sidebar-mobile, start-0/-translate-x-full RTL rules) was removed with the legacy shell; its six drawer cases were replaced by the Kit shell block in the same file, which asserts the kit Sidebar Sheet anchoring by side. Net 21 -> 19 is the realignment, not a weakening. Release-green base-red #17219 (2026-10-24).",
"tests/unit/mergify-queue-config.test.ts": "PR #20616 (2026-11-19): the owner retired the Mergify merge queue, so .mergify.yml no longer carries queue_rules, merge_protections_settings or pull_request_rules. The 10 tests that pinned the release and relay-integration queue rules (squash method, label/draft/conflict conditions, the fail-closed anchor check, paid-tier and deprecated keys, integration routing and admission) have no surface left to assert. They are replaced by 5 tests of what remains: the file holds only commands_restrictions, no queue or auto-merge key exists, each of the 7 commands that merge or rewrite a pull request keeps an unsatisfiable condition list, and the two rules that outlive Mergify (checks timeout >= 2x the measured quality.yml p95; Gate / CI, Gate / Quality and Merge integrity required) are now asserted against omni-queue's config. The replacement queue's own admission contract is pinned in tests/unit/merge-queue/. Net 28 -> 11 is a retired surface, not a weakening. Prune after v3.8.55 merges to main."
}

View File

@@ -47,6 +47,12 @@ separate administrative change; adding these jobs does not itself protect a bran
### Merge queue
> **2026-11-19: the Mergify merge queue is retired** (owner's decision). `.mergify.yml` no
> longer defines a queue and refuses the Mergify commands that merge or rewrite a pull request.
> Release PRs are merged by hand under the repository ruleset "Require green gates on the active
> release" (`Gate / CI` + `Gate / Quality`) until omni-queue runs in live mode, and through
> omni-queue after that ([OMNI_QUEUE.md](../ops/OMNI_QUEUE.md)). The workflow handling of Mergify drafts described below is still in `ci.yml` and `quality.yml`, but no Mergify draft is opened any more.
The `queue` label sends a PR to the Mergify queue (`.mergify.yml`). Mergify opens a draft PR on
a `mergify/merge-queue/` branch, CI runs the full selection there, and the original PR merges
when `Gate / CI`, `Gate / Quality` and `Merge integrity (changelog + generated skills)` pass.

View File

@@ -92,18 +92,19 @@ All endpoints require management auth (`requireManagementAuth`) **and** are
loopback-only — `/api/plugins` and `/api/plugins/` are listed in
`LOCAL_ONLY_API_PREFIXES` (`src/server/authz/routeGuard.ts`).
| Endpoint | Method | Description |
| -------------------------------- | ------ | --------------------------------------------------- |
| `/api/plugins` | GET | List installed plugins (optional `?status=` filter) |
| `/api/plugins` | POST | Install a plugin from the plugin sources directory |
| `/api/plugins/scan` | POST | Scan the plugin directory and register new plugins |
| `/api/plugins/marketplace` | GET | List marketplace catalog entries |
| `/api/plugins/[name]` | GET | Get installed plugin details |
| `/api/plugins/[name]` | DELETE | Uninstall a plugin |
| `/api/plugins/[name]/activate` | POST | Activate (load + register hooks) |
| `/api/plugins/[name]/deactivate` | POST | Deactivate (fire `onDeactivate`, unregister hooks) |
| `/api/plugins/[name]/config` | GET | Get plugin config + config schema |
| `/api/plugins/[name]/config` | PUT | Update plugin config (validated against schema) |
| Endpoint | Method | Description |
| ---------------------------------- | ------ | --------------------------------------------------- |
| `/api/plugins` | GET | List installed plugins (optional `?status=` filter) |
| `/api/plugins` | POST | Install a plugin from the plugin sources directory |
| `/api/plugins/scan` | POST | Scan the plugin directory and register new plugins |
| `/api/plugins/marketplace` | GET | List marketplace catalog entries |
| `/api/plugins/marketplace/install` | POST | Install a marketplace plugin by name |
| `/api/plugins/[name]` | GET | Get installed plugin details |
| `/api/plugins/[name]` | DELETE | Uninstall a plugin |
| `/api/plugins/[name]/activate` | POST | Activate (load + register hooks) |
| `/api/plugins/[name]/deactivate` | POST | Deactivate (fire `onDeactivate`, unregister hooks) |
| `/api/plugins/[name]/config` | GET | Get plugin config + config schema |
| `/api/plugins/[name]/config` | PUT | Update plugin config (validated against schema) |
The `GET /api/plugins` `status` filter accepts one of
`installed` / `active` / `inactive` / `error`. An invalid value returns `400`.
@@ -137,7 +138,8 @@ the response is `201` with the installed plugin row.
Unlike the other plugin routes, this one requires the management credential (a
dashboard session or a manage-scoped API key) even when login is disabled
(`requireLogin=false`): installing code is never an anonymous action.
(`requireLogin=false`): installing code is never an anonymous action. The same
applies to `POST /api/plugins/marketplace/install` (body `{ "name": "<plugin>" }`).
### Browse the marketplace
@@ -155,10 +157,13 @@ curl -X PUT http://localhost:20128/api/plugins/my-plugin/config \
-d '{ "config": { "level": "debug", "maxItems": 100 } }'
```
`PUT .../config` validates each provided value against the plugin's
`configSchema` (declared in the manifest): `number` fields honor `min`/`max`,
`select` fields must match the declared `enum`. Keys not present in the schema
are allowed through.
`PUT .../config` validates the body against the plugin's `configSchema`
(declared in the manifest) with `validatePluginConfig()` from
`src/lib/plugins/manifest.ts`: every key must be declared in the schema, values
must match the declared type, `number` fields honor `min`/`max`, and `select`
fields must match the declared `enum`. Any violation returns `400` and nothing is
stored. A plugin that declares no `configSchema` has no configurable keys, so the
request is refused with `400` ("Plugin does not declare any configurable keys").
## Configuration

View File

@@ -19,16 +19,18 @@
### የእጩዎች መግቢያ
CI እና የጥራት ጌትስ የስራ ፍሰቶች እያንዳንዳቸው የተረጋጋ ብይን ይሰጣሉ `Gate / CI` እና `Gate / Quality`. የእነርሱ ስሪት ያለው የመግቢያ ፖሊሲ እንደ አስፈላጊነቱ ወይም እንደ ምክር ሁሉንም የወራጅ ስራዎችን ይዘረዝራል። የሚመለከተው አስፈላጊ ሥራ ሊሳካለት ይገባል፡ የጠፋ፣ የተሰረዘ፣ የተዘለለ፣ በመጠባበቅ ላይ እና ያልታወቁ ውጤቶች PASS መመስረት አይችሉም። የሚሰራ ሰነዶች-ብቻ ወይም ካታሎግ-ብቻ ምደባ የኮድ መስመርን የማይተገበር ያደርገዋል። ረቂቅ PR ተቀባይነት ያለው እጩ አይደለም። የ `hotfix` መለያ ማስረጃን አይተውም።
CI እና የጥራት ጌትስ የስራ ፍሰቶች እያንዳንዳቸው የተረጋጋ ብይን ይሰጣሉ `Gate / CI` እና `Gate / Quality`. የእነርሱ ስሪት ያለው የመግቢያ ፖሊሲ እንደ አስፈላጊነቱ ወይም እንደ ምክር ሁሉንም የወራጅ ስራዎችን ይዘረዝራል። የሚመለከተው አስፈላጊ ሥራ ስኬታማ መሆን አለበት፡ ጠፍቷል፣ የተሰረዘ፣ የተዘለለ፣ በመጠባበቅ ላይ እና ያልታወቁ ውጤቶች PASS መመስረት አይችሉም። የሚሰራ ሰነዶች-ብቻ ወይም ካታሎግ-ብቻ ምደባ የኮድ መስመርን የማይተገበር ያደርገዋል። ረቂቅ PR ተቀባይነት ያለው እጩ አይደለም። የ `hotfix` መለያ ማስረጃን አይተውም።
ሁለቱም የስራ ፍሰቶች PRs ወደ main/release ቅርንጫፎች ይሸፍናሉ፣ ወደ `main` ይገፋሉ፣ በእጅ መላኪያ እና የቡድን ውህደት ክስተቶች። ሙሉ ምርጫውን ይግፉ፣ ይላኩ እና ያዋህዱ። ወደ `release/**` የሚገፋፉ አይጀምራቸውም (2026-10-18)፡ እያንዳንዱ ለውጥ ማትሪክስ ቀድሞውንም በ PR ላይ ሰርቷል እና የተዋሃደው ጥምር የልቀት-አረንጓዴ ስራ ነው (`docs/ops/RUNNER_BOX.md` → የሚስተናገድ ሌይን)። ሹካ እና የተዋሃዱ ቡድኖች በራሳቸው የሚስተናገዱ ሯጮችን ለሚመርጡ ስራዎች የተስተናገዱ ሯጮችን ይጠቀማሉ። ከታቀደው ልቀት በፊት በቂ የተስተናገደ አቅም መረጋገጥ አለበት።
አንድ ተራ PR ፈጣን ምርጫን ያካሂዳል. የ `full-code` እና `full-code-e2e` የመግቢያ ፖሊሲ መስመሮች (E2E፣ ውህደት፣ የጥቅል ቅርስ፣ Electron ጭስ፣ Bun SQLite፣ ምህዳር እና ፕሮቶኮል ደንበኞች) በ Mergify ወረፋ ረቂቅ ወይም ሙሉ ሩጫ ላይ ብቻ ይሰራሉ `gh workflow run ci.yml --ref <branch>`.
እያንዳንዱ JSON ደረሰኝ ተመዝግቦ የወጣውን SHA፣ የስራ ሂደትን እና ሙከራን ይለያል። CLI የ checkout/event SHA አለመዛመድን ውድቅ ያደርጋል። የስራ ፍሰት ሙከራዎች የፖሊሲ አባልነትን ከፍርዱ ስራ `needs` ዝርዝር ጋር ስለሚያቆራኙ አዲስ ወይም የተወገደ መስመር በፀጥታ ሊጠፋ አይችልም። ደረሰኞቹ የራሳቸውን የስራ ሂደት ይሸፍናሉ እንጂ ማተምን፣ ማሰማራትን ወይም ነባር የአማካሪ ስካነርን ውስጣዊ ነገሮች አይሸፍኑም። በቅርንጫፍ ደንቦች ውስጥ ሁለቱንም የቼክ ስሞች ማግበር የተለየ አስተዳደራዊ ለውጥ ነው; እነዚህን ስራዎች መጨመር እራሱን ቅርንጫፍ አይከላከልም.
እያንዳንዱ JSON ደረሰኝ ተመዝግቦ የወጣውን SHA፣ የስራ ሂደትን እና ሙከራን ይለያል። CLI የ checkout/event SHA አለመዛመድን ውድቅ ያደርጋል። የስራ ፍሰት ሙከራዎች የፖሊሲ አባልነትን ከፍርዱ ስራ `needs` ዝርዝር ጋር ስለሚያቆራኙ አዲስ ወይም የተወገደ መስመር በፀጥታ እንዳይጠፋ። ደረሰኞቹ የራሳቸውን የስራ ሂደት ይሸፍናሉ እንጂ ማተምን፣ ማሰማራትን ወይም ነባር የአማካሪ ስካነርን ውስጣዊ ነገሮች አይሸፍኑም። በቅርንጫፍ ደንቦች ውስጥ ሁለቱንም የቼክ ስሞች ማግበር የተለየ አስተዳደራዊ ለውጥ ነው; እነዚህን ስራዎች መጨመር እራሱን ቅርንጫፍ አይከላከልም.
### ወረፋ አዋህድ
> **2026-11-19፡ የመርግፋይ ውህደት ወረፋ ጡረታ ወጥቷል።** (የባለቤቱ ውሳኔ). `.mergify.yml` ከአሁን በኋላ ወረፋን አይገልጽም እና የመሳብ ጥያቄን የሚያዋህዱ ወይም የሚጽፉ የ Mergify ትዕዛዞችን አይቀበልም። ልቀቅ PRs በማከማቻ ደንቡ መሠረት "በነቃ ልቀቱ ላይ አረንጓዴ በሮች ጠይቅ" (`Gate / CI` + `Gate / Quality`) omni-ወረፋ በቀጥታ ሁነታ ላይ እስኪሄድ ድረስ እና ከዚያ በኋላ በኦምኒ ወረፋ ( [OMNI_QUEUE.md](../ops/OMNI_QUEUE.md) ) ስር ይደባለቃሉ። ከዚህ በታች የተገለጹት የ Mergify ረቂቆች የስራ ፍሰት አያያዝ አሁንም በ `ci.yml` እና `quality.yml` ነው፣ ነገር ግን ምንም የ Mergify ረቂቅ ከአሁን በኋላ አልተከፈተም።
`queue` መለያው ወደ Mergify ወረፋ (`.mergify.yml`) PR ይልካል። Mergify ረቂቅ PR በ `mergify/merge-queue/` ቅርንጫፍ ላይ ይከፍታል፣ CI ሙሉውን ምርጫ እዚያ ያካሂዳል፣ እና የመጀመሪያው PR `Gate / CI`, `Gate / Quality` እና `Merge integrity (changelog + generated skills)` ሲያልፍ ይዋሃዳሉ።
Mergify የወረፋ ማጠቃለያውን ወደ ረቂቁ መግለጫ ይጽፋል፣ እና ሌሎች መተግበሪያዎችም አርትዖት ሊያደርጉት ይችላሉ። በእንደዚህ አይነት ረቂቅ ላይ `pull_request` `edited` ክስተት የራሱ የሆነ የተጓዳኝ ቡድን (`-queue-edit-<run_id>`) ስለሚወስድ የረቂቁን ትክክለኛ ሩጫ መሰረዝ አይችልም፣ እና በሩን እና ማትሪክስ ይዘላል። አሁንም የሚሄደው `Merge integrity` ብቻ ነው። የተዘለለው የጌት ስራ የተለየ የፍተሻ ስም ይይዛል፣ ምክንያቱም Mergify የተዘለለ `Gate / CI` እንደ ያልተሳካ ቼክ አንብቦ PR ስለሚያጠፋ ነው።
@@ -37,7 +39,7 @@ Mergify የወረፋ ማጠቃለያውን ወደ ረቂቁ መግለጫ ይጽ
### በተቀባይ ተቀባይ ውስጥ የተያዙ ማስረጃዎች
`scripts/quality/validate-release-acceptance.mjs` የቀረበውን እቅድ እና መግለጫዎቹን ይቀንሳል; እቅዱ ሙሉ ለሙሉ የመልቀቂያ ቧንቧን እንደሚሸፍን አያረጋግጥም. የእሱ ሪፖርቶች በግልጽ `releaseAcceptance: false` ያስቀምጣሉ፣ ምንም እንኳን ያ እቅድ `VERIFIED` ቢሆንም። የ `release-acceptance.yml` የስራ ፍሰቱ አሁንም የጥላ ዕቃዎችን ይጠቀማል እንጂ እውነተኛ ግንባታ፣ ጥቅል፣ ቡት ወይም የማስተዋወቂያ ደረሰኞች አይደለም።
`scripts/quality/validate-release-acceptance.mjs` የቀረበውን እቅድ እና መግለጫዎቹን ይቀንሳል; እቅዱ የተጠናቀቀውን የመልቀቂያ ቧንቧ የሚሸፍን መሆኑን አያረጋግጥም. የእሱ ሪፖርቶች በግልጽ `releaseAcceptance: false` ያስቀምጣሉ፣ ምንም እንኳን ያ እቅድ `VERIFIED` ቢሆንም። የ `release-acceptance.yml` የስራ ፍሰቱ አሁንም ቢሆን የጥላ ዕቃዎችን ይጠቀማል እንጂ እውነተኛ ግንባታ፣ ጥቅል፣ ቡት ወይም የማስተዋወቂያ ደረሰኞች አይደለም።
የተያዙ ማስረጃዎችን ለማረጋገጥ CLI `--evidence-root` ያስፈልገዋል። ፋይሎች እንደ `<evidence-root>/<artifact_id>/<member>` እና hashed እንደ SHA-256 ተፈትተዋል። የ PASS መዝገብ ያለ ማስረጃ፣ የጠፋ ወይም የተለወጠ ፋይል፣ ደህንነቱ ያልተጠበቀ መንገድ ወይም ሲምሊንክ ማረጋገጥን ይከለክላል። የጎደሉ ፋይሎች ስኬታማ ከሆኑ ምዝግብ ማስታወሻዎች ባዶ ጋር እኩል አይደሉም። አሁን ያሉት SHA/run/attempt ቼኮች ነጻ ሆነው ይቆያሉ፡ ተዛማጅ ባይት የቆየ ደረሰኝን ማዳን አይችልም። የፋይል ታማኝነት የአፈፃፀም ትክክለኛነት ወይም የቅርስ ማስተዋወቅ ማረጋገጫ አይደለም።
@@ -47,7 +49,7 @@ Mergify የወረፋ ማጠቃለያውን ወደ ረቂቁ መግለጫ ይጽ
የተመረጡትን ተለዋጭ ስሞች ሳትፈጽም ለመመርመር `npm run quality:scan -- --list` ወይም `npm run quality:scan:fast -- --list` ይጠቀሙ። ሯጩ የ npm መግቢያ ነጥብን ይጠራል፣ ስለዚህ የሩጫ ሰዓቱ (ከተዋቀረ Bun ጨምሮ) ተጠብቆ ይቆያል። አንጸባራቂው ከነዚያ መገለጫዎች ውጭ ተለዋጭ ስሞችን ለብቻው በተጠራ መልኩ ይመዘግባል፣ እና የጥገና ትዕዛዞች በተነባቢ-ብቻ ቅኝት መገለጫዎች የተከለከሉ ናቸው።
እነዚህ መገለጫዎች የማይንቀሳቀስ ቅኝትን ብቻ ይሸፍናሉ። የምርት ሙከራዎችን፣ ሽፋንን፣ ማሸግን፣ የውጭ ቼኮችን ወይም የእጩን ሙሉ ልቀት መቀበልን አያረጋግጡም። የስራ ፍሰት መግቢያ የተገናኘውን `config/quality/admission-policy.json` እና `scripts/quality/admission-verdict.mjs` ይጠቀማል። የመልቀቂያ-ታዛቢ መገለጫዎች ተለይተው ይቀራሉ; የሚመለከታቸውን ቼኮች እና ደረሰኞች በተናጥል ይፈትሹ። የሙሉ ተመልካቾች የማይለዋወጡ ትዕዛዞች `audit:deps`፣ ሚውቴሽን-ሙከራ ምርጫ እና የትርጉም ፍተሻዎችን ጨምሮ በ `config/quality/release-green-static-profile.json` ውስጥ ተገልፀዋል። ጫኚው የ npm ትዕዛዞችን በ package.json እና በተቀረጹ CI/Quality መግለጫዎች ላይ ያረጋግጣል። የሼል ቶከኖችን እንደ ክርክር ከማስፈጸም ይልቅ ተንሸራታትን ውድቅ ያደርጋል። የሚያስፈልግ ስካነር SKIP/INCOMPLETE ውፅዓት PASS መመስረት አይችልም። መገለጫው ውጫዊ ማግለያዎቹን ይመዘግባል እና የተስተናገደ ሽፋን፣ የሙከራ ማትሪክስ፣ ጥቅል ወይም የማሰማራት ማስረጃን አይተካም። ከታች ያለው የስድ መዝገብ ዝርዝር ዋቢ እንጂ በር በትክክል መሮጡን ማረጋገጫ አይደለም።
እነዚህ መገለጫዎች የማይንቀሳቀስ ቅኝትን ብቻ ይሸፍናሉ። የምርት ሙከራዎችን፣ ሽፋንን፣ ማሸግን፣ የውጭ ቼኮችን ወይም የእጩን ሙሉ ልቀት መቀበሉን አያረጋግጡም። የስራ ፍሰት መግቢያ የተገናኘውን `config/quality/admission-policy.json` እና `scripts/quality/admission-verdict.mjs` ይጠቀማል። የመልቀቂያ-ታዛቢ መገለጫዎች ተለይተው ይቀራሉ; የሚመለከታቸውን ቼኮች እና ደረሰኞች በተናጥል ይፈትሹ። የሙሉ ተመልካቾች የማይለዋወጡ ትዕዛዞች `audit:deps`፣ ሚውቴሽን-ሙከራ ምርጫ እና የትርጉም ፍተሻዎችን ጨምሮ በ `config/quality/release-green-static-profile.json` ውስጥ ታውጇል። ጫኚው የ npm ትዕዛዞችን በ package.json እና በተቀረጹ CI/Quality መግለጫዎች ላይ ያረጋግጣል። የሼል ቶከኖችን እንደ ክርክር ከማስፈጸም ይልቅ ተንሸራታትን ውድቅ ያደርጋል። የሚያስፈልግ ስካነር SKIP/INCOMPLETE ውፅዓት PASS መመስረት አይችልም። መገለጫው ውጫዊ ማግለያዎቹን ይመዘግባል እና የተስተናገደ ሽፋን፣ የሙከራ ማትሪክስ፣ ጥቅል ወይም የማሰማራት ማስረጃን አይተካም። ከታች ያለው የስድ መዝገብ ዝርዝር ዋቢ እንጂ በር በትክክል መሮጡን ማረጋገጫ አይደለም።
ስክሪፕቶች በ `scripts/check/` (የፖሊሲ በሮች) እና `scripts/quality/` (የራትቼ ሞተር) ስር ይኖራሉ። CI የእውነት ምንጭ `.github/workflows/ci.yml` ነው።
@@ -64,9 +66,9 @@ Mergify የወረፋ ማጠቃለያውን ወደ ረቂቁ መግለጫ ይጽ
#### የተረሱ ወንድም እህት ፈተናዎች ሪፖርት ያደርጋሉ
`npm run check:forgotten-sibling-tests` እንደ `Fast Quality Gates` የአማካሪ ደረጃ ይሰራል እና የማስመጣት ፈላጊውን ከሙከራ-ተጽእኖ ካርታው ጀርባ እንደገና ይጠቀማል። ለእያንዳንዱ የተለወጠ የምርት ሞጁል፣ የእጩው ፈተና ከመጎተት-ጥያቄ ልዩነት በማይኖርበት ጊዜ ቆራጥ የሆኑ `changed module/symbol -> static consumer -> candidate sibling test` ሰንሰለቶችን ሪፖርት ያደርጋል። የ Markdown ማጠቃለያ እና JSON ውጤት ከማንኛውም ማገድ መልቀቅ በፊት እንደ `forgotten-sibling-tests` የስራ ፍሰት ቅርስ ሆኖ እንዲቆይ ተደርጓል።
`npm run check:forgotten-sibling-tests` እንደ `Fast Quality Gates` የማማከር ደረጃ ይሰራል እና ከሙከራ-ተፅእኖ ካርታ በስተጀርባ የማስመጣት ፈላጊውን እንደገና ይጠቀማል። ለእያንዳንዱ የተለወጠ የምርት ሞጁል፣ የእጩው ፈተና ከመጎተት-ጥያቄ ልዩነት በማይኖርበት ጊዜ ቆራጥ የሆኑ `changed module/symbol -> static consumer -> candidate sibling test` ሰንሰለቶችን ሪፖርት ያደርጋል። የማርክዳው ማጠቃለያ እና JSON ውጤት ከማናቸውም የማገድ ልቀት በፊት እንደ `forgotten-sibling-tests` የስራ ፍሰት ቅርስ ሆኖ እንዲቆይ ተደርጓል።
በርሜል እንደገና ወደ ውጭ መላክ እና ተለዋዋጭ ወደ ሀገር ውስጥ መግባቶች የመፍትሄ ምርመራዎች ብቻ ናቸው; የማገድ ግኝትን ፈጽሞ አይፈጥሩም። የተገመገሙ ልዩ ሁኔታዎች በ `config/quality/forgotten-sibling-allowlist.json` ውስጥ ይኖራሉ። እያንዳንዱ ግቤት የሸማቹን እና የእጩዎችን ፈተና መሰየም፣ የተለየ ምክንያት መስጠት እና GitHub ጉዳይን ማገናኘት ወይም የመሳብ ጥያቄን ማያያዝ አለበት። የተበላሹ ምዝግቦች አልተዘጉም። ልዩ ሁኔታዎች የተሰረዘ እጩ ፈተናን ወይም `.skip`/`.todo` የሚጨምር ልዩነትን ማፈን አይችሉም። ማዳከም እና ሌሎች ጭንብል መሸፈኛዎች በተናጥል በተዘጋው `check:test-masking` በር ባለቤትነት ይቆያሉ።
በርሜል እንደገና ወደ ውጭ መላክ እና ተለዋዋጭ ወደ አገር ውስጥ መግባቶች የመፍትሄ ምርመራዎች ብቻ ናቸው; የማገድ ግኝትን ፈጽሞ አይፈጥሩም። የተገመገሙ ልዩ ሁኔታዎች በ `config/quality/forgotten-sibling-allowlist.json` ውስጥ ይኖራሉ። እያንዳንዱ ግቤት የሸማቹን እና የእጩዎችን ፈተና መሰየም፣ የተለየ ምክንያት መስጠት እና GitHub ጉዳይን ማገናኘት ወይም የመሳብ ጥያቄን ማያያዝ አለበት። የተበላሹ ምዝግቦች አልተዘጉም። ልዩ ሁኔታዎች የተሰረዘ እጩ ፈተናን ወይም `.skip`/`.todo` የሚጨምር ልዩነትን ማፈን አይችሉም። ማዳከም እና ሌሎች ጭንብል መሸፈኛዎች በተናጥል በተዘጋው `check:test-masking` በር ባለቤትነት ይቆያሉ።
### ሥራ `lint`
@@ -175,11 +177,11 @@ Mergify የወረፋ ማጠቃለያውን ወደ ረቂቁ መግለጫ ይጽ
`scripts/i18n/sync-llm-mirrors.mjs` (እንዲሁም እንደ `syncLlmMirrors()` ወደ ውጭ ይላካል, ከ `--dry-run` ጋር) የ `llm.txt` መስተዋቶችን እንደገና ይጽፋል; የመልቀቂያው አድስ፣ የትርጉም ሞገድ እና የታቀደው `i18n-mirror-refresh.yml` ያካሂዱት (ማደሱ የቆዩ `llm.txt` መስተዋቶችን በደረቅ ሩጫ ይገነዘባል፣ ተንሳፋፊ ሪፖርቱ ስለማይዘረዝራቸው እና ከ `check:docs-all` በፊት ያመሳስላቸዋል)።
በ `docs/diagrams/` ስር ያሉት አስራ ሁለቱ README SVGs ይፈጠራሉ (`scripts/docs/gen-readme-<name>.mjs`፣ `npm run docs:readme-diagrams` ሁሉንም ያድሳል)። እያንዳንዱ የባይት-ንጽጽር አሃድ ሙከራ (`tests/unit/docs/readme-*-svg.test.ts`, job `test-unit`) ያለው የተፈፀመው ፋይል በመልቀቂያ ሁነታ ላይ ሲያልቅ የማይሳካው; በ PR፣ `check:generated-artifacts` አንድ SVG PR አርትዖቶችን ይፈርዳል እና የመሠረቱ ተንሸራታች ለመልቀቂያው እድሳት ይቀራል ( [የተፈጠሩ ፋይሎችን እና የመነሻ መስመሮችን](#generated-files-and-derived-baselines-written-at-release) ይመልከቱ) — እና `check:docs-counts` ቀኖናዊ ቁጥሮችን ከ `<text>` nodes — ያነባሉ ለዚህም ነው የዝርዝር ሂደቱ በፋይሉ ውስጥ ያሉትን እያንዳንዱን ሕብረቁምፊዎች በማይታይ `<text>` ያቆየዋል። የ SVG ቀኖናዊ-ቁጥሮች ቼክ በ `SVG_DIAGRAM_FILES` (`scripts/check/check-docs-counts-sync.mjs`) የተዘረዘሩትን ፋይሎች ያነባል `docs/diagrams/readme-hero.svg`, `free-tier-budget.svg`, `promise-pillars.svg`, `comparison-table.svg`, `cli-terminal.svg`, `tier-cascade.svg`, plus `public/images/tier-flow-dark.svg` እና `tier-flow-light.svg` የነፃው-ዘላለም፣ ካታሎግ-መግቢያ፣ ተደጋጋሚ ገንዳ እና የውጤት መንስኤዎች የይገባኛል ጥያቄዎች በተጨማሪ `promise-pillars.svg`, `free-tier-budget.svg` እና `strategies-grid.svg` አንብበዋል. እነዚህ ጄነሬተሮች የሚሳሉት ቆጠራዎች (የአቅራቢው ጠቅላላ፣ MCP መሣሪያዎች፣ የማዞሪያ ስልቶች፣ ለዘለዓለም ነጻ የሆኑ አቅራቢዎች፣ …) ከእውነታዎች ቅጽበታዊ ገጽ እይታ `docs/reference/derived-facts.json` እስከ `scripts/docs/readmeFacts.mjs` በኩል የሚመጡት እንጂ ከጥሬ ቃላት አይደሉም፣ ስለዚህ በማንኛውም ቅርንጫፍ ላይ ዲያግራምን እንደገና ማመንጨት የገባውን ፋይል እንደገና ያባዛል። `free-tier-budget.svg` ረድፎቹን ከተመሳሳዩ ቅጽበታዊ ገጽ እይታ ይሳሉ (`code.freeTierBudget`፣ ካታሎግ ማጠቃለያው የእውነታ መመርመሪያ መዝገቦች)፣ ስለዚህ `FREE_MODEL_BUDGETS` ወደ CI ቀይ ከመቀየር ይልቅ በሚቀጥለው ማደስ ካርዱ ላይ ይደርሳል።
በ `docs/diagrams/` ስር ያሉት አስራ ሁለቱ README SVGs ይፈጠራሉ (`scripts/docs/gen-readme-<name>.mjs`፣ `npm run docs:readme-diagrams` ሁሉንም ያድሳል)። እያንዳንዱ የባይት-ንጽጽር አሃድ ፈተና (`tests/unit/docs/readme-*-svg.test.ts`, job `test-unit`) ያለው የተፈፀመው ፋይል በመልቀቂያ ሁነታ ላይ ሲቀር አይሳካም; በ PR፣ `check:generated-artifacts` አንድ SVG PR አርትዖቶችን ይፈርዳል እና የመሠረቱ ተንሸራታች ለመልቀቂያው እድሳት ይቀራል ( [የተፈጠሩ ፋይሎችን እና የመነሻ መስመሮችን](#generated-files-and-derived-baselines-written-at-release) ይመልከቱ) — እና `check:docs-counts` ቀኖናዊ ቁጥሮችን ከ `<text>` nodes — ያነባሉ ለዚህም ነው የዝርዝር ሂደቱ በፋይሉ ውስጥ ያሉትን እያንዳንዱን ሕብረቁምፊዎች በማይታይ `<text>` ያቆየዋል። የ SVG ቀኖናዊ-ቁጥሮች ቼክ በ `SVG_DIAGRAM_FILES` (`scripts/check/check-docs-counts-sync.mjs`) የተዘረዘሩትን ፋይሎች ያነባል `docs/diagrams/readme-hero.svg`, `free-tier-budget.svg`, `promise-pillars.svg`, `comparison-table.svg`, `cli-terminal.svg`, `tier-cascade.svg`, plus `public/images/tier-flow-dark.svg` እና `tier-flow-light.svg` የነፃው-ዘላለም፣ ካታሎግ-መግቢያ፣ ተደጋጋሚ ገንዳ እና የውጤት መንስኤዎች የይገባኛል ጥያቄዎች በተጨማሪ `promise-pillars.svg`, `free-tier-budget.svg` እና `strategies-grid.svg` አንብበዋል. እነዚህ ጄነሬተሮች የሚሳሉት ቆጠራዎች (የአቅራቢው ጠቅላላ፣ MCP መሣሪያዎች፣ የማዞሪያ ስልቶች፣ ለዘለዓለም ነጻ የሆኑ አቅራቢዎች፣ …) ከእውነታዎች ቅጽበታዊ ገጽ እይታ `docs/reference/derived-facts.json` እስከ `scripts/docs/readmeFacts.mjs` በኩል የሚመጡት እንጂ ከጥሬ ቃላት አይደሉም፣ ስለዚህ በማንኛውም ቅርንጫፍ ላይ ዲያግራምን እንደገና ማመንጨት የገባውን ፋይል እንደገና ያባዛል። `free-tier-budget.svg` ረድፎቹን ከተመሳሳዩ ቅጽበታዊ ገጽ እይታ ይሳሉ (`code.freeTierBudget`፣ ካታሎግ ማጠቃለያው የእውነታ መመርመሪያ መዝገቦች)፣ ስለዚህ `FREE_MODEL_BUDGETS` ወደ CI ቀይ ከመቀየር ይልቅ በሚቀጥለው ማደስ ካርዱ ላይ ይደርሳል።
### የተገኙ እሴቶች፡ የ `pr` እና `release` በር ሁነታዎች
PR ባህሪ እንደ መነሻው ሁኔታ የሚወሰን እሴትን በጭራሽ አይጽፍም፡ አቅራቢ፣ ፍልሰት፣ MCP-መሳሪያ እና የስትራቴጂ ቆጠራዎች፣ የ README SVG ቁጥሮች፣ የእውነታዎች ቅጽበታዊ ገጽ እይታ። አንድ እርምጃ ሁሉንም ያሰላል፣ `npm run release:refresh-derived`፣ በተለቀቀው እና በምሽት በመነጨ-እድሳት PR የሚተዳደር። ስለዚህ** በተለቀቁት መካከል መሠረቱ ከቀጥታ ኮድ በንድፍ በስተጀርባ ነው።** , እና ዛፉን ከቀጥታ ኮድ ጋር የሚያነጻጽር በር ወይም ፈተና በእያንዳንዱ PR ላይ አንድ ወንድም ወይም እህት አቅራቢ ካከሉ በኋላ ቀይ ይሆናል። የተገኙትን እሴቶች የሚዳኙት በሮች ከሁለቱ ሁነታዎች በአንዱ ይሰራሉ በ `scripts/check/lib/gateMode.mjs` (የመጀመሪያ ግጥሚያ አሸነፈ)
PR ባህሪ እንደ መነሻው ሁኔታ የሚወሰን እሴትን በጭራሽ አይጽፍም፡ አቅራቢ፣ ፍልሰት፣ MCP-መሳሪያ እና የስትራቴጂ ቆጠራዎች፣ የ README SVG ቁጥሮች፣ የእውነታዎች ቅጽበታዊ ገጽ እይታ። አንድ እርምጃ ሁሉንም ያሰላል፣ `npm run release:refresh-derived`፣ በተለቀቀው እና በምሽት በመነጨ-እድሳት PR የሚተዳደር። ስለዚህ** በተለቀቁት መካከል መሠረቱ ከቀጥታ ኮድ በንድፍ በስተጀርባ ነው።** , እና ዛፉን ከቀጥታ ኮድ ጋር የሚያወዳድረው በር ወይም ፈተና በእያንዳንዱ PR ላይ አንድ ወንድም ወይም እህት አቅራቢ ካከሉ በኋላ ቀይ ይሆናል። የተገኙትን እሴቶች የሚዳኙት በሮች ከሁለቱ ሁነታዎች በአንዱ ይሰራሉ በ `scripts/check/lib/gateMode.mjs` (የመጀመሪያ ግጥሚያ አሸነፈ)
1. `--mode=pr|release` በትእዛዝ መስመር ላይ;
2. የ `OMNIROUTE_GATE_MODE` አካባቢ ተለዋዋጭ (`pr` ወይም `release`);
@@ -213,7 +215,7 @@ PR ባህሪ እንደ መነሻው ሁኔታ የሚወሰን እሴትን በ
- `npm run facts` እያንዳንዱን የተገኘ ቁጥር እንደ JSON (`scripts/release/facts.mjs`) ያትማል። `--key=code.mcpTools` አንድ እሴት ያትማል፣ `--snapshot` ከቀጥታ ዛፍ ይልቅ የተፈጸመውን ቅጽበታዊ ገጽ እይታ ያነባል። እውነታውን መሰብሰብ በማይቻልበት ጊዜ 2 ውጣ።
- `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; the values are translated in the same run by the backend configured in the environment or in `.env` (`OMNIROUTE_TRANSLATION_*`, only those keys are read) or by the Google engine. Without a backend it never writes `__MISSING__` markers: the release profile fails, the nightly skips the keys, and `--allow-untranslated` writes them on purpose), `llm-mirrors` and `verify-generated` (after a write, `check:generated-artifacts` and `check:agent-skills-sync` in release mode must pass; skipped in `--check` and when `--only` leaves it out; a failure is exit 2). 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` የመጨረሻው ማደስ ጥቅም ላይ የዋለው የእውነታዎች ቅጽበታዊ ገጽ እይታ ነው። ማደስ ብቻ ነው የሚጽፈው። የ README SVG ጀነሬተሮች አንብበውታል፣ እና የPR-time ዩኒት ሙከራዎች የተፈጸሙትን ሰነዶች እና የመነጩ ፋይሎች ከእሱ ጋር — በጭራሽ ከቀጥታ ኮድ ጋር ያወዳድራሉ። የስብስቡ ነጠላ የቀጥታ ንፅፅር በ `tests/unit/check-docs-counts-sync.test.ts` ውስጥ "የልቀት መታደስ ዑደቱን ይዘጋል" ነው፡ ከቀጥታ እውነታዎች ጋር፣ የማደስ ዳግም መፃፍ እቅድ በማህደረ ትውስታ ውስጥ የተተገበረው ምንም STRICT መንቀጥቀጥ አይተወውም፣ እና እንደገና እቅድ ማውጣት ምንም አይቀይረውም።
- `docs/reference/derived-facts.json` ጥቅም ላይ የዋለው የመጨረሻው ማደስ የእውነታዎች ቅጽበታዊ ገጽ እይታ ነው። ማደስ ብቻ ነው የሚጽፈው። የ README SVG ጀነሬተሮች አንብበውታል፣ እና የPR-time ዩኒት ሙከራዎች የተፈጸሙትን ሰነዶች እና የመነጩ ፋይሎች ከእሱ ጋር — በጭራሽ ከቀጥታ ኮድ ጋር ያወዳድራሉ። የስብስቡ ነጠላ የቀጥታ ንፅፅር በ `tests/unit/check-docs-counts-sync.test.ts` ውስጥ "የልቀት መታደስ ዑደቱን ይዘጋል" ነው፡ ከቀጥታ እውነታዎች ጋር፣ የማደስ ዳግም መፃፍ እቅድ በማህደረ ትውስታ ውስጥ የተተገበረው ምንም STRICT መንቀጥቀጥ አይተወውም፣ እና እንደገና እቅድ ማውጣት ምንም አይቀይረውም።
በአካባቢው ለመራባት (አካባቢያዊ አሂድ ወደ `release` ነባሪዎች)፡-
@@ -249,7 +251,7 @@ npm run release:refresh-derived -- --check # what the rele
አንዱን i18n regression ይይዛል ሌላኛው በመዋቅራዊ መልኩ በሮች ማየት አይችሉም፡ የእንግሊዘኛ እሴት እንደገና ይፃፋል እና ከ _ቀዳሚ_ እንግሊዘኛ የተገኙት ትርጉሞች ወደ ኋላ ይቆያሉ፣ ስለዚህ እንግሊዛዊ ያልሆኑ ተጠቃሚዎች በልበ ሙሉነት-ቃል ያለው አሁን የተሳሳተ ቅጂ ያነባሉ።
ይህ በእውነቱ ተልኳል። `oauthModal.googleOAuthWarning` በድጋሚ የተጻፈው አንቲግራቪቲ መግቢያ ረዳት ሲያርፍ (#5203);** 39 ከ 43 አከባቢዎች** ለኦፕሬተሮች "ሙሉውን URL ገልብጠው ከዚህ በታች ለጥፍ" — ለዚያ አገልግሎት አቅራቢ ማጠናቀቅ የማይችል ፍሰት እንዲያደርጉ የሚገልጽ ጽሁፍ ቀጠለ። እስከ #8463 ድረስ ሳይስተዋል ቀርቷል ምክንያቱም፡-
ይህ በእውነቱ ተልኳል። `oauthModal.googleOAuthWarning` እንደገና የተጻፈው Antigravity መግቢያ ረዳት ሲያርፍ (#5203);** 39 ከ 43 አከባቢዎች** ለኦፕሬተሮች "ሙሉውን URL ገልብጠው ከዚህ በታች ለጥፍ" የሚል ጽሁፍ ደጋግሞ ለአገልግሎት አቅራቢው ማጠናቀቅ የማይችል — ። እስከ #8463 ድረስ ሳይስተዋል ቀርቷል ምክንያቱም፡-
- `sync-ui-keys` ያሉትን ቁልፎች ብቻ ነው የሚሞላው።** የለም** ፣ በጭራሽ ያልሆኑት።** የቆየ** ;
- `check-ui-keys-coverage` ቁልፍ _presence_ ይቆጥራል፣ ስለዚህ የቆየ ትርጉም እንደተሸፈነ ይቆጠራል።

Some files were not shown because too many files have changed in this diff Show More