Prepare 0.9.9 release

[noeltock]

Problem

The synced-pattern guard and native-block proof improvements since 0.9.8 are ready for a maintenance release.

Solution

Prepare 0.9.9 with matching package and lockfile versions and a changelog covering #120–#122 and #124.

Behaviour that changes or must stay true	Read first	Proof
CLI, package and installed skill report 0.9.9	package.json, package-lock.json	Release matrix and fresh consumer verification
Release notes describe shipped changes and bounded compatibility proof	CHANGELOG.md	Compared with commits since v0.9.8

Diff

+12 −4 · 3 files · version and changelog only relative to current main

-package / lockfile: 0.9.8
+package / lockfile: 0.9.9
+CHANGELOG: synced-pattern guard, native Tabs coverage and compatibility proof

Testing & verification

Reviewed revision: 9ab35117042e51d9e2e6c58e76e0982e27445bfb · Environment: Node 22.23.1, macOS.

• git diff --check: passed.
• PR Reject inline content in synced pattern references #124 passed Node 20/22/24, package-boundary and WordPress proof CI before merge.
• npm run release:check -- --matrix full-release-matrix --manual-review proof/reviews/0.9.0/owner-acceptance.json --receipt md/releases/next/local-release.json: passed on the reviewed commit with a clean worktree. Includes 724 tests (4 existing skips), clean consumers, skill installation and generated-plugin WordPress 7.1 proof.
• Fresh native Heading and Paragraph controls passed. The raw editor accessibility findings remain recorded under the existing scoped upstream exceptions; automated and release acceptance both passed.
• Exact-version CI passed Node 20.19.0, 22.13.0 and 24.0.0, package-boundary and WordPress proof: https://github.com/humanmade/block-runner/actions/runs/37096514926

Not verified: fresh manual acceptance or a model benchmark. Existing hash-bound owner acceptance and the documented native editor accessibility exceptions remain the release policy.

Risk / rollout

Version metadata and release notes only. The release remains on the existing 0.9 policy. Publishing the GitHub release triggers the full release matrix followed by npm trusted publication.

Detection: exact-version CI, release receipts and registry/consumer checks. Rollback: close this PR before publication; after npm publication, ship a corrective version rather than replacing immutable package bytes.