Churn-absorption log

Every provider break this library absorbed on your behalf, newest first.

The point of a sandbox abstraction is that a provider's breaking change costs you a version bump instead of a migration. That claim is only worth as much as its evidence, so each absorbed break is written down here — including the ones that were not absorbed cleanly.

Each entry records the date, the provider and the versions affected, what broke, what changed here, and whether you need to act. An entry lands in the same release as the fix, and in CHANGELOG.md as well. The procedure is Provider churn in the runbook.

Entries

None yet — the first release has not shipped.

An empty log and a busy one tell different stories, and both are honest. This one is empty because there is nothing to report, not because nothing is being watched: the nightly latest-SDK canary runs every provider SDK unpinned to find these breaks before you do. The weekly framework matrix is not built yet.