docs(releases): correct the falsified batch-cap claim on the 17.0 release page (#18854) - #18907
Merged
Merged
Conversation
…ease page (#18854) The 17.0 release page told bulk callers the cap was "raisable to 1000". That claim was ruled false on 2026-09-07: `batch.maxBatchSize` is embedder policy, written only by a host that constructs the server; `os serve` and the dev plugins pass none, so a CLI-started deployment is at 200 and no published surface raises it. Eight carriers were corrected under that ruling; this is the ninth and last, amended in the entry itself with a dated erratum, in the shape PR #18852 established. Docs-only, no source, no schema, no changeset. Claude-Session: https://claude.ai/code/session_01Wj1HUjzyeiBQ8atRf1ZhaL Co-authored-by: Claude <noreply@anthropic.com>
github-actions
Bot
added
the
documentation
hotlong
added
the
skip-changeset
Claude
os-zhuang
approved these changes
Sep 20, 2026
os-zhuang
marked this pull request as ready for review
September 20, 2026 15:13
os-zhuang
enabled auto-merge
September 20, 2026 15:13
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
2 participants
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.
Fixes #18854
The 17.0 release page (
content/docs/releases/v17/17-0.mdx) told bulk callers the batch cap was "raisable to 1000". That claim was ruled false on 2026-09-07 (director seat, summon #17, decision batch #2, maintainer 「同意」):batch.maxBatchSizeis embedder policy —RestServerConfig.batch.maxBatchSize, 1..1000, default 200 — written only by a host that constructs the server;os serveand the dev plugins pass none, so a CLI-started deployment is at 200 and no published surface raises it.Eight carriers were corrected under that ruling (#15543, #16801, #16940, #17183, #18739, #18740 ×8 sites via PR #18852). This is the ninth and last: the bullet is corrected in the entry itself and carries a dated erratum, in the shape PR #18852 established.
AGENTS.md's Documentation Guardrails row forcontent/docs/releases/(factual error on a releases page → dedicated docs-only PR, never a rider). Opened by the director seat executing decision batch 🔗 Broken links detected in documentation #155 item 1 (maintainer 「同意」 to B on [finding]content/docs/releases/v17/17-0.mdx:1734still tells bulk callers the batch cap is "raisable to 1000" — the last live carrier of the falsified claim, on the one tree every delivering agent is prohibited from editing #18854); the dispatched dev correctly declined this site underos-dev.md:67, whose alignment is its own card.Clause-②: no— no contract surface. No changeset (docs-only;skip-changesetlabel applied).Branch:this branch,Clause-②: no— both carriers agree;check-clause2-carriers --pair 18907exit 0 locally).🤖 Generated with Claude Code
https://claude.ai/code/session_01Wj1HUjzyeiBQ8atRf1ZhaL
Generated by Claude Code