Repository navigation
v0.2.6 research preview
Pre-releasev0.2.6
This research preview delivers the nine output-interaction corrections in the acceptance review: full-width password wrapping, a visible 1.2-second scramble, adjacent Generate/Show/Hide/Copy actions, length-matched masking, exact native selected-text Copy, bold countdown seconds, contextual low-bit guidance, aligned translated metrics and concrete Vietnamese instructions. Cryptographic sampling, vocabulary, shared chrome and original font/brand assets are unchanged.
Both v0.2.4 and v0.2.5 were held by failed CI and published no release. The latter established that changing the awaited driver lifecycle event from load to DOMContentLoaded was insufficient. Script-enabled HTTP app navigation now uses one browser location.assign action, then requires the requested URL in a fresh document, readyState complete, a successful main-document HTTP response, ready fonts and decoded images. The preceding document receives a marker that must disappear, so an old already-loaded document cannot satisfy readiness. This avoids reliance on the unresolved page.goto completion path without catching a timeout, accepting a failed page, retrying navigation or weakening interaction assertions. Offline file, JavaScript-disabled and foreign-ancestor fixtures retain their original direct navigation for their distinct capability boundaries. The precise intermittent driver cause remains undetermined.
A new adversarial browser case verifies rejection of a 404 document and an undecodable image, followed by a successful real app navigation. The full matrix now has 135 cases across Chromium, Firefox and WebKit with zero retries. Failed executions retain JSON results and diagnostic traces through CI. Every tagged release still requires successful Ubuntu/Windows builds, byte-identical deterministic artifacts and exact-tag build provenance. Deployment and affected live checks are recorded separately after their execution; historical tags and failures are retained.