Compare commits

..

4 Commits

Author SHA1 Message Date
diegosouzapw
fc94dbf174 refactor(api): unwrap one escape level per pass in the API-only port path check 2026-11-20 17:27:44 -03:00
diegosouzapw
6475dbfa0f docs: add changelog fragment for #20793 2026-11-20 12:44:20 -03:00
diegosouzapw
bd49e1bb34 fix(api): refuse a fragment marker in paths on the API-only port 2026-11-20 12:19:00 -03:00
diegosouzapw
fa084e324f fix(api): refuse dot-segment paths on the API-only port 2026-11-20 00:10:11 -03:00
720 changed files with 14441 additions and 21321 deletions

View File

@@ -38,9 +38,6 @@ 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"
@@ -1175,7 +1172,7 @@ jobs:
- uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7
with:
package-manager-cache: false
node-version: ${{ env.CI_V8_NODE_VERSION }}
node-version: ${{ env.CI_NODE_VERSION }}
- uses: ./.github/actions/prepare-unit-storage
with:
cache: ${{ github.event_name == 'pull_request' }}
@@ -1195,7 +1192,6 @@ 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
@@ -1205,12 +1201,6 @@ 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 \
@@ -1218,23 +1208,11 @@ jobs:
--exclude=tests/** \
--exclude=**/*.test.* \
npm run test:unit:ci:shard
- 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
- name: Upload raw shard coverage
if: always()
uses: actions/upload-artifact@cf430e030ddbb5b0abf93d22962f4752f3646cd9 # v7
with:
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 }}
name: coverage-shard-${{ matrix.shard }}
path: coverage-shard/*.json
if-no-files-found: error
@@ -1337,9 +1315,6 @@ 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
@@ -1379,47 +1354,41 @@ jobs:
- uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7
with:
package-manager-cache: false
node-version: ${{ env.CI_V8_NODE_VERSION }}
node-version: ${{ env.CI_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:
artifact-ids: ${{ steps.coverage_selection.outputs.artifact_ids }}
pattern: coverage-shard-*
path: coverage-shards/
merge-multiple: false
merge-multiple: true
- name: Merge + report + gate
# 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.
# 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.
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" ] || [ "${SONARQUBE_ENABLED:-}" = "true" ]; then
LCOV_REPORTER=(--reporter=lcov)
fi
if [ "$EVENT_NAME" != "pull_request" ]; then LCOV_REPORTER=(--reporter=lcov); fi
mkdir -p coverage
# 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
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
# 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
@@ -1427,7 +1396,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-verified \
--temp-directory coverage-shards \
--reports-dir coverage \
--merge-async \
--reporter=text-summary \
@@ -1437,7 +1406,6 @@ 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: |
@@ -1488,8 +1456,6 @@ 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
@@ -1518,17 +1484,6 @@ 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,53 +1,122 @@
# Mergify — merge queue RETIRED by the owner's decision of 2026-11-19.
# Mergify merge queue — WS3.4/D5 of the v3.8.49 quality/velocity master plan.
#
# 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).
# 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.
#
# 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.
# 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.
commands_restrictions:
queue:
# 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
conditions:
- 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
- merged
actions:
label:
remove:
- queue

View File

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

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulyasiya] ediləcəkdi: {action}",
"cancelled": "Ləğv edildi.",
"jsonOpt": "JSON formatında çıxış",
"yesOpt": "Təsdiq sorğusunu keç",
"positiveIntegerRequired": "Limit müsbət tam ədəd olmalıdır."
"yesOpt": "Təsdiq sorğusunu keç"
},
"setup": {
"title": "OmniRoute Quraşdırılması",

View File

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

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[dry-run] bi izvršio {action}",
"cancelled": "Otkazano.",
"jsonOpt": "Izlaz kao JSON",
"yesOpt": "Preskoči potvrdu",
"positiveIntegerRequired": "Limit mora biti pozitivan cijeli broj."
"yesOpt": "Preskoči potvrdu"
},
"setup": {
"title": "OmniRoute Setup",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulace] by provedlo: {action}",
"cancelled": "Zrušeno.",
"jsonOpt": "Výstup jako JSON",
"yesOpt": "Přeskočit potvrzení",
"positiveIntegerRequired": "Limit musí být kladné celé číslo."
"yesOpt": "Přeskočit potvrzení"
},
"setup": {
"title": "Nastavení OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulering] ville: {action}",
"cancelled": "Annulleret.",
"jsonOpt": "Output som JSON",
"yesOpt": "Spring bekræftelse over",
"positiveIntegerRequired": "Grænse skal være et positivt heltal."
"yesOpt": "Spring bekræftelse over"
},
"setup": {
"title": "Opsætning af OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[Simulation] würde: {action}",
"cancelled": "Abgebrochen.",
"jsonOpt": "Ausgabe als JSON",
"yesOpt": "Bestätigung überspringen",
"positiveIntegerRequired": "Der Grenzwert muss eine positive ganze Zahl sein."
"yesOpt": "Bestätigung überspringen"
},
"setup": {
"title": "OmniRoute-Einrichtung",

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulación] haría: {action}",
"cancelled": "Cancelado.",
"jsonOpt": "Salida como JSON",
"yesOpt": "Omitir confirmación",
"positiveIntegerRequired": "El límite debe ser un número entero positivo."
"yesOpt": "Omitir confirmación"
},
"setup": {
"title": "Configuración de OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[testkäivitus] tehakse {action}",
"cancelled": "Tühistatud.",
"jsonOpt": "Väljund JSON-formaadis",
"yesOpt": "Jäta kinnitusküsimus vahele",
"positiveIntegerRequired": "Limiit peab olema positiivne täisarv."
"yesOpt": "Jäta kinnitusküsimus vahele"
},
"setup": {
"title": "OmniRoute seadistus",

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulointi] tekisi: {action}",
"cancelled": "Peruutettu.",
"jsonOpt": "Tulosta JSON-muodossa",
"yesOpt": "Ohita vahvistuspyyntö",
"positiveIntegerRequired": "Rajan on oltava positiivinen kokonaisluku."
"yesOpt": "Ohita vahvistuspyyntö"
},
"setup": {
"title": "OmniRoute-asennus",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulation] ferait : {action}",
"cancelled": "Annulé.",
"jsonOpt": "Sortie au format JSON",
"yesOpt": "Ignorer la confirmation",
"positiveIntegerRequired": "La limite doit être un entier positif."
"yesOpt": "Ignorer la confirmation"
},
"setup": {
"title": "Configuration d’OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[triail thuras] dhéanfadh {action}",
"cancelled": "Cealaithe.",
"jsonOpt": "Aschur mar JSON",
"yesOpt": "Scipeáil an契ordheimhniú",
"positiveIntegerRequired": "Ní mór teorainn a bheith ina slánuimhir dhearfach."
"yesOpt": "Scipeáil an契ordheimhniú"
},
"setup": {
"title": "Socrú OmniRoute",

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[dry-run] za a {action}",
"cancelled": "An soke.",
"jsonOpt": "Fitar da sakamako a matsayin JSON",
"yesOpt": "Tsallake tambayar tabbatarwa",
"positiveIntegerRequired": "Dole ne iyakar ta zama cikakkiyar lamba wadda ta fi sifili."
"yesOpt": "Tsallake tambayar tabbatarwa"
},
"setup": {
"title": "Saitin OmniRoute",

View File

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

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[probni-unos] bi {action}",
"cancelled": "Otkazano.",
"jsonOpt": "Ispis kao JSON",
"yesOpt": "Preskoči upit za potvrdu",
"positiveIntegerRequired": "Ograničenje mora biti pozitivan cijeli broj."
"yesOpt": "Preskoči upit za potvrdu"
},
"setup": {
"title": "OmniRoute Postavljanje",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[szimuláció] végrehajtaná: {action}",
"cancelled": "Törölve.",
"jsonOpt": "JSON formátumú kimenet",
"yesOpt": "Megerősítés kihagyása",
"positiveIntegerRequired": "A limitnek pozitív egész számnak kell lennie."
"yesOpt": "Megerősítés kihagyása"
},
"setup": {
"title": "OmniRoute beállítása",

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulasi] akan: {action}",
"cancelled": "Dibatalkan.",
"jsonOpt": "Keluaran sebagai JSON",
"yesOpt": "Lewati konfirmasi",
"positiveIntegerRequired": "Batas harus berupa bilangan bulat positif."
"yesOpt": "Lewati konfirmasi"
},
"setup": {
"title": "Penyiapan OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[dry-run] a ga-eme {action}",
"cancelled": "Akagbuola.",
"jsonOpt": "Wepụta dị ka JSON",
"yesOpt": "Mafee ajụjụ nkwenye",
"positiveIntegerRequired": "Oke ga-abụrịrị ọnụọgụ zuru ezu karịrị efu."
"yesOpt": "Mafee ajụjụ nkwenye"
},
"setup": {
"title": "Ntọala OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulazione] eseguirebbe: {action}",
"cancelled": "Annullato.",
"jsonOpt": "Output come JSON",
"yesOpt": "Salta la conferma",
"positiveIntegerRequired": "Il limite deve essere un numero intero positivo."
"yesOpt": "Salta la conferma"
},
"setup": {
"title": "Configurazione di OmniRoute",

View File

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

View File

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

View File

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

View File

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

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[dry-run] būtų atliktas veiksmas: {action}",
"cancelled": "Atšaukta.",
"jsonOpt": "Išvesti JSON formatu",
"yesOpt": "Praleisti patvirtinimo užklausą",
"positiveIntegerRequired": "Riba turi būti teigiamas sveikasis skaičius."
"yesOpt": "Praleisti patvirtinimo užklausą"
},
"setup": {
"title": "OmniRoute sąranka",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[testrežīms] veiktu {action}",
"cancelled": "Atcelts.",
"jsonOpt": "Izvade JSON formātā",
"yesOpt": "Izlaist apstiprinājuma pieprasījumu",
"positiveIntegerRequired": "Ierobežojumam ir jābūt pozitīvam veselam skaitlim."
"yesOpt": "Izlaist apstiprinājuma pieprasījumu"
},
"setup": {
"title": "OmniRoute iestatīšana",

View File

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

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[dry-run] akan {action}",
"cancelled": "Dibatalkan.",
"jsonOpt": "Output sebagai JSON",
"yesOpt": "Langkau gesaan pengesahan",
"positiveIntegerRequired": "Had mestilah integer positif."
"yesOpt": "Langkau gesaan pengesahan"
},
"setup": {
"title": "Persediaan OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[dry-run] se jaġixx {action}",
"cancelled": "Kkanċellat.",
"jsonOpt": "Output bħala JSON",
"yesOpt": "Qabżu l-prompt ta' konferma",
"positiveIntegerRequired": "Il-limitu għandu jkun numru sħiħ pożittiv."
"yesOpt": "Qabżu l-prompt ta' konferma"
},
"setup": {
"title": "Twaqqif ta' OmniRoute",

View File

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

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulatie] zou: {action}",
"cancelled": "Geannuleerd.",
"jsonOpt": "Uitvoer als JSON",
"yesOpt": "Bevestiging overslaan",
"positiveIntegerRequired": "Limiet moet een positief geheel getal zijn."
"yesOpt": "Bevestiging overslaan"
},
"setup": {
"title": "OmniRoute-installatie",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulering] ville: {action}",
"cancelled": "Avbrutt.",
"jsonOpt": "Utdata som JSON",
"yesOpt": "Hopp over bekreftelse",
"positiveIntegerRequired": "Grensen må være et positivt heltall."
"yesOpt": "Hopp over bekreftelse"
},
"setup": {
"title": "Oppsett av OmniRoute",

View File

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

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[dry-run] isasagawa sana ang {action}",
"cancelled": "Kinansela.",
"jsonOpt": "I-output bilang JSON",
"yesOpt": "Laktawan ang prompt sa pagkumpirma",
"positiveIntegerRequired": "Ang limitasyon ay dapat na isang positibong integer."
"yesOpt": "Laktawan ang prompt sa pagkumpirma"
},
"setup": {
"title": "Pag-setup ng OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[symulacja] wykonałoby: {action}",
"cancelled": "Anulowano.",
"jsonOpt": "Wyjście jako JSON",
"yesOpt": "Pomiń potwierdzenie",
"positiveIntegerRequired": "Limit musi być dodatnią liczbą całkowitą."
"yesOpt": "Pomiń potwierdzenie"
},
"setup": {
"title": "Konfiguracja OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulação] faria: {action}",
"cancelled": "Cancelado.",
"jsonOpt": "Saída em JSON",
"yesOpt": "Pular confirmação",
"positiveIntegerRequired": "O limite deve ser um número inteiro positivo."
"yesOpt": "Pular confirmação"
},
"setup": {
"title": "Configuração do OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulação] faria: {action}",
"cancelled": "Cancelado.",
"jsonOpt": "Saída em JSON",
"yesOpt": "Ignorar confirmação",
"positiveIntegerRequired": "O limite deve ser um número inteiro positivo."
"yesOpt": "Ignorar confirmação"
},
"setup": {
"title": "Configuração do OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulare] ar face: {action}",
"cancelled": "Anulat.",
"jsonOpt": "Ieșire ca JSON",
"yesOpt": "Omite confirmarea",
"positiveIntegerRequired": "Limita trebuie să fie un număr întreg pozitiv."
"yesOpt": "Omite confirmarea"
},
"setup": {
"title": "Configurare OmniRoute",

View File

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

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulácia] by vykonalo: {action}",
"cancelled": "Zrušené.",
"jsonOpt": "Výstup ako JSON",
"yesOpt": "Preskočiť potvrdenie",
"positiveIntegerRequired": "Limit musí byť kladné celé číslo."
"yesOpt": "Preskočiť potvrdenie"
},
"setup": {
"title": "Nastavenie OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[poskusni zagon] izvedlo bi se dejanje: {action}",
"cancelled": "Preklicano.",
"jsonOpt": "Izpis v obliki JSON",
"yesOpt": "Preskoči poziv za potrditev",
"positiveIntegerRequired": "Omejitev mora biti pozitivno celo število."
"yesOpt": "Preskoči poziv za potrditev"
},
"setup": {
"title": "Nastavitev OmniRoute",

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simulering] skulle: {action}",
"cancelled": "Avbruten.",
"jsonOpt": "Utdata som JSON",
"yesOpt": "Hoppa över bekräftelse",
"positiveIntegerRequired": "Gränsen måste vara ett positivt heltal."
"yesOpt": "Hoppa över bekräftelse"
},
"setup": {
"title": "OmniRoute-konfiguration",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[dry-run] ingefanya {action}",
"cancelled": "Imeghairiwa.",
"jsonOpt": "Toa matokeo kama JSON",
"yesOpt": "Ruka kidokezo cha uthibitishaji",
"positiveIntegerRequired": "Kikomo lazima kiwe nambari kamili chanya."
"yesOpt": "Ruka kidokezo cha uthibitishaji"
},
"setup": {
"title": "Usanidi wa OmniRoute",

View File

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

View File

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

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[simülasyon] yapılacaktı: {action}",
"cancelled": "İptal edildi.",
"jsonOpt": "JSON olarak çıktı",
"yesOpt": "Onayı atla",
"positiveIntegerRequired": "Limit pozitif bir tam sayı olmalıdır."
"yesOpt": "Onayı atla"
},
"setup": {
"title": "OmniRoute Kurulumu",

View File

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

View File

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

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[dry-run] {action} bajarilgan bo‘lardi",
"cancelled": "Bekor qilindi.",
"jsonOpt": "JSON formatida chiqarish",
"yesOpt": "Tasdiqlash so‘rovini o‘tkazib yuborish",
"positiveIntegerRequired": "Limit musbat butun son boʻlishi kerak."
"yesOpt": "Tasdiqlash so‘rovini o‘tkazib yuborish"
},
"setup": {
"title": "OmniRoute sozlamalari",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"dryRun": "[mô phỏng] sẽ: {action}",
"cancelled": "Đã hủy.",
"jsonOpt": "Xuất dưới dạng JSON",
"yesOpt": "Bỏ qua xác nhận",
"positiveIntegerRequired": "Giới hạn phải là số nguyên dương."
"yesOpt": "Bỏ qua xác nhận"
},
"setup": {
"title": "Thiết lập OmniRoute",

View File

@@ -1,5 +1,6 @@
{
"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",
@@ -12,8 +13,7 @@
"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ú",
"positiveIntegerRequired": "Iye ààlà gbọ́dọ̀ jẹ́ odidi nọ́ńbà rere."
"yesOpt": "Fo ìbéèrè ìmúdájú"
},
"setup": {
"title": "Ìṣètò OmniRoute",

View File

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

View File

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

View File

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

View File

@@ -1 +0,0 @@
- 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

@@ -1 +0,0 @@
- 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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- 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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- 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

@@ -1 +0,0 @@
- 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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- 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

@@ -1 +0,0 @@
- **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

@@ -0,0 +1 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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

@@ -1 +0,0 @@
- **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,7 +1,6 @@
{
"_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.",
@@ -35,7 +34,6 @@
"@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,13 +157,12 @@
"dedicatedGate": true
},
"codeqlAlerts": {
"value": 103,
"value": 6,
"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_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."
"_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."
},
"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,6 +348,5 @@
"@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/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."
"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)."
}

View File

@@ -47,12 +47,6 @@ 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,19 +92,18 @@ 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/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) |
| 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) |
The `GET /api/plugins` `status` filter accepts one of
`installed` / `active` / `inactive` / `error`. An invalid value returns `400`.
@@ -138,8 +137,7 @@ 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. The same
applies to `POST /api/plugins/marketplace/install` (body `{ "name": "<plugin>" }`).
(`requireLogin=false`): installing code is never an anonymous action.
### Browse the marketplace
@@ -157,13 +155,10 @@ curl -X PUT http://localhost:20128/api/plugins/my-plugin/config \
-d '{ "config": { "level": "debug", "maxItems": 100 } }'
```
`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").
`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.
## Configuration

View File

@@ -19,18 +19,16 @@
### የእጩዎች መግቢያ
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 ስለሚያጠፋ ነው።
@@ -39,7 +37,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 ቼኮች ነጻ ሆነው ይቆያሉ፡ ተዛማጅ ባይት የቆየ ደረሰኝን ማዳን አይችልም። የፋይል ታማኝነት የአፈፃፀም ትክክለኛነት ወይም የቅርስ ማስተዋወቅ ማረጋገጫ አይደለም።
@@ -49,7 +47,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` ነው።
@@ -66,9 +64,9 @@ Mergify የወረፋ ማጠቃለያውን ወደ ረቂቁ መግለጫ ይጽ
#### የተረሱ ወንድም እህት ፈተናዎች ሪፖርት ያደርጋሉ
`npm run check:forgotten-sibling-tests` እንደ `Fast Quality Gates` የማማከር ደረጃ ይሰራል እና ከሙከራ-ተፅእኖ ካርታ በስተጀርባ የማስመጣት ፈላጊውን እንደገና ይጠቀማል። ለእያንዳንዱ የተለወጠ የምርት ሞጁል፣ የእጩው ፈተና ከመጎተት-ጥያቄ ልዩነት በማይኖርበት ጊዜ ቆራጥ የሆኑ `changed module/symbol -> static consumer -> candidate sibling test` ሰንሰለቶችን ሪፖርት ያደርጋል። የማርክዳው ማጠቃለያ እና JSON ውጤት ከማናቸውም የማገድ ልቀት በፊት እንደ `forgotten-sibling-tests` የስራ ፍሰት ቅርስ ሆኖ እንዲቆይ ተደርጓል።
`npm run check:forgotten-sibling-tests` እንደ `Fast Quality Gates` የአማካሪ ደረጃ ይሰራል እና የማስመጣት ፈላጊውን ከሙከራ-ተጽእኖ ካርታው ጀርባ እንደገና ይጠቀማል። ለእያንዳንዱ የተለወጠ የምርት ሞጁል፣ የእጩው ፈተና ከመጎተት-ጥያቄ ልዩነት በማይኖርበት ጊዜ ቆራጥ የሆኑ `changed module/symbol -> static consumer -> candidate sibling test` ሰንሰለቶችን ሪፖርት ያደርጋል። የ Markdown ማጠቃለያ እና 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`
@@ -177,11 +175,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`);
@@ -215,7 +213,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` ነባሪዎች)፡-
@@ -251,7 +249,7 @@ npm run release:refresh-derived -- --check # what the rele
አንዱን i18n regression ይይዛል ሌላኛው በመዋቅራዊ መልኩ በሮች ማየት አይችሉም፡ የእንግሊዘኛ እሴት እንደገና ይፃፋል እና ከ _ቀዳሚ_ እንግሊዘኛ የተገኙት ትርጉሞች ወደ ኋላ ይቆያሉ፣ ስለዚህ እንግሊዛዊ ያልሆኑ ተጠቃሚዎች በልበ ሙሉነት-ቃል ያለው አሁን የተሳሳተ ቅጂ ያነባሉ።
ይህ በእውነቱ ተልኳል። `oauthModal.googleOAuthWarning` እንደገና የተጻፈው Antigravity መግቢያ ረዳት ሲያርፍ (#5203);** 39 ከ 43 አከባቢዎች** ለኦፕሬተሮች "ሙሉውን URL ገልብጠው ከዚህ በታች ለጥፍ" የሚል ጽሁፍ ደጋግሞ ለአገልግሎት አቅራቢው ማጠናቀቅ የማይችል — ። እስከ #8463 ድረስ ሳይስተዋል ቀርቷል ምክንያቱም፡-
ይህ በእውነቱ ተልኳል። `oauthModal.googleOAuthWarning` በድጋሚ የተጻፈው አንቲግራቪቲ መግቢያ ረዳት ሲያርፍ (#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