Claude 7b4ebbf7f5 test(timer): expose pause-over-midnight duration bug ...

Pause is tracked as pausedAt (TimeOfDay, ms since local midnight) and
paused duration is derived via the naive `clock - pausedAt`. When a pause
spans midnight the clock has wrapped to a small value while pausedAt is
still large, so the subtraction goes negative and every paused-duration
result is corrupted (runtimeState.start resume accumulation, and
getExpectedFinish/getCurrent/getRuntimeOffset in timerUtils).

Add two currently-failing tests that reproduce this:
- runtimeState: full start/pause/resume cycle where the pause crosses
  midnight, asserting pausedDuration and elapsed exclude the pause.
- timerUtils.getRuntimeOffset: over-midnight variant of the paused-offset
  case (the site carrying the "brakes when crossing midnight" TODO).

Both fail today (report ~ -86,100,000 instead of the real 5-minute pause)
and will pass once the pause math adopts the wrap-aware primitives
(timeCore.elapsedTime / epoch-based tracking).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0136N3FnyuUmLJbMNJiZd6YX

2026-07-14 10:41:50 +00:00

..

cli

bump ontime to version 4.10.0

2026-07-01 13:20:04 +02:00

client

ux(finder): add navigation shortcuts

2026-07-14 12:04:44 +02:00

electron

bump ontime to version 4.10.0

2026-07-01 13:20:04 +02:00

resolver

resolver: drop dead ignoreDeprecations from tsconfig.dts.json

2026-07-13 14:27:31 +02:00

server

test(timer): expose pause-over-midnight duration bug

2026-07-14 10:41:50 +00:00

spec

Deps migration (#1988)

2026-03-08 16:22:12 +01:00