[Fuma2514]

Fixes #67323.

Since #60441 (v26.0.0, semver-major), readable.read() without a size argument returns one buffered chunk per call, but doc/api/stream.md still said it returns "all of the data contained in the internal buffer". This PR:

• Rewords that paragraph to describe the current behaviour and documents the migration hint from stream: readable read one buffer at a time #60441 (readable.read(readable.readableLength), with the readable.read(0) caveat).
• Adds a changes: entry for v26.0.0 linking stream: readable read one buffer at a time #60441.

Docs only, no code changes. Verified that no other part of the example text depends on the old wording; the while (null !== (chunk = readable.read())) loop example remains correct under the new behaviour (it now drains one chunk per iteration until null).

[github-actions]

Welcome to Node.js, and thank you for your first contribution!

Before review, please take a moment to read:

• the guide for first-time contributors
• the contribution and automation policies
• the pull request guide
• the AI use policy
• the Code of Conduct

Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal.

Caution

AgentScan found account activity patterns that may be consistent with automation. This is a heuristic, not proof that this pull request was opened by an agent or violates policy. AI-assisted contributions are permitted, but automated tooling must not open pull requests without advance approval, and contributors must personally understand, test, verify, and take responsibility for every submitted change. See the AgentScan analysis, AI use policy, and automation policy for additional context.