Fix GLM-5.2 standalone model bucket

[adibarra]

Summary

• map glm5.2 to its own GLM-5.2 dashboard model
• keep GLM-5 and GLM-5.1 grouped together
• add a dedicated GLM-5.2 compare slug and query bucket

Verification

• focused Vitest: 96 tests passed
• pnpm typecheck
• formatting check on changed files

---

Note

Low Risk
Scoped model-mapping and URL routing changes with updated tests; no auth or data-mutation logic, though a missed caller could still query the wrong DB bucket.

Overview
GLM-5.2 is no longer rolled into the shared GLM-5 display group. The glm5.2 DB key now maps to GLM-5.2, while GLM-5 keeps only glm5 and glm5.1.

The dashboard gains a Model.GLM_5_2 entry (labels, prefix glm5.2), and artifact name parsing matches prefixes longest-first so glm5.2 is not swallowed by glm5.

Compare URLs add a dedicated glm-5-2 slug (queries only glm5.2); glm-5-1 is narrowed to GLM 5/5.1. Compare SSR accepts GLM-5.2 as a known ?g_model= override.

^{Reviewed by Cursor Bugbot for commit 455d103. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
inferencemax-app	Ready	Preview, Comment	Jul 18, 2026 8:34pm

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit cf5fce9. Configure here.}