Framework Upgrades Change Adapter Behavior More Than Release Notes Admit

Framework releases change tool semantics, defaults, and error shapes in ways their release notes rarely enumerate, and adapters inherit all of it silently.

The framework’s release notes describe what its authors think they changed. The adapter experiences what actually changed. These lists overlap imperfectly.

Post-upgrade verification

• Re-run the capability probe suite against the new version.
• Diff error shapes and retry semantics against the previous baseline.
• Hold rollout until parity with other adapters is re-confirmed.

Use the adapter system, changelog, and benchmarks to treat every framework bump as an adapter behavior change.