fix: recognize GLM-5.2 ingest results

[adibarra]

Summary

• recognize the glm5.2 DB key and zai-org/GLM-5.2-FP8 model path
• group GLM-5.2 with the existing GLM-5 display family
• include GLM-5.2 in compare queries and labels

Verification

• direct resolveModelKey smoke check resolves the run payload to glm5.2
• DB normalizer tests: 64 passed
• constants tests: 11 passed
• frontend mapping tests: 85 passed
• changed files pass oxlint and oxfmt

After deployment, re-ingest source run 29654139122 to recover the previously skipped rows.

---

Note

Low Risk
Additive model-key and label updates with no auth or query-behavior changes beyond including the new bucket; re-ingest is noted for recovering skipped rows.

Overview
Adds GLM-5.2 as a first-class benchmark bucket so ingest no longer drops runs that report glm5.2 or zai-org/GLM-5.2-FP8. ETL maps those inputs to the glm5.2 DB key; shared constants fold glm5.2 into the existing GLM-5 display family alongside glm5 and glm5.1.

Compare pages keep the glm-5-1 slug but now query all three buckets and show labels as GLM 5/5.1/5.2 (dashboard model label updated to GLM5/5.1/5.2 744B). Tests cover the new mappings end to end.

^{Reviewed by Cursor Bugbot for commit 5efdf35. 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	Building	Preview, Comment	Jul 18, 2026 7:19pm

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

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

Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.

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

[cursor]

Missing FAQ GLM-5.2 override

Low Severity

Adding glm5.2 under the shared GLM-5 display name without a matching about-page override leaves /about listing GLM-5 twice and omitting GLM-5.2. Those FAQ maps intentionally expand point-release DB buckets (glm5.1, kimik2.6, kimik2.7-code, minimaxm2.7), so the new key needs the same treatment in both locale files.

 

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