A one-millisecond timer could become runnable immediately after registration.
Remove the early dispatch allowance from the shared scheduler so registered
and rescheduled timers become runnable only at or after their actual
monotonic deadline. All readiness queries use the same rule.
Regression coverage checks registration-time and pre-deadline queries,
exact-deadline dispatch through filtered and unfiltered paths, and interval
rescheduling without advancing the new deadline.
Capture each IdleDeadline's native performance time origin and subtract
coarsened timestamps in ticks. This keeps timeRemaining on the same 100us
timeline as performance.now, including when the method is borrowed from
another realm, and avoids exposing floating-point sub-tick residuals.
The recursive idle WPT regression is reproducible at 8a353fa2a: its release
parent passes 20/20 while that commit fails 20/20. That commit changed the
DOM clock from 5us to 100us without updating the raw idle deadline clock.
Add deterministic clock-bucket and expiration checks plus a native API
resolution test that fails before this fix. Clock-only release stress passes
97/100; the remaining failures expose early idle timer admission, which is
handled separately.
Validation: cargo fmt --all; cargo clippy --workspace --all-targets
--all-features -- -D warnings; cargo nextest run --no-fail-fast
(19139 passed, 16 skipped).
Remove the Date/Intl wrappers, custom date parser and per-Page replay state. Keep exclusive locale/timezone ownership in a process controller and refresh existing Page and Worker isolates through generation-bound notifications and observation boundaries, including nested Inspector pauses.
Release claims on session/target/context retirement, retain native coercion and locale matching, and cover lifecycle restoration with Rust, BiDi and process-isolated CDP regressions.
ldm0