feat: add Zhipu Coding Plan provider (domestic China)

[mengfanbo123]

Summary

Adds a new Zhipu quota provider for the domestic China Zhipu Coding Plan (bigmodel.cn), mirroring the existing Z.ai provider (api.z.ai).

What's new

• New provider: zhipu — queries https://bigmodel.cn/api/monitor/usage/quota/limit
• Auth resolution: ZHIPU_API_KEY / ZHIPU_CODING_PLAN_API_KEY env vars → opencode.jsonc provider config (zhipu, zhipu-coding-plan, glm-coding-plan) → auth.json
• Full feature parity with Z.ai provider: TUI sidebar, toast notifications, /quota command status report
• Same response format as Z.ai (5h/weekly token windows + MCP monthly limit)

Files changed

File	Change
src/lib/zhipu.ts	New — quota fetcher (mirrors zai.ts)
src/lib/zhipu-auth.ts	New — auth resolution (mirrors zai-auth.ts)
src/providers/zhipu.ts	New — provider wrapper (mirrors zai.ts)
src/providers/registry.ts	Register zhipuProvider
src/lib/provider-metadata.ts	Add zhipu canonical ID, labels, synonyms, runtime IDs, shape
src/lib/types.ts	Add zhipu-coding-plan to AuthData interface
src/lib/quota-status.ts	Add zhipu diagnostics section for /quota command

Usage

Add to opencode.jsonc:

{
  "experimental": {
    "quotaToast": {
      "enabledProviders": ["zai", "zhipu", "kimi-code"]
    }
  }
}

And configure the provider:

{
  "provider": {
    "zhipu-coding-plan": {
      "name": "Zhipu Coding Plan",
      "options": { "apiKey": "{env:ZHIPU_API_KEY}" },
      // ...models...
    }
  }
}

Testing

• npm run typecheck ✅
• npm run build ✅
• Published as @mingxy/[email protected] and tested in production

Why separate provider?

Z.ai (international) and Zhipu (domestic China) use different API endpoints and API keys. They serve different user bases and need independent auth resolution. The domestic endpoint is bigmodel.cn (not api.z.ai).

[mengfanbo123]

[slkiser]

@mengfanbo123 Thanks for the contribution, I'll take a look!

[slkiser]

@mengfanbo123 Thanks for the contribution