docs(release): record the v1.1.2 hotfix in CHANGELOG and bd info

[maphew]

Why

v1.1.2 shipped on 2026-07-26, cut from the v1.1.0 tag (branch hotfix/v1.1.1) to carry the dolt#11131 aux-rekey encoding-drift fix so bricked 1.1.0 databases regain an upgrade path (#4380). Main never received the release metadata, so CHANGELOG.md jumps from [Unreleased] to [1.1.0] and bd info --changes doesn't mention 1.1.2. This is the standard post-hotfix back-merge of that metadata.

What

• CHANGELOG.md: add the [1.1.2] - 2026-07-26 section (verbatim from the release branch). It also records why there is no 1.1.1: the tag was cut but the release run died at the MCP package gate on a stale uv.lock before publishing anything, and the number was burned rather than moving the tag.
• cmd/bd/info.go: add the 1.1.2 versionChanges entry.

Deliberately not carried from the hotfix branch

• The fix itself — reaches main via fix(schema): survive dolt#11131 encoding drift in the aux row re-key (#4380) #5064, which stays gated on storage-owner review; this PR must not bypass that.
• Version bumps (version.go, winres, npm/MCP package manifests) — release-branch concerns; main builds stamp version via ldflags.
• The Docusaurus versioned-docs snapshot — main deleted the Docusaurus site in 52aea3f (Mintlify migration), so there is nothing to version here anymore.

Docs-only + one data literal; go build ./cmd/bd passes, gofmt clean.

claude-fable-5-medium on behalf of matt wilkie