Hard sleeps remain
Polling-based synchronization debt still spans 40 files.
Selenium BiDi Readiness Lab · Five real assessment landmarks
See A Selenium 3 Suite Become Ready For Governed Modernization
This is not a completed BiDi migration story. It is the evidence-backed path that shows what must become true before a team can adopt BiDi without carrying old synchronization risk into a new protocol.
Baseline30/BLOCK
Current state73/WARN
Next blockerSynchronization debt
Honesty boundary
Readiness is measured before migration is claimed.
The repair loop uses static framework evidence and real reassessments. No completed BiDi migration or runtime test execution is claimed because the dotnet runtime was unavailable in this environment.
01 · Definitive baseline
Selenium 3 blocks the protocol path.
The first assessment found 13 Selenium 3 package references, no executable BiDi readiness contract, and 137 hard sleeps across 42 files.
Assessment decision30/BLOCK
02 · Readiness contract
The target becomes explicit before the runtime changes.
A BiDi readiness contract was added. Trust improved, but Selenium 3 still prevented a supported BiDi session contract.
Assessment decision42/BLOCK
03 · Selenium 4 runtime
The hard runtime blocker is removed.
The Selenium 4 correction landmark removed the protocol-runtime blocker. Synchronization and browser-driver governance became the next visible risks.
Assessment decision72/WARN
04 · Wait contract
A governed wait contract starts replacing sleeps.
Hard sleeps fell from 137 to 129. The score moved by one point because the remaining debt was still systemic.
Assessment decision73/WARN
05 · Expanded wait repair
The plateau identifies the next real blocker.
Hard sleeps fell again to 121 across 40 files, but the score held at 73. The system did not manufacture progress; it promoted synchronization debt as the next governed target.
Assessment decision73/WARN
Evidence package
Inspect the chain, not just the conclusion.
Every public claim on this page points back to a detector audit, advisory report, engineer plan, or run manifest from the real repair loop.
01
Journey manifest
The score movement, stage order, and honesty boundary.
Open artifact →02Baseline detector audit
Raw observations behind the 30/BLOCK baseline.
Open artifact →03Baseline engineer plan
The internal correction path generated from the baseline.
Open artifact →04Current detector audit
Raw observations behind the current 73/WARN state.
Open artifact →05Current engineer plan
The remaining governed correction path.
Open artifact →06Current run manifest
The chain-of-custody record for the latest landmark.
Open artifact →Govern before migration