Release 0.9.10

[noeltock]

Problem

The intent preservation fixes and corrected skill guidance are merged but absent from npm latest (0.9.9). This prepares their 0.9.10 maintenance release.

Solution

Bump package and lockfile versions to 0.9.10 and date the changelog. Runtime changes are already merged through #133 and #135–#139.

Change	Read first	Proof
Publish the merged fixes as 0.9.10	CHANGELOG.md	Exact-candidate release matrix and release CI

Diff

+4 / −4 across three files.

- package.json and package-lock.json: 0.9.9
+ package.json and package-lock.json: 0.9.10
- CHANGELOG.md: Unreleased
+ CHANGELOG.md: 0.9.10 — 2026-10-04

Testing & verification

Reviewed revision: 709e68fb87d9f782e9a00e691d7fdc05167eb129. Local environment: Node 22.23.1, npm 10.9.8, macOS arm64, OrbStack.

git diff --check passed. Fresh native Heading and Paragraph controls passed on WordPress 7.1. npm run release:check -- --matrix full-release-matrix --manual-review proof/reviews/0.9.0/owner-acceptance.json passed on the clean candidate: 751 tests with four existing skips, consumer tests, packed installation, canonical skill/installer checks, generated-plugin activation and full WordPress proof. The receipt reports releaseOk: true, with no release blockers and the existing native Heading/Paragraph editor accessibility exceptions. Saved hash-bound owner acceptance was reused; no new manual review is claimed.

Exact-head CI 37181261033 passed Node 20.19/22.13/24, package boundary, WordPress proof and the final scope gate.

Two local startup attempts hit network timeouts before testing; both are retained. The controls and release matrix passed with IPv4-first DNS and a 2000ms Node connection-attempt timeout, without changing candidate code or proof configuration.

Release workflow 37182323401 passed on merge d800020867a49d7d40739e631e33ae9bd9da92c7; npm accepted 0.9.10 with signed provenance and reported registry processing. Main CI also passed. Not verified: registry propagation, independent provenance and a fresh registry consumer; these checks were skipped at the owner’s request. The optional model benchmark remains unscored; existing 0.9 native editor accessibility exceptions remain scoped.

Risk / rollout

Unknown block types and malformed consumed intent now fail instead of returning partial content. Dropped attributes remain warnings. The changelog records this compatibility change. The publishing workflow repeats the full release matrix before npm publication. On failure, stop before publishing; a released package would require a corrective version rather than replacing its bytes.