fix(models): support glm-5.2, kimi-k2.7-code + merge live/curated mod…

[adelvillar1]

…el lists

Three changes to fix newly-released models not appearing in the picker or being capped at wrong context lengths:

1. Add glm-5.2 to zai provider's static model list
2. Add kimi-k2.7-code to kimi-coding provider's static model list
3. Fix generic live-fetch path in provider_model_ids() to MERGE curated entries with live /v1/models results instead of replacing them — same pattern already used by the Anthropic path. Providers like Z.AI and Kimi don't list new models in /v1/models immediately even though inference works, causing curated entries to silently disappear.
4. Add glm-5.2 context length (1M tokens) to DEFAULT_CONTEXT_LENGTHS, before the generic 'glm' catch-all (202752) that was capping it at ~200K via substring matching.

What does this PR do?

Related Issue

Fixes #

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 🔒 Security fix
• 📝 Documentation update
• ✅ Tests (adding or improving test coverage)
• ♻️ Refactor (no behavior change)
• 🎯 New skill (bundled or hub)

Changes Made

How to Test

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform:

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

• This skill is broadly useful to most users (if bundled) — see Contributing Guide
• SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
• No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
• I've tested the skill end-to-end: hermes --toolsets skills -q "Use the X skill to do Y"

Screenshots / Logs

[teknium1]

Thanks for jumping on GLM-5.2. We merged the broader GLM-5.2 support via #45695, preserving @am423's authorship in git history:

#45695

That landed the 1M context metadata plus the Z.AI model picker/setup/auth probing/fallback surfaces, so this PR is now covered. Closing as duplicate, with appreciation for helping validate the same issue.