Fix race condition in Time.test.ts timing assertions

[Copilot]

The Time.test.ts test was failing intermittently in CI (webkit browser) due to a timing race condition in the assertion logic.

Root Cause

The test captured Date.now() after creating the time object, then called time.now() twice and asserted both values were within [now - 10, now + 10]. If enough execution time elapsed between the reference capture and the second call, the assertion would fail.

// Before (flaky)
const time = createTime();
const now = Date.now();
expect(time.now()).toBeGreaterThanOrEqual(now - 10);
expect(time.now()).toBeLessThanOrEqual(now + 10);  // Can fail if time progresses

// After (stable)
const before = Date.now();
const time = createTime();
const after = Date.now();
const timeNow = time.now();
expect(timeNow).toBeGreaterThanOrEqual(before - 10);
expect(timeNow).toBeLessThanOrEqual(after + 10);  // Proper time window

Changes

• Capture timestamps before and after createTime() to establish proper time window
• Call time.now() once and store result to avoid multiple calls affecting timing
• Adjust assertions to verify time falls within the established window

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}