docs(config): align max_turns example with actual default (90)

[waroffchange]

Summary

The example config (cli-config.yaml.example) shipped max_turns: 60, but the actual default used across the codebase is 90:

• hermes_cli/config.py ? DEFAULT_CONFIG["agent"]["max_turns"] = 90
• hermes_cli/_parser.py ? --max-turns help text states "default: 90"
• AGENTS.md ? AIAgent.__init__(max_iterations: int = 90)

This aligns the example file with the real default and adds the (default: 90) annotation, matching the style already used for other keys in the same file (e.g. compression:).

Validation

• Docs/config-only change - no runtime code touched
• YAML validity checked
• Checked open PRs: no overlap (fix(cli): unify clarify timeout config key across CLI and gateway #25865 touches a different file)
• Checked merged history: PR fix(setup): align max_turns default to 90 across docs and prompts #4020/fix(setup): default max agent turns to 90 (#4018) #4031 set the real default to 90 but never updated this example file - this PR closes that gap

Related

Related to the default-value work done in #4020 / #4031 (example file was missed)

[teknium1]

Thanks for correcting this stale example. Current main still has max_turns: 60 in cli-config.yaml.example:684, while the actual default is 90 in hermes_cli/config.py:991 and the CLI help states the same at hermes_cli/_parser.py:385. The PR’s focused documentation change matches current behavior.

Automated hermes-sweeper review.

[teknium1]

Thanks @waroffchange — you were right about the example/default drift. Your commit was cherry-picked (authorship preserved) into #72182 and merged; the only adjustment was updating the target value from 90 to 500, since #72176 raised the actual default after your PR was opened. Closing in favor of #72182.