[chr-hertel]

Adds a TL;DR, moves the namespace split and cross-cutting changes above the components, groups Server and Client entries by theme and merges the duplicated ones, like the 0.9.0 changelog. JSON-RPC folds into Schema, where MessageFactory lives now.

[Copilot]

🟡 Changes recommended

The changelog incorrectly attributes rejection of all 3xx responses to all three classes, although AuthenticatingHttpClient returns redirects unchanged and the error guarantee applies only to HttpTransport.

1 open issue

• Limit redirect rejection guarantee to HttpTransport · New

What changed in this PR

Reorganizes the SDK’s 0.10.0 changelog to make release highlights and migration details easier to scan, following the 0.9.0 layout. No runtime code changes.

Changes:

• Adds a TL;DR and places namespace and cross-cutting changes before component details.
• Groups Server and Client entries by theme and merges duplicate entries.
• Moves JSON-RPC entries into Schema, where MessageFactory resides.

File	Description
CHANGELOG.md	Condenses and groups the 0.10.0 release notes.

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

The changelog incorrectly implies handlers run under an event loop by default, when this behavior is opt-in via Builder::setFiberScheduler().

No open issues 🎉

1 previously missed issue

In code that hasn't changed since last review

Clarify event-loop support requires setFiberScheduler()

CHANGELOG.md:14

Event-loop execution is opt-in (Builder::$fiberScheduler defaults to null), so this reads as a new default execution model that the SDK does not actually introduce. Please describe support for running handlers under an event loop with Builder::setFiberScheduler(), rather than stating that handlers run under one.

1 resolved since last review

• Limit redirect rejection guarantee to HttpTransport

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

The changelog reorganization has no active review issues.

No open issues 🎉

_{Review effort: Balanced}