CedarCopilot wants to merge 1 commit into staging from feat/glm-crm-updater-strategist-next-steps
Live on prod, watching, 1 day left
Libra has verdicts on 0 of 3 tracked behaviors on prod; 3 are still being checked. Libra checks hourly for 3 days after each deploy.
GLM_MODEL = 'glm-5.3-flash' to services/llm/models.ts (routed via Understudy exactly like SOL_MODEL/KIMI_MODEL, family: 'openai', never direct).-oss call sites currently on Kimi K3 over to GLM: crm-updater (which crm-updater-haiku shares a model branch with), strategist, next-steps.-oss workload names are model-agnostic, and cedar-oss-system-subagents is already active for <email> / <email>, so this takes effect immediately on deploy to staging.Same rigor applied after the earlier Sol reasoning_effort incident (PR #2850): confirmed with standalone scripts against the real Understudy gateway, not just a typecheck.
glm-5.3-flash produces real tool_calls (not text-embedded pseudo-XML) both with and without an explicit reasoning_effort: 'none'.reasoningEffort: 'none' is set) GLM has no known sensitivity to that provider option either way, so the existing THINKING_DISABLED_PROVIDER_OPTIONS at each call site is left unchanged.pnpm --filter @zero/server run types , cleanpnpm deps:check , no violationsreasoning_effort: 'none')🤖 Generated with Claude Code
https://claude.ai/code/session_012WwyQEcVnYQzkB4Fxsfpx6
The PR appears safe to merge as a staging-only model substitution with unchanged routing and workload contracts.
This PR introduces the Understudy-routed glm-5.3-flash model and switches three staging OSS agent paths from Kimi K3 to GLM while retaining their existing feature flags, workloads, provider options, and tool restrictions.
GLM_MODEL identifier.Reviews (1) · Last reviewed commit: "Swap GLM 5.3 Flash in for Kimi K3 on crm..."
Libra has not measured any production surfaces for this change yet.