Release 0.9.7 with Wesper 0.4.1 compatibility

[noeltock]

Problem

Block Runner pins Wesper 0.0.3. Wesper 0.4.1 adds optional ownership and taxonomy evidence and more explicit partial warnings while retaining manifest version 1. Verify these additions remain safe for BR consumers and prepare 0.9.7, including the CI improvements already merged in #106.

Closes #107.

Solution

Pin Wesper exactly to 0.4.1, retain its additive manifest fields through collection, and cover conversion with a real missing-attribute warning. The production BR adapters require no code changes. Version and changelog advance to 0.9.7.

Behavior that changes or must stay true	Read first	Proof
Installed Wesper version is exactly 0.4.1	package.json, package-lock.json	Registry install and manifest/lock consistency checks
Optional ownership and taxonomy associations survive BR collection	dev/test/context.test.ts	Typed fixture forwarded unchanged; real WP-CLI collection succeeded
Partial context evidence permits supported generation	dev/test/styles.test.ts	Actual missing-attribute warning shape; refreshed-manifest generation and validation passed
Release contains Wesper update and merged CI changes	CHANGELOG.md	Version 0.9.7; candidate CI, release matrix and registry checks passed

Diff

+119 −12 · 5 files · no BR runtime-source change

 package
-  block-runner 0.9.6 / wesper 0.0.3
+  block-runner 0.9.7 / wesper 0.4.1
 consumer checks
+  optional owner: unknown and taxonomy associations pass through unchanged
+  partial missing-attribute evidence still permits supported conversion
 unchanged contracts
   contextVersion: 1
   absent registry remains non-authoritative
   legacy source is not ownership

The older prepared Wesper adapter branch changes REST/WP-CLI collection architecture and is not included.

Testing & verification

Reviewed revision: 5b85ff8 · Environment: local macOS, published Wesper 0.4.1, read-only WP-CLI collection from a running WordPress site.

• npm test -- --run dev/test/context.test.ts dev/test/styles.test.ts: 88 passed.
• npx --no-install vitest run dev/test/tokens.test.ts: 19 passed.
• npm run typecheck: passed.
• npm run build: passed.
• git diff --check: passed.
• block-runner context --wp-binary <local-wrapper> --wp-path /var/www/html --out <manifest>: passed with contextVersion 1, collectorVersion 0.2.3 and partial evidence. Optional ownership and taxonomy records were present; missing-context-attribute warnings were retained.
• block-runner convert <authored-html> --context <fresh-manifest> --json, followed by block-runner validate <generated-markup> --json: passed. Native group, heading, paragraph and button output used the site's base/accent tokens with no Custom HTML fallback.

Private site data and wrapper paths remain outside the repository. This is collection and generation/validation evidence, not a new browser-rendering claim.

Full candidate CI 34920171730 passed on this revision: Node 20/22/24, packed consumers, WordPress acceptance and the final scope gate. The local release:check --matrix package-packed receipt also passed for this clean commit.

0.9.7 is published as npm latest. The release workflow and post-merge CI passed at 42cbd756fdfe076c18af35bdb60b2bd926422ee6, whose tree matches the tested candidate.

Fresh registry verification:

• npm view block-runner@latest version dependencies.wesper gitHead: 0.9.7, 0.4.1, matching release commit.
• Engine-strict install of block-runner@0.9.7 into an empty consumer: passed.
• Installed CLI --version, representative context-driven conversion, validation and skill installation: passed.
• npm audit signatures: passed, 367 registry signatures and 79 attestations verified.

Not verified: the optional model benchmark and browser rendering against the private collection site were not run. Automated release WordPress acceptance passed; there are no outstanding publication checks.

Risk / rollout

The dependency moves across pre-1.0 releases. Targeted tests cover the consumed fields and warnings; full CI and the existing release matrix remain required before publication. No additional dependency, WordPress plugin installation or consumer migration is introduced.

• Exact registry pin and focused compatibility checks.
• Representative generation using a freshly collected partial manifest.
• Full candidate CI.
• Merge, tag 0.9.7 and complete trusted-publishing workflow.
• Verify fresh npm consumer and provenance.

Detection: context/token/style regressions and release receipts. Rollback before publication: revert this commit. After publication, any correction requires a new npm version; retain 0.9.6 as the prior version.

Authored by: Codex (GPT-6).