mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-08-24 16:12:23 +03:00
d861b76b5f
Three stale unit tests went red across PRs #11301/#11303/#11304 because their mocks/fixtures predated intentional contract changes merged the same day: - compression-cli-rest-fallback-6571.test.ts: #10960 moved the CLI's MCP transport from the never-mounted /api/mcp/tools/call to the real Streamable HTTP endpoint /api/mcp/stream. The REST-fallback trigger in this test's fetch mock still targeted the retired path, so mcpCallTool() threw on an unmocked fetch instead of exercising the fallback. Updated the mock to intercept /api/mcp/stream. - memory-system-first-6135.test.ts: #11290/#11303 added a Claude-family reroute to the leading-system-message placement (Opus 5 rejects a system message spliced right after a plain-text assistant turn). The regression test used "anthropic" as its NON-Claude-specific example, which is now classified as Claude-family and no longer exercises the plain cache-safe splice path it targets. Switched the fixture provider to "openai". - kiro-auto-import-name-dedup-3615.test.ts: #10815/#11287 hardened findKiroConnectionByIdentity to require an account-level identifier (email/clientId) alongside a matching profileArn before trusting the match, since distinct Builder ID accounts can share a CodeWhisperer profile ARN. Extended findKiroConnectionByProfileArn (test-only helper) with an optional account-identity param, and added a companion test documenting the new ARN-alone-is-untrusted safety behavior. All three are genuine stale-test drift, not production bugs: the code changes were deliberate fixes from other reviewed PRs; only the tests' fixtures needed to catch up.