Merge main into testnet-canary (v10.0.9 version bump)

[branarakic]

Routine post-release back-merge: brings the v10.0.9 lockstep version bump + CHANGELOG from main into testnet-canary, so canary reports 10.0.9 instead of 10.0.8. Conflict-free; no code changes.

🤖 Generated with Claude Code

[otReviewAgent]

🔵 Nit: Add the changelog link target with the release entry

Why it matters
This keeps release metadata self-contained and avoids letting the changelog’s navigation drift further from its declared format.

Suggestion
Either add [10.0.9] and refresh [Unreleased] at the footer in the same PR, or stop using reference-style release headings until the release tooling owns those links.

[branarakic]

Closing — this PR's code is already on main, so merging it would change nothing.

Evidence (verified 2026-08-06 against main @ 0277d82c6):

• git cherry origin/main reports no new patches — the backmerge is already reconciled in both directions (also a no-op against testnet-canary). Main is at 10.0.12; this branch carries the 10.0.9 bump.
• git merge-tree --write-tree origin/main 155ea26b4 returns main's exact tree (d1812f293) — a merge would be a no-op.

Closed as part of a sweep of open PRs whose code had already landed. Please reopen if this is wrong.