Repository navigation
Release KeyTrail beta.2 with guarded manual-tab observations - #22
Merged
Merged
Conversation
added 6 commits
November 1, 2026 10:01
PerchAnton
marked this pull request as draft
November 4, 2026 19:31
PerchAnton
changed the title
PerchAnton
changed the base branch from
keytrail/strict-browser-report
to
main
November 4, 2026 23:16
PerchAnton
changed the title
PerchAnton
marked this pull request as ready for review
November 4, 2026 23:38
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Manual-tab observations previously took four Playwright requests per repeated sample. On macOS 15 ARM, the older reader blocked valid short and manual activation fixtures after 130.2, 107.3 and 117.1 ms gaps. The grouped reader resolves every original target and role in one request when the observed mapping is safe. Ambiguity, changed membership and mutations trigger fresh resolution. Genuine gaps above 100 ms still block activation.
This PR includes #21's strict validator and actual-report CI gate, #19's historical correction, the beta.1 release ancestry, and the beta.2 ten-round policy. Use a merge commit to preserve that ancestry.
Final source
fd8f58a. Ten sequential full rounds passed 180 tests each. The four-worker comparison passed the same 180 tests. All eleven original reports were reread with matching semantic signatures, 1,771 distinct journey IDs and zero retries, skips or unexpected failures. All 52 guard cases and 108 benchmark tests passed. Each workload met both overhead criteria. Final validation.Verified archive
f5740ed. All six readiness checks passed. The release package gate verified archive contents, ESM/CJS, types, offline installs and browser checks in clean vanilla and React consumers. The React negative control exited 1 as expected and retained its HTML, JUnit and journey reports. The archive contains 479,777 bytes and its SHA-256 isfcfd700d0bc2534d76f07382a9cf3bdc43457224d2c6d72e479fcdb0232df586. CI for the release commit.