0.1.0

First non-prerelease with an explicit 0.1.x compatibility and support policy. Documented exports, contract defaults, result schema 1 and ruleset 0.4.0 remain compatible with beta.2; only package-version metadata changes. No contract migration is required.

Frozen inputs 85cee8c completed ten full rounds of 180 tests plus a separate 180-test four-worker comparison: 1,980 successful executions, zero retries/skips, matching semantics and 1,771 distinct journey IDs. The 100 ms observation limit is unchanged. All 52 guard controls and 108 benchmark checks passed. Both overhead calculations meet the 20% bound for the three synthetic fixtures; these measurements do not establish a general speed advantage.

The exact attached archive passed the release gate on documentation/evidence head a086847: ESM/CJS and TypeScript imports, fresh vanilla and React consumers, guarded journeys and deliberate failure with HTML/JUnit reports. Linux and three macOS ARM CI jobs passed on this final PR commit. The release tag selects that tested commit, which is now an ancestor of main; the merged source tree is identical. Historical alpha/beta evidence is preserved separately.

Published on npm as keytrail@0.1.0 under latest on 8 November 2026. Install with npm install --save-dev --save-exact keytrail@0.1.0 @playwright/test@1.64.1 on Node 24. The beta tag remains 0.1.0-beta.2.

The canonical npm tarball matches the attached qualified archive byte for byte; SHA-256 and SHA-512 integrity were verified. Fresh registry installations passed ESM/CJS and TypeScript checks, six vanilla examples and three guarded journeys, plus React portal examples and its guard. The deliberately broken React fixture exited 1 with D03 FOCUS_MISMATCH and retained HTML/JUnit reports and the failed journey attachment. Both the exact tag and merge commit passed all four CI jobs. The completed final series was revalidated from its raw reports and was not rerun.

npm-verification.json records publication and consumer checks. The original package-verification receipt remains the pre-publication qualification record; its published: false field is historical. The tag, original assets and downstream dependencies are unchanged.

SHA-256: 49eb5efacb84ac4c41560164a081e9f9368d93a24e171eecc03765cf5f72491c.

Compatibility and support · Migration and qualification · Changes in #23.