mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-08-26 09:02:11 +03:00
* fix(ci): clear base-reds on release/v3.8.50 (round 3) - CHANGELOG.md: restore the top [Unreleased] section dropped by the #10189 reconcile (docs-sync gate: first section must be Unreleased) - env-doc-sync: document CONDUCTOR_ORCHESTRATOR_TOKEN + CONDUCTOR_SPOKESPERSON_URL in .env.example/ENVIRONMENT.md; allowlist the CI-only GITHUB_STEP_SUMMARY and TS7_BASE_REF (ts7 ratchet signals); drop a stray merge artifact line - providers: restore the audited chatanywhere metadata entry that base-reds round 2 dropped together with its duplicate — the provider was half-wired (registry+endpoint without APIKEY metadata), which is what the wave3 test catches; re-pin providers-constants-split at the measured 228 - docs counts: 338 -> 339 (today's +2 void-ai/helixmind, -1 Puter) via gen:provider-reference + README/AGENTS/llm.txt/package.json/diagrams/i18n mirrors - file-size ratchet: annotated rebaseline for the two pre-existing drifts (ModelSelectModal 1138, gateways 1250) following the 2026-08-11 precedent Refs #9985 * fix(ci): base-reds round 3b — stale sibling tests + mode-pack weight contract - check-docs-counts-sync.test.ts: drop the imports/subtests of the four helpers #10196 removed from the gate script (readMcpFactsFromSource, listLocalizedDocs, makeRequiredCountsValidator, checkFreeTierInventory) — the new-API tests that #10196 added stay; the file now loads again under the node runner - quota-connection-recovery.test.ts: convert from vitest APIs to node:test — the file lives in tests/unit/*.test.ts (node-runner glob) and the vitest runtime crashes when imported outside vitest, killing the whole shard entry - modePacks.ts: re-normalize all six mode packs to sum 1.0 — #8940 added sessionAvailability: 0.05 to every pack without rebalancing (1.05 total); ratios preserved exactly (÷1.05), so post-normalizeScoringWeights behavior is unchanged; restores the declared sum-to-1.0 contract the 4235 test pins Refs #9985 * fix(ci): base-reds round 3c — vitest siblings, weights default, secrets FP, mutation tap - DistributeProxiesButton.test.tsx: wrap renders in NextIntlClientProvider — #9245 localized the component (useTranslations) and left the test without the intl context, failing all 14 cases - scoring.ts: re-normalize DEFAULT_WEIGHTS to sum 1.0 (same #8940 class as the mode packs — sessionAvailability added without rebalancing; ratios preserved) - .gitleaks.toml: generalize the kimi sponsor-banner localStorage-key allowlist to -v\d+ — #10200 bumped v1→v2 and the stale regex regressed the secrets ratchet with a false positive - stryker.conf.json: register 6 covering unit tests in tap.testFiles (4 modules) so their mutant kills count — unblocks check:mutation-test-coverage --strict Refs #9985 * fix(ci): base-reds round 3d — inspector factor gap, stale registry/gap tests, i18n key sync - comboScoringInspector: add cacheAffinity/sessionAvailability/connectionDensity to FACTOR_KEYS + the factor-key type — calculateScore() weighs them but the breakdown omitted them, so the explained contributions never summed to the reported score (inspector bug, red on the pure tip) - combo-scoring-inspector.test: make the explicit-weights override sum-neutral (±0.05 shift) so it stays valid for any DEFAULT_WEIGHTS values — the hardcoded override only summed to 1.0 against the pre-#8940 defaults, which is also why explicit weights silently fell back to 'default' on the tip - unorouter-registry.test: align to the canonical .com host (api.unorouter.ai 301-redirects there, verified live) and to wave4's live model discovery (passthrough, no static seed) — the .ai/auto-model expectations were stale - check-migration-numbering.test: 147 left KNOWN_GAPS when 147_api_keys_model_access_mode.sql landed — assert absent (same as 143) - i18n: sync-ui pass — 35,914 missing UI keys stamped as __MISSING__ placeholders across 42 locales (mechanical; greens the pt-BR key-presence integrity test; coverage pct unchanged by design — translation is a separate workstream) Refs #9985 * fix(ci): base-reds round 3e — 2 real defects + 14 stale sibling tests (waves A-E) Real defects fixed: - src/lib/db/apiKeys.ts: #9313's empty-allowlist early return bypassed the group permission check, silently disabling group deny rules (#8817) for every key without a per-key allowlist; fall-through restored, restricted+[] deny-all kept - open-sse/utils/proxyFetch.ts: #10032 re-appended the raw transport error to the propagated message, reintroducing the proxy user:password leak #9837 closed; new redactProxyDetailsInMessage() keeps the reason, redacts URL/credentials - .github/workflows/quality.yml: #10134 added the TS7 ratchet as a separate blocking step AFTER the aggregated gates — the exact #8542 masking mechanism; folded into the non-fail-fast loop (still blocking, still PR-only) ⚠️ CI edit, gate-strengthening — explicit owner sign-off requested on the PR - src/i18n/messages/ko.json: 3 machine-mistranslation regressions caught by the #8244 glossary checker (장애인→비활성화됨, 양말5://→socks5://, 비클로드→Claude가 아닌) Stale sibling tests aligned to deliberately-moved contracts (each cites its mover): request-log-detail-layout + -stream (#9245 intl provider), repro-8542 pin update, quality-rail-gate-membership (#10134 shape), agentSkills-routes 45→46 (#9058), cloudflare-ai-catalog-8717 (#8804 supersedes #8808), executor-xai (#9994), vision-bridge-claude-wire (#9463 minimax→openai), sse-auth forced-pin (#8893), tls-proxy-context (strengthened leak guards), rate-limit-local-error-classification (#9164/#9342), minimax-thinking-signature (#9463), codebuddy-cn (#9723 +1 test), github-copilot-custom-model (#9050), providers-g4f-batch3 (#9584), synced-capability-warmup (#9199, stricter), sidebar-tools-group (#8221), oauth-modal-grok-cli-paste (#9245); agentSkills/catalog.ts comment 45→46; file-size rebaseline for proxyFetch (+19, annotated) Refs #9985 * fix(ci): base-reds round 3f — waves F-J: 9 more real defects + stale sibling sweep Real production defects fixed (all red on the pure tip, each with its origin): - routeGuard.ts: #8949 accidentally DELETED the /api/providers/[id]/login local-only pattern — the route spawns a browser, so the loopback gate for a process-spawning route was gone (Hard Rules #15/#17); restored (314 guard tests green) - agentSkills generator: #9058's category dispatch gave the config category an empty body, wiping skills/config-codex-cli/SKILL.md at the #10131 sync; fixed + SKILL.md regenerated via the official generator - imageRegistry: #9982 broke same-provider bare aliasing (antigravity preview id sent upstream unresolved); new resolveSameProviderBareAlias() keeps the fal cross-provider fix intact - imageRegistry: #9982's prefix strip handed the bare nano-banana ids to fal-ai, violating the pinned 2026-07-31 operator decision (adobe-firefly owns them); fal entries made prefix-only (dispatch already re-prefixes) - mediaGeneration/fal.ts: the missing-credential 401 guard was lost when #10198 deleted the superseded falHandler — tests were hitting the live network - bottleneckPatch/rateLimitManager: #9041's merge clobbered #9604, resurrecting the Bottleneck v2.19.5 heartbeat bug (reservoir never refills); patched the library defect at the root and re-aligned chat-rate-limit-body-lock to the working reservoir contract - processSupervisor.mjs: #9761 regressed the Node spawn to bare "node" (the #9156 launchd bug) and dropped #9209's ipv4first args; both restored - openai-responses/pureHelpers: #9423's Agent null-sentinel was unreachable on the schemaless JSON-string path; gate extended - i18n en.json: #8222's regen reverted the #9976 unclosed-tag fix and #8559's combo-cooldown copy; #9038 shipped 40 t() calls with no messages (runtime MISSING_MESSAGE); all restored/added + official sync-ui stamps, and vi's zero-marker policy re-established via the sanctioned translation backend Stale sibling tests aligned (movers cited inline): chat-helpers (#9447), executor-antigravity (#9351), video-fal-grok (#9982), visionBridge (#9759), web-session-credentials (#8974), production-build-module-integrity (positive anchor added), agentSkills-generator/skillManifestsLint/skills-injection/ agentSkillTools-mcp/listCapabilities-a2a (#9058), memory-settings (#10010), model-catalog-policy-invalidation (#8906), model-alias-seed (#9485), reactive-context-compaction (#8949), combo-provider-wildcard (broken upsert helper), oauth-google-loopback (43-locale resurrected-key removal) Validation: 501/501 across the 47 touched test files; typecheck:core, lint, file-size, docs-sync all green. Refs #9985 * fix(ci): base-reds round 3g — wave K/L: 4 more real defects + stale alignments Real defects: - base/reasoningEffort.ts: the stale duplicate cherry-pick #9612 re-added the codex minimal→low rewrite that #9883 had deliberately removed (OMP minimal passthrough); block removed again - cursorImages.ts: #9840 wired prepareCursorImageForWire (sharp re-encode, fail-closed) into the SHARED resolveCursorImages, breaking zai-web and conol-web image uploads (HTTP 400 'undecodable'); new prepareForWire opt-out, Cursor default path unchanged (8 cursor suites green) - modelCapabilities/snapshot: catalog prepare still issued 323 per-model reads of model_context_overrides + max_input_tokens overrides, violating #9199's bulk-load contract; both now resolve from the snapshot single pass - v1-models-discovery-conformance: re-pinned to the bounded 30s SWR window (#9199/#10198) — the old 'stale-first regardless of age' contract is gone Stale tests aligned (movers cited inline): codex-tools-strict-default (#9828 redundant-oneOf strip), devin-providers (#9245 i18n), db-migrationrunner- constants-split (147→151 renumber #8228), gitlab-duo-oauth-setup (#9245), chatcore-extracted-modules (#9161 outbound-protocol keying) compression-api CI failures were cascade artifacts of codex-tools-strict-default failing in the same force-exit shard process — no own defect (171/171 local). Refs #9985 * fix(test): compression-api — register both describes before the runner starts The DATA_DIR setup + route/db top-level awaits sat BETWEEN the two describes; under --test-force-exit (the CI unit-runner flag) the process exits once the already-registered tests finish, so on slow CI machines the whole second describe died as 'Promise resolution is still pending' — the recurring CI-only shard-2 failure that never reproduced locally without the flag. Moved to the top of the file; 10/10 under --test-force-exit locally. Refs #9985 * fix(quality): freeze modelCapabilities.ts at 1006 (annotated) — snapshot routing growth Refs #9985 * fix(quality): move the modelCapabilities freeze into the frozen map (nested schema) Refs #9985 * fix(i18n): translate all 39,718 pending UI keys across 42 locales (owner-approved) Mass-translated every __MISSING__ placeholder via the official i18n:sync-ui --translate-markers pipeline (operator backend), restoring i18nUiCoverage to the 100 baseline (was 89.9 after the merge-storm UI landings + the 42 keys #9038 never shipped). Post-pass repairs, all caught by the existing gates: - glossary: retired renderings the machine reintroduced normalized again (提供商→提供者 zh-CN/zh-TW, 鏈接→連結, 文檔→文件, 調用→呼叫, 供應商→提供者, 響應→回應, 不活躍→未啟用 zh-TW; 클로드→Claude, 옴니루트→OmniRoute ko); DATA_DIR forbidden rendering avoided via 数据文件夹 rephrase - ICU integrity: 120 values with renamed/dropped {params} repaired (39 positional renames, 81 reset to the en source — functional over fluent) Validation: glossary/pt-BR/vi/deno-relay/settings-keys/value-drift/google- loopback suites 76/76; placeholder diff en×42 locales = 0; worst-locale coverage = 100.0%. Refs #9985 --------- Co-authored-by: backryun <bakryun0718@proton.me>
122 lines
5.1 KiB
TypeScript
122 lines
5.1 KiB
TypeScript
/**
|
|
* G0 guard — the PR→release/** rail (quality.yml) must keep the ratchet + security
|
|
* gates that used to run only on the PR→main rail (ci.yml).
|
|
*
|
|
* Why: the god-file refactor (trilho 3.8.50→3.9.0) happens almost entirely in
|
|
* PRs targeting release/**. Before G0, those PRs skipped the CodeQL ratchet, the
|
|
* quality-ratchet engine, and every security scanner — exactly the net the
|
|
* refactor needs. Five of the 13 root causes reconciled on 2026-07-24 were real
|
|
* production regressions shipped through green per-PR CI; the gates below are the
|
|
* part of that lesson that can be enforced by machine.
|
|
*
|
|
* This test pins MEMBERSHIP, not order: removing a gate from quality.yml (or
|
|
* moving it to a job that does not run on code PRs) must be a conscious decision
|
|
* that edits this file in the same PR, with the reason in the diff.
|
|
*/
|
|
import test from "node:test";
|
|
import assert from "node:assert/strict";
|
|
import fs from "node:fs";
|
|
import path from "node:path";
|
|
import { fileURLToPath } from "node:url";
|
|
|
|
const repoRoot = path.resolve(path.dirname(fileURLToPath(import.meta.url)), "../..");
|
|
const workflow = fs.readFileSync(path.join(repoRoot, ".github/workflows/quality.yml"), "utf-8");
|
|
|
|
/** Extract one top-level job block from the workflow (2-space indented key). */
|
|
function jobBlock(job: string): string {
|
|
const m = new RegExp(`^ {2}${job}:\\s*$`, "m").exec(workflow);
|
|
assert.ok(m, `quality.yml must define job "${job}"`);
|
|
const rest = workflow.slice(m.index + m[0].length);
|
|
const next = /^ {2}[A-Za-z0-9_-]+:\s*$/m.exec(rest);
|
|
return next ? rest.slice(0, next.index) : rest;
|
|
}
|
|
|
|
test("lint-guard carries the quality-ratchet engine (collect → ratchet → require-tighten → codeql)", () => {
|
|
const block = jobBlock("lint-guard");
|
|
for (const needle of [
|
|
"npm run quality:collect",
|
|
"check-quality-ratchet.mjs --allow-missing",
|
|
"--require-tighten",
|
|
"npm run check:codeql-ratchet",
|
|
]) {
|
|
assert.ok(block.includes(needle), `lint-guard must run "${needle}"`);
|
|
}
|
|
// The CodeQL ratchet reads open code-scanning alerts; without this permission
|
|
// the API call 403s and the gate silently self-skips forever.
|
|
assert.match(block, /security-events:\s*read/, "lint-guard needs security-events: read");
|
|
});
|
|
|
|
test("fast-gates carries the deterministic ratchets and security scanners from the main rail", () => {
|
|
const block = jobBlock("fast-gates");
|
|
// #8542: all gates run inside a single aggregation step's bash loop.
|
|
// Check that the gate names appear in the arrays or the loop body.
|
|
for (const needle of [
|
|
"cycles lockfile duplication dead-code type-coverage compression-budget",
|
|
"secrets vuln-ratchet workflows openapi-breaking",
|
|
"typecheck:core",
|
|
"check:dashboard-typecheck",
|
|
"check:ts7-diagnostics-ratchet",
|
|
]) {
|
|
assert.ok(block.includes(needle), `fast-gates must contain "${needle}"`);
|
|
}
|
|
assert.ok(
|
|
block.includes(
|
|
"BASE_REF: ${{ github.base_ref && format('origin/{0}', github.base_ref) || '' }}"
|
|
),
|
|
"oasdiff must receive the origin-prefixed base ref fetched by actions/checkout"
|
|
);
|
|
for (const version of [
|
|
"GITLEAKS_VERSION=v",
|
|
"OSV_SCANNER_VERSION=v",
|
|
"ACTIONLINT_VERSION=v",
|
|
"ZIZMOR_VERSION=",
|
|
"OASDIFF_VERSION=v",
|
|
]) {
|
|
assert.ok(block.includes(version), `fast-gates must pin ${version.split("=")[0]}`);
|
|
}
|
|
assert.doesNotMatch(
|
|
block,
|
|
/download-actionlint\.bash\) latest/,
|
|
"actionlint must not use latest"
|
|
);
|
|
});
|
|
|
|
test("the complexity ratchet stays on the release rail (G0's written validation criterion)", () => {
|
|
assert.ok(
|
|
jobBlock("fast-gates").includes("complexity-ratchets"),
|
|
"a complexity regression in a PR→release/** must be blocked by fast-gates"
|
|
);
|
|
});
|
|
|
|
test("the TS7 shadow and zero-new-diagnostics ratchet use one pinned compiler and core scope", () => {
|
|
const block = jobBlock("fast-gates");
|
|
assert.match(block, /typescript@7\.0\.2/, "TS7 diagnostics must use the reviewed compiler");
|
|
// The ratchet is folded into the non-fail-fast aggregation step (#8542 — a
|
|
// separate blocking step would let an earlier red gate mask it), so its base
|
|
// ref arrives via that step's PR_BASE_SHA env binding.
|
|
assert.match(
|
|
block,
|
|
/PR_BASE_SHA:\s*\$\{\{ github\.event\.pull_request\.base\.sha \}\}/,
|
|
"the ratchet must compare against the exact pull-request base commit"
|
|
);
|
|
assert.match(
|
|
block,
|
|
/check:ts7-diagnostics-ratchet -- --base-ref "\$PR_BASE_SHA"/,
|
|
"the ratchet invocation must consume the pull-request base sha"
|
|
);
|
|
assert.ok(
|
|
block.includes("tsconfig.typecheck-core.json"),
|
|
"the advisory shadow must use the same core scope as the blocking ratchet"
|
|
);
|
|
});
|
|
|
|
test("the new gates run on jobs that stay pinned to hosted runners", () => {
|
|
// Complements tests/unit/vps-runner-variable-scope.test.ts: neither gate job
|
|
// may pick up a USE_VPS_RUNNER switch (setup-node measured 20m06s on .113 vs 16s hosted).
|
|
for (const job of ["lint-guard", "fast-gates"]) {
|
|
const runsOn = /^ {4}runs-on:\s*(.+)$/m.exec(jobBlock(job));
|
|
assert.ok(runsOn, `${job} must declare runs-on`);
|
|
assert.equal(runsOn[1].trim(), "ubuntu-latest", `${job} must stay pinned to ubuntu-latest`);
|
|
}
|
|
});
|