Keep runs with different tuning apart in the report, and raise max_turns to 40 #52

Merged

dongar merged 1 commits from report-keeps-tuning-apart into main

2026-09-27 22:43:26 +00:00

Author	SHA1	Message	Date
dongarandClaude Opus 5.5	f881a18ca4	Keep runs with different tuning apart in the report, and raise max_turns to 40 CI / checks (push) Skipped CI / checks (pull_request) Successful in 1m11s Details The report grouped runs by model, serving note and task version, so runs made at different tuning were silently averaged together. Tuning is now part of the key, and a tuning column shows how a row's settings differ from today's defaults; it appears only when some row needs it. tuning.executor.max_turns goes from 24 to 40. On the harder benchmark tasks Haiku, the calibration ceiling, hit 24 on both refactor-rename runs and both long-milestone runs, one of which had finished the work. The cap guards against a model trying forever; it isn't a budget. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-09-27 22:25:14 +00:00

Author

SHA1

Message

Date

dongarandClaude Opus 5.5

f881a18ca4

Keep runs with different tuning apart in the report, and raise max_turns to 40

CI / checks (push) Skipped

CI / checks (pull_request) Successful in 1m11s

Details

The report grouped runs by model, serving note and task version, so
runs made at different tuning were silently averaged together. Tuning
is now part of the key, and a tuning column shows how a row's settings
differ from today's defaults; it appears only when some row needs it.

tuning.executor.max_turns goes from 24 to 40. On the harder benchmark
tasks Haiku, the calibration ceiling, hit 24 on both refactor-rename
runs and both long-milestone runs, one of which had finished the work.
The cap guards against a model trying forever; it isn't a budget.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-09-27 22:25:14 +00:00