Skip to content

Lock GLM bridge to Zhipu GLM-5.2#40

Merged
yangfei222666-9 merged 1 commit into
mainfrom
glm52-only-provider-lock
Jun 24, 2026
Merged

Lock GLM bridge to Zhipu GLM-5.2#40
yangfei222666-9 merged 1 commit into
mainfrom
glm52-only-provider-lock

Conversation

@yangfei222666-9

Copy link
Copy Markdown
Owner

Summary

  • Lock the GLM smoke probe and candidate-review envelope to Zhipu GLM-5.2 only.
  • Remove dynamic model and endpoint selection from the local bridge scripts.
  • Remove non-Zhipu API-key environment fallbacks so the only accepted key source is ZHIPUAI_API_KEY.

Scope

Changed files:

  • tools/glm52_smoke.py
  • tools/glm52_candidate_review.py

Validation

Fresh local checks before push:

  • python3 -m py_compile tools/glm52_smoke.py tools/glm52_candidate_review.py -> PASS
  • GLM smoke dry-run -> provider_called=false, api_key_read=false
  • candidate-review dry-run JSON check -> PASS
  • dynamic --model / --endpoint rejection checks -> PASS
  • static lock scan for removed fallback providers/envs/endpoints -> PASS

Boundaries

  • No provider/API call was made.
  • No API key was read or printed.
  • This remains candidate bridge hardening until PR review/CI completes.
  • This does not claim provider readiness, long-task readiness, or runtime readiness.

@yangfei222666-9 yangfei222666-9 marked this pull request as ready for review June 24, 2026 14:54
@yangfei222666-9 yangfei222666-9 merged commit 54c2b63 into main Jun 24, 2026
8 checks passed
@yangfei222666-9 yangfei222666-9 deleted the glm52-only-provider-lock branch June 24, 2026 15:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant