mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-08-05 23:02:10 +03:00
* fix(dashboard): resolve Kimi banner casing collision + shrink frozen test file (release tip) - Rename src/app/(dashboard)/dashboard/kimiSponsorBanner.ts to kimiSponsorBannerGate.ts so it no longer differs from KimiSponsorBanner.tsx only by the first letter's case (breaks next build on case-insensitive filesystems). Updates the sole importer (KimiSponsorBanner.tsx) and the two tests that reference it. - Extract the 8 Kimi/Moonshot featured-ordering tests out of the frozen tests/unit/providers-page-utils.test.ts (grown 3 lines past its 1294 cap by #8039's rebrand-comment update) into a new sibling file tests/unit/providers-page-utils-kimi.test.ts. No assertions dropped; both files pass in full (24 + 8 = 32 tests). * fix(sse): register PromptQlExecutor in the executor registry (release tip) getExecutor("promptql") had no entry in open-sse/executors/index.ts, so it silently fell through to DefaultExecutor's provider fallback, which issues a raw fetch() and returns the bare upstream Response instead of the executor wrapper shape {response, url, headers, transformedBody}. The real PromptQlExecutor class (open-sse/executors/promptql.ts) already honors the contract correctly — it was just never wired into the registry. Fixes tests/unit/executor-web-cookie-sweep.test.ts "promptql executor returns wrapper shape". * fix(i18n): backfill 2220 missing pt-BR keys to restore en.json parity (release tip) pt-BR.json fell behind after #7935 restored +2220 keys into en.json and vi.json but left pt-BR.json unmodified. Translated all missing entries to Brazilian Portuguese, preserving ICU/interpolation placeholders and existing terminology, and merged them mirroring en.json's key order so the diff is additions-only (the small comma-only deletions are pure JSON reformatting from new sibling keys). * fix(providers): repair 4 pre-existing catalog/registry reds on release tip - providers-constants-split.test.ts: APIKEY_PROVIDERS grew 182->187 (PR #7887 added 5 free-tier providers: ainative/aion/sealion/routeway/nara). Verified no dup/loss (6-family partition sums exactly to 187) and updated the stale expected count + comment trail to match. - cline registry: added the missing minimax/minimax-m3 free OpenRouter entry (#3321) and fixed the neighbouring nemotron-3-ultra-550b-a55b entry, which carried a stray ":free" id suffix and an imprecise 1_000_000 contextLength instead of the 1_048_576 the test (and every sibling 1M-context entry in this catalog) expects. - promptqlModels.ts / registry/promptql/index.ts: PROMPTQL_FALLBACK_MODELS's minimax-m3 entry was missing supportsVision, and the registry mapping dropped it entirely (only id/name were passed through) — it was the sole minimax-m3 entry across the whole registry not flagged multimodal, despite every other provider (minimax, minimax-cn, ollama-cloud, trae, bazaarlink, clinepass, codebuddy-cn, opencode-zen/go, synthetic, huggingchat, lmarena) agreeing MiniMax-M3 supports vision. Added the field to the PromptQlModel type and threaded it through. - tests/snapshots/provider/translate-path.json: regenerated the golden via UPDATE_GOLDEN=1. Diffed old vs new — zero providers removed, 5 added (ainative/aion/nara/routeway/sealion, matching #7887), and the only changed entry (cline) reflects the already-merged #7914 ClinePass header protocol change (Cline/<version> User-Agent + X-Task-ID) that a prior narrow golden touch-up missed capturing. * fix(docs): repair docs-sync/env-sync/repo-contract gates (release tip) Six pre-existing reds on release/v3.8.49, all "repo drifted from its own documented contract": - check-docs-counts-sync: free-tier headline was stale (~1.4B/~2.0B) vs the live catalog (~1.53B steady / ~2.15B first month, 43 pools). Updated README.md and docs/reference/FREE_TIERS.md to the live numbers and added a v3.8.49 correction note explaining the pool-count delta (39->43, #7840). Also fixed a soft executors-count drift in ARCHITECTURE.md (84->86, 268->271 providers) while touching that line. - release-green-docs-drift-7253: docs/proxy-subscriptions.md referenced a fabricated migration filename (123_proxy_subscriptions.sql); the real file is 131_proxy_subscriptions.sql. Fixed all 3 occurrences. - check-env-doc-sync + issue-7793-env-doc-sync-repro: OMNIROUTE_DATA_DIR (DATA_DIR fallback alias read by open-sse/executors/promptql/threadSticky.ts) was undocumented. Added to .env.example and docs/reference/ENVIRONMENT.md. - check-db-rules: src/lib/db/proxySubscriptions.ts (#7299) is a db-internal split of proxies.ts (kept under the frozen file-size cap) whose one export is already re-exported via proxies.ts -> localDb.ts. Added it to INTENTIONALLY_INTERNAL with the same db-internal justification used for identical split modules (apiKeyColumnFallbacks, providerNodeSelect, webSessionDedup) rather than a redundant direct re-export from localDb.ts. - mcp-server-hollow-dist-deps: the sanity test expected better-sqlite3 among the MCP bundle's static top-level external imports. That's been stale since the pre-#7878 migration to a cascading SqliteAdapter driver factory (createRequire()-based lazy require, not a static import); better-sqlite3 already has its own native-asset copy guarantee in assembleStandalone.mjs, unrelated to this test's EXTRA_MODULE_ENTRIES concern. Updated the assertion to a still-genuinely-static external (zod) with a comment explaining the change. No production runtime behavior changed — docs, .env.example, and a checker allowlist/test-expectation only. * fix(dashboard): repair stale UI component-shape test assertions (release tip) Two pre-existing reds in the dashboard UI component-contract cluster were caused by test assertions that had gone stale after intentional, correct refactors — not by real defects in the components: - quota-pool-wizard-multi.test.ts: the step-3 preview assertion required the literal single-line substring "connectionIds.map((cid)". Prettier (100-char width, project config) legitimately breaks the connectionIds.map(...).filter(...) chain across lines because of the multi-line callback body, so the literal never matches. PoolWizard.tsx still builds previewByProvider correctly by mapping over connectionIds; updated the assertion to a regex that tolerates the line break. - v388-phase1-screen-fixes.test.ts: the shared Select placeholder-guard assertion required the literal "!children && placeholder". An earlier, intentional i18n commit changed the hardcoded "Select an option" default to a translated fallback (`placeholder ?? t("selectOption")`), which requires parens around the ?? expression for operator precedence. The guard behavior is unchanged (still gated on !children); updated the assertion to match the current, correct guard shape. Both fixes are read-only test-file changes; no production behavior changed. review-reviews-v3814-fixes.test.ts still has one pre-existing, unrelated red (LEDGER-4: minimax-m3 registry entries missing supportsVision) that requires editing the promptql provider registry/catalog — out of this cluster's scope, left untouched and reported separately. * fix(providers): reconcile cline catalog contradictions + deterministic golden (release tip) The first tip-green pass introduced 3 regressions caught by CI on sibling guard tests: - clinepass-provider + cline-catalog-models-3321 encoded OPPOSITE expectations of the same cline model list (minimax presence, nvidia :free suffix). Reference upstream (OpenRouter free lineup) confirms nvidia/nemotron-3-ultra-550b-a55b:free (with :free, 1M ctx) is correct, so restore that id and fix #3321's stale no-:free assertion; add minimax/minimax-m3 (the real #3321 gap) to clinepass-provider's list. - check-db-rules-classification froze INTENTIONALLY_INTERNAL at 35; proxySubscriptions was the intentional 36th entry — add it + bump the count. - provider-translate-path golden stored a LITERAL Cline/3.8.49: clineAuth resolves the version from APP_CONFIG.version (stable), but the golden sanitizer collapsed only process.env.npm_package_version (unset under `node`, set under `npm run`) — so the golden was shard-dependent. Resolve APP_VERSION from APP_CONFIG.version like clineAuth and regenerate; now Cline/<APP> normalizes identically in every shard. * fix(services): type execFile signal/killed in classifyError + ratchet dashboard baseline (release tip) Pre-existing base-red on the tip's Fast Quality Gates (dashboard-typecheck), missed in the first inventory: - src/lib/services/installers/utils.ts TS2339 — `err.signal` was read off a value typed as NodeJS.ErrnoException, which @types/node does not declare `signal`/`killed` on (those belong to execFile's ExecFileException). Widen classifyError's param to type both, and drop the now-redundant `(err as … { killed })` cast. - Ratchet config/quality/dashboard-typecheck-baseline.json down: 5 baselined errors were fixed by already-merged PRs but never ratcheted (OAuthModal TS2769 4→3 / TS2345 4→3, CliproxyModelMappingEditor TS2339, CompressionPreviewAccordion TS4104, MonacoEditor TS2307). Baseline now 254, matching live — gate exits 0.
202 lines
8.8 KiB
TypeScript
202 lines
8.8 KiB
TypeScript
// Kimi (Moonshot AI) featured-first ordering — split out of
|
|
// providers-page-utils.test.ts (2026-07-21) to keep that frozen file under
|
|
// its size cap; same providerPageUtils/featuredProviders module under test,
|
|
// no assertions dropped or weakened in the split.
|
|
import test from "node:test";
|
|
import assert from "node:assert/strict";
|
|
|
|
const providerPageUtils =
|
|
await import("../../src/app/(dashboard)/dashboard/providers/providerPageUtils.ts");
|
|
const providers = await import("../../src/shared/constants/providers.ts");
|
|
const featuredProviders =
|
|
await import("../../src/app/(dashboard)/dashboard/providers/featuredProviders.ts");
|
|
|
|
// ── Kimi (Moonshot AI) official-partnership featured-first ordering (2026-07) ──
|
|
// UI-only pin: Kimi-family providers must render first within whichever
|
|
// category/group they appear in on the providers dashboard. This must never
|
|
// touch routing/fallback order (open-sse/config/providerRegistry.ts) — only how
|
|
// filterConfiguredProviderEntries sorts a category's card grid.
|
|
|
|
test("featuredProviders identifies every Kimi/Moonshot dashboard provider id", () => {
|
|
const { isFeaturedProviderId, isKimiPartnerProviderId, KIMI_BRAND_COLOR } = featuredProviders;
|
|
|
|
for (const id of ["kimi", "kimi-coding", "kimi-coding-apikey", "kimi-web", "moonshot"]) {
|
|
assert.equal(isFeaturedProviderId(id), true, `${id} should be featured`);
|
|
assert.equal(isKimiPartnerProviderId(id), true, `${id} should be a Kimi partner id`);
|
|
}
|
|
|
|
// Unrelated providers must not be swept in.
|
|
for (const id of ["openai", "claude", "moonshot-labs", "kimichat", null, undefined, ""]) {
|
|
assert.equal(isFeaturedProviderId(id), false, `${id} should not be featured`);
|
|
assert.equal(isKimiPartnerProviderId(id), false, `${id} should not be a Kimi partner id`);
|
|
}
|
|
|
|
assert.equal(KIMI_BRAND_COLOR, "#1783FF");
|
|
});
|
|
|
|
test("sortProviderEntriesFeaturedFirst pins Kimi providers first, alphabetical otherwise", () => {
|
|
const entry = (providerId: string, name: string) => ({
|
|
providerId,
|
|
provider: { id: providerId, name },
|
|
stats: { total: 0 },
|
|
displayAuthType: "apikey",
|
|
toggleAuthType: "apikey",
|
|
});
|
|
|
|
// Deliberately alphabetically-earlier non-Kimi providers ("Acme", "Anthropic")
|
|
// so the assertion actually proves the pin overrides pure alphabetical order,
|
|
// not merely that Kimi happens to sort first on its own.
|
|
const entries = [
|
|
entry("zulu-provider", "Zulu Provider"),
|
|
entry("moonshot", "Kimi"),
|
|
entry("acme", "Acme"),
|
|
entry("kimi-web", "Kimi Web"),
|
|
entry("anthropic-clone", "Anthropic Clone"),
|
|
entry("kimi-coding", "Kimi Code CLI"),
|
|
];
|
|
|
|
const sorted = providerPageUtils.sortProviderEntriesFeaturedFirst(entries);
|
|
|
|
// "Kimi" (moonshot's rebranded display name) alphabetically precedes "Kimi
|
|
// Code CLI" and "Kimi Web" — a shorter string that is a prefix of a longer
|
|
// one sorts first — so moonshot leads the featured group.
|
|
assert.deepEqual(
|
|
sorted.map((e) => e.providerId),
|
|
["moonshot", "kimi-coding", "kimi-web", "acme", "anthropic-clone", "zulu-provider"],
|
|
"featured (Kimi) entries come first, each group alphabetical among itself"
|
|
);
|
|
});
|
|
|
|
test("filterConfiguredProviderEntries surfaces Kimi first within a mixed category (oauth section shape)", () => {
|
|
const entries = [
|
|
{ providerId: "claude", provider: { name: "Claude" }, stats: { total: 1 }, displayAuthType: "oauth", toggleAuthType: "oauth" },
|
|
{ providerId: "kimi-coding", provider: { name: "Kimi Code CLI" }, stats: { total: 0 }, displayAuthType: "oauth", toggleAuthType: "oauth" },
|
|
{ providerId: "amazon-q", provider: { name: "Amazon Q" }, stats: { total: 0 }, displayAuthType: "oauth", toggleAuthType: "oauth" },
|
|
];
|
|
|
|
// No filters applied (showConfiguredOnly=false) — pure ordering behavior.
|
|
const visible = providerPageUtils.filterConfiguredProviderEntries(entries, false);
|
|
assert.deepEqual(
|
|
visible.map((e) => e.providerId),
|
|
["kimi-coding", "amazon-q", "claude"],
|
|
"kimi-coding is pinned first even though 'Amazon Q' and 'Claude' sort earlier alphabetically"
|
|
);
|
|
});
|
|
|
|
test("sortProviderEntriesFeaturedFirst leaves a category with no featured providers alphabetical", () => {
|
|
const entry = (providerId: string, name: string) => ({
|
|
providerId,
|
|
provider: { name },
|
|
stats: { total: 0 },
|
|
displayAuthType: "apikey",
|
|
toggleAuthType: "apikey",
|
|
});
|
|
const entries = [entry("zulu", "Zulu"), entry("acme", "Acme"), entry("mid", "Mid")];
|
|
|
|
const sorted = providerPageUtils.sortProviderEntriesFeaturedFirst(entries);
|
|
assert.deepEqual(
|
|
sorted.map((e) => e.providerId),
|
|
["acme", "mid", "zulu"]
|
|
);
|
|
});
|
|
|
|
// ── Section-scoped proof against the REAL catalog (not synthetic mocks) ───────
|
|
// page.tsx builds each dashboard section as
|
|
// buildStaticProviderEntries(category) -> filterConfiguredProviderEntries(...).
|
|
// These tests replicate that exact call chain per real section to prove where
|
|
// each real Kimi/Moonshot card actually lands — the 3 sections that render a
|
|
// Kimi-family card today: OAuth (kimi-coding), Web Cookie (kimi-web), and the
|
|
// "LLM providers" subsection of API Key (moonshot). kimi-coding-apikey and kimi
|
|
// are both hiddenFromDashboard and never render their own card in ANY section
|
|
// (kimi-coding-apikey folds into the kimi-coding card's own connection flow —
|
|
// see KimiCodeAuthMethodModal.tsx; verified below).
|
|
|
|
test("real OAuth section pins kimi-coding first (page.tsx's oauthProviderEntries shape)", () => {
|
|
const getProviderStats = () => ({ total: 0 });
|
|
const oauthEntriesAll = providerPageUtils.buildStaticProviderEntries("oauth", getProviderStats);
|
|
const oauthEntries = providerPageUtils.filterConfiguredProviderEntries(oauthEntriesAll, false);
|
|
|
|
assert.ok(oauthEntries.length > 5, "sanity: the real OAuth section has many providers");
|
|
assert.equal(
|
|
oauthEntries[0].providerId,
|
|
"kimi-coding",
|
|
"kimi-coding (Kimi Code CLI) must be the first card in the real OAuth section"
|
|
);
|
|
});
|
|
|
|
test("real Web Cookie section pins kimi-web first (page.tsx's webCookieProviderEntries shape)", () => {
|
|
const getProviderStats = () => ({ total: 0 });
|
|
const webCookieEntriesAll = providerPageUtils.buildStaticProviderEntries(
|
|
"web-cookie",
|
|
getProviderStats
|
|
);
|
|
const webCookieEntries = providerPageUtils.filterConfiguredProviderEntries(
|
|
webCookieEntriesAll,
|
|
false
|
|
);
|
|
|
|
assert.ok(webCookieEntries.length > 5, "sanity: the real Web Cookie section has many providers");
|
|
assert.equal(
|
|
webCookieEntries[0].providerId,
|
|
"kimi-web",
|
|
"kimi-web (Kimi Web) must be the first card in the real Web Cookie section"
|
|
);
|
|
});
|
|
|
|
test("real API Key -> LLM subsection pins moonshot first (page.tsx's llmProviderEntries shape)", () => {
|
|
const getProviderStats = () => ({ total: 0 });
|
|
const apiKeyEntriesAll = providerPageUtils.buildStaticProviderEntries("apikey", getProviderStats);
|
|
// Mirrors page.tsx's llmProviderEntriesAll filter exactly (moonshot is not an
|
|
// image/aggregator/enterprise-cloud/video/embedding-rerank provider).
|
|
const llmEntriesAll = apiKeyEntriesAll.filter(
|
|
(entry) =>
|
|
!providers.IMAGE_ONLY_PROVIDER_IDS.has(entry.providerId) &&
|
|
!providers.AGGREGATOR_PROVIDER_IDS.has(entry.providerId) &&
|
|
!providers.ENTERPRISE_CLOUD_PROVIDER_IDS.has(entry.providerId) &&
|
|
!providers.VIDEO_PROVIDER_IDS.has(entry.providerId) &&
|
|
!providers.EMBEDDING_RERANK_PROVIDER_IDS.has(entry.providerId)
|
|
);
|
|
const llmEntries = providerPageUtils.filterConfiguredProviderEntries(llmEntriesAll, false);
|
|
|
|
assert.ok(llmEntries.length > 5, "sanity: the real API Key -> LLM subsection has many providers");
|
|
assert.equal(
|
|
llmEntries[0].providerId,
|
|
"moonshot",
|
|
"moonshot (displayed as 'Kimi', where kimi-k3 lives) must be the first card in the real API Key -> LLM subsection"
|
|
);
|
|
|
|
// kimi-coding-apikey and kimi (both hiddenFromDashboard) never surface as
|
|
// their own card here or in any other section — see the dedicated test below.
|
|
assert.equal(llmEntries.some((e) => e.providerId === "kimi-coding-apikey"), false);
|
|
assert.equal(llmEntries.some((e) => e.providerId === "kimi"), false);
|
|
});
|
|
|
|
test("kimi-coding-apikey and kimi never render as their own dashboard card in ANY section (hiddenFromDashboard)", () => {
|
|
const getProviderStats = () => ({ total: 0 });
|
|
const categories = [
|
|
"no-auth",
|
|
"oauth",
|
|
"web-cookie",
|
|
"local",
|
|
"search",
|
|
"audio",
|
|
"upstream-proxy",
|
|
"apikey",
|
|
"cloud-agent",
|
|
] as const;
|
|
|
|
for (const category of categories) {
|
|
const entries = providerPageUtils.buildStaticProviderEntries(category, getProviderStats);
|
|
assert.equal(
|
|
entries.some((e) => e.providerId === "kimi-coding-apikey"),
|
|
false,
|
|
`kimi-coding-apikey must not appear as its own card in the "${category}" category`
|
|
);
|
|
assert.equal(
|
|
entries.some((e) => e.providerId === "kimi"),
|
|
false,
|
|
`kimi (legacy alias) must not appear as its own card in the "${category}" category`
|
|
);
|
|
}
|
|
});
|