docs(releases): correct the falsified batch-cap claim on the 17.0 release page (#18854) (#18907)

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.maxBatchSize` is embedder policy —
`RestServerConfig.batch.maxBatchSize`, 1..1000, default 200 — 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 (#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.

- **Dedicated docs-only PR** per `AGENTS.md`'s Documentation Guardrails
row for `content/docs/releases/` (factual error on a releases page →
dedicated docs-only PR, never a rider). Opened by the director seat
executing decision batch #155 item 1 (maintainer 「同意」 to B on #18854);
the dispatched dev correctly declined this site under `os-dev.md:67`,
whose alignment is its own card.
- Diff: one file, one bullet (+8/−2). No source, no schema, no export,
no test.
- `Clause-②: no` — no contract surface. No changeset (docs-only;
`skip-changeset` label applied).
- Claim record on the card: objectstack#18854 comment 5725535123
(`Branch:` this branch, `Clause-②: no` — both carriers agree;
`check-clause2-carriers --pair 18907` exit 0 locally).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

https://claude.ai/code/session_01Wj1HUjzyeiBQ8atRf1ZhaL

---
_Generated by [Claude Code](https://claude.ai/code)_

Co-authored-by: hotlong <hotlong@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>

Author: hotlong

content/docs/releases/v17/17-0.mdx

@@ -1731,9 +1731,15 @@ This section covers the window bundled at **`rc.0`**: `cf2d56e32a11 →
 - **Raw-`fetch` readers** of the settings / datasource-admin /
   external-datasource / package / share-link routes: read the payload under
   `data` and errors as `error.code` / `error.message` (#3843, #3983).
-- **Bulk callers:** stay under `batch.maxBatchSize` (default 200, raisable to
-  1000) or chunk; stop sending `object` / `context` in bulk bodies (ignored);
+- **Bulk callers:** stay under `batch.maxBatchSize` (200 unless the host
+  embedding the server passed another value — no shipped boot path does) or
+  chunk; stop sending `object` / `context` in bulk bodies (ignored);
   read `deleteMany`'s new structured `BatchUpdateResponse` (#3939, #3897).
+  *Erratum, 2026-09-18 — this bullet said the cap was "raisable to 1000". The
+  cap is embedder policy (`RestServerConfig.batch.maxBatchSize`, 1..1000,
+  default 200), 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 (ruling 2026-09-07; #18854).*
 - **Analytics clients:** send the bare `AnalyticsQuery` shape (`where`, not
   `filters`; no `{cube, query, format}` envelope) (#3878). Embedded /
   programmatic hosts must install `@objectstack/service-analytics` — the