Skip to content

fix(ai): restore CI after catalog refresh - #265

Merged
Pepps233 merged 2 commits into
mainfrom
fix/main-ci
Oct 17, 2026
Merged

Pepps233 merged 2 commits into
mainfrom
fix/main-ci

Conversation

@Pepps233

@Pepps233 Pepps233 commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Fix the main CI build failure after the live catalog added Google-format OpenCode Go models.

Those models now use the existing Google streaming adapter instead of failing compilation or returning a missing-implementation error.

Reasoning

The provider must support the APIs advertised by its generated catalog.

The next validation stages also exposed obsolete model IDs and an attribution allowlist entry that predates the merged README wording.

Changes

  • Register the Google adapter for OpenCode Go and test its endpoint and credential routing with mocked HTTP.
  • Update model tests to use available NVIDIA and OpenCode models with equivalent coverage.
  • Match the existing README attribution in the exact-content allowlist.
  • Update the Kimi K3 pricing expectation to include the catalog's default cache-write rate, consistent with the provider's separate cache-write billing: https://platform.kimi.ai/docs/pricing/chat.

Testing

  • Reproduced the original catalog-generation/typecheck failure and missing-adapter runtime error before the fix.
  • AI package build typecheck and npm run check pass.
  • Focused tests: 30 passed; 234 credential-dependent E2E cases skipped in an isolated environment.
  • Full ./test.sh passes with loopback-server and process-inspection permissions; the initial sandboxed attempt hit EPERM restrictions.
  • All eight CI jobs pass on 83ebaa7e4: https://github.com/diffexai/diffex/actions/runs/39064167925.

- Register Google streaming for newly listed OpenCode Go models.
- Keep model tests and the attribution inventory aligned with current inputs.
- Cover OpenCode Go routing and credentials without paid provider calls.
@Pepps233 Pepps233 self-assigned this Oct 17, 2026
- Match the current catalog cache-write rate instead of requiring a zero rate.
- Preserve the pricing regression coverage uncovered by Linux CI.
@Pepps233
Pepps233 requested a review from Issacboy123 October 17, 2026 19:56

@Issacboy123 Issacboy123 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@Pepps233
Pepps233 merged commit 280fdda into main Oct 17, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants