3.0 release notes and bump peer deps

Editor assessment

This header welds two dissimilar changes together — writing 3.0 release notes (docs) and bumping peer dependencies (chore/build) — so neither concern gets an accurate type, and git log gains one entry that means two things. More seriously, '3.0' plus peer-dep bumps smells like a major release where peer ranges were widened or raised; if any peer range dropped support, the spec expects a BREAKING CHANGE footer or a `!` marker, and there is none. The subject also lacks a leading imperative verb ('release notes and bump...' starts with a noun), reading as a list rather than an action. Splitting into `docs: add 3.0 release notes` and a separate dependency commit, with breaking status explicit, would serve changelogs and downgrade decisions far better.