fix(setup): default max agent turns to 90 (#4018)

[avishj]

What does this PR do?

As described in #4018, there is an inconsistency between 60/90 for max agent turns. I've fixed it to be 90 consistently everywhere it was still at 60.

Related Issue

Fixes #4018

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

• cli-config.yaml.example: max_turns 60 -> 90
• cli.py: docstring default 60 -> 90
• environments/benchmarks/tblite/default.yaml: max_agent_turns 60 -> 90
• environments/benchmarks/tblite/local.yaml: max_agent_turns 60 -> 90
• environments/benchmarks/tblite/local_vllm.yaml: max_agent_turns 60 -> 90
• environments/benchmarks/terminalbench_2/default.yaml: max_agent_turns 60 -> 90
• website/docs/developer-guide/environments.md: Updated documentation examples for max_agent_turns default to 90

How to Test

1. Install hermes via setup-hermes.sh.
2. Prompt shows 90 in both locations.

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 (existing PR is incorrect)
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've tested on my platform: macOS 15.7.3

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings)
• I've updated cli-config.yaml.example if I added/changed config keys

Screenshots / Logs

[alt-glitch]

Likely duplicate of #4020 — both fix the same max_turns 60/90 inconsistency from #4018.

[alt-glitch]

Likely duplicate of #4020 — both fix the same max_turns 60/90 inconsistency from #4018.

[teknium1]

Thanks for tracing the inconsistent max-turn documentation.

Problems

• This branch is now conflicting: its four environments/benchmarks/... YAML targets and website/docs/developer-guide/environments.md are absent on current main. The remaining two corrections are still applicable: cli-config.yaml.example:684 and cli.py:15795 still say 60, while hermes_cli/config.py:991 defines the runtime default as 90.

Suggested changes

• Salvage the two live documentation/example edits and drop the removed-file hunks. Current CLI coverage already verifies the runtime default is 90 in tests/cli/test_cli_init.py:60-72.

Automated hermes-sweeper review.