[WRONG BRANCH] fix(providers): disable unverified Zhipu live model discovery

[luvs01]

Motivation

• The Zhipu BigModel registry row shipped static model metadata but did not explicitly disable live /models discovery, which can cause the runtime to probe the unverified endpoint and replace the static catalog with an empty live response.

Description

• Set liveModels: false on the zhipu-bigmodel entry in src/providers/registry.ts to keep the static catalog authoritative and avoid probing the unverified /api/paas/v4/models endpoint.
• Tweak the nearby comment to reflect that live discovery is unverified and should remain disabled until verified.
• Add a focused regression test in tests/provider-registry-parity.test.ts asserting the registry entry and its derived provider seed both have liveModels: false.

Testing

• Ran bun run typecheck, which completed successfully.
• Ran bun run privacy:scan, which passed.
• Ran the focused test file with bun test tests/provider-registry-parity.test.ts, which failed to complete in this environment due to a Bun/runtime import error (Export named 'zstdDecompressSync' not found in module 'node:zlib') preventing the focused verification here.
• Ran the broader bun run test suite locally in this environment; many tests passed but the run encountered unrelated timeouts in tests/grok-models-effort-list.test.ts, so a full-suite green was not achieved within this session.

---

Codex Task

[coderabbitai]

Warning

Review limit reached

@luvs01, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: a8a259db-f473-41ac-afcf-2879e662b21d

📥 Commits

Reviewing files that changed from the base of the PR and between 6d881db and 53b0152.

📒 Files selected for processing (2)

• src/providers/registry.ts
• tests/provider-registry-parity.test.ts

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

✅ Deterministic PR hygiene checks passed.

[github-actions]

⏳ DRAFT

• wrong target branch (main); retarget to dev.

What to do

• Retarget this PR to dev — all contributions go to dev.

Its title has been prefixed with [WRONG BRANCH].
This pull request was already a draft. Its draft status will be preserved after every issue above is resolved.