[docs] Self-healing documentation fixes from issue analysis - 2026-08-07 - #51235
Merged
pelikhan merged 1 commit intoAug 8, 2026
Merged
Conversation
Two rows in the engine feature comparison table were both labeled `max-turns` with contradictory support values, making the table self-contradictory. Per the explanatory prose below the table, the second row describes the deprecated nested `engine.max-turns` alias (Claude-only), not the top-level field. Co-Authored-By: Claude <noreply@anthropic.com>
pelikhan
marked this pull request as ready for review
August 8, 2026 00:29
pelikhan
deleted the
doc-healer/engines-max-turns-disambiguation-235bac4f787b6e02
branch
August 8, 2026 00:30
Contributor
Author
|
✅ Test Quality Sentinel completed test quality analysis. No test files were added or modified in this PR. Test Quality Sentinel skipped.
|
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies two max-turns configuration paths in the engine comparison table.
Changes:
- Qualifies the top-level
max-turnsfield. - Renames the nested alias to
engine.max-turns.
Show a summary per file
| File | Description |
|---|---|
docs/src/content/docs/reference/engines.md |
Disambiguates max-turns table rows. |
Review details
Tip
Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Balanced
| | `max-turns` (AWF invocation cap; `max-runs` deprecated) | ✅ | ✅ | ✅ | ✅ | ✅ | | ||
| | `max-turns` | ❌ | ✅ | ❌ | ❌ | ❌ | | ||
| | `max-turns` (top-level AWF invocation cap; `max-runs` deprecated) | ✅ | ✅ | ✅ | ✅ | ✅ | | ||
| | `engine.max-turns` (deprecated nested alias) | ❌ | ✅ | ❌ | ❌ | ❌ | |
This was referenced Aug 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Documentation fix disambiguating a duplicate
max-turnsrow in the engine feature-comparison table on the Engines reference page.Key Change
The table previously listed two rows both labeled
max-turns, which was ambiguous. This PR clarifies them:`max-turns` (AWF invocation cap; `max-runs` deprecated)`max-turns` (top-level AWF invocation cap; `max-runs` deprecated)`max-turns``engine.max-turns` (deprecated nested alias)Files Changed
docs/src/content/docs/reference/engines.md— 1 file, 2 lines changed (2 additions, 2 deletions)Impact
References: