[TueJon]

The merged cancellation fix is still unreleased, and the discovery guide calls Chrome declarative features part of the CG draft even after upstream #338 removed that section. This prepares patch 0.7.1 with synchronized distribution versions, finalized changelog/release notes, and dated spec, Chrome and Site tools boundaries.

The release packages PR #23’s cooperative cancellation work without changing runtime code. Cancellation may leave unknown effects; native evidence remains the five synthetic Chrome Beta 156 probes recorded on 2026-10-05. No WPT or declarative conformance claim is added.

Validation: governor reran npm run check (79/79 pass); worker also verified Workbench browser simulation and whitespace checks. All distribution manifests and both lockfile version entries agree at 0.7.1. Existing external contributor attribution is retained; no new external contributor since v0.7.0.

Coordinated site PR follows. Merge, v0.7.1 tag/GitHub release at the exact merge SHA, and site deployment require the automation’s exact-head shipment decision. Release body: release/v0.7.1.md; previous tag: v0.7.0. No repository About or directory action is requested.

[TueJon]

No findings at e419c669a09e54e9a77bbc0fab46f0b84d17a413. Release/version consumers are consistent, and the dated source boundaries match upstream PR #338, Chrome documentation, and official Site tools guidance.
Exact-head CI passed; manifest versions and whitespace checks passed. Native browser evidence remains the recorded October 5 run; no new native acceptance was performed.