fix: saturate timer tick payload

[nvphungdev]

Summary

• Saturate timer tick values at i64::MAX before storing them in Value::Integer.
• Reuse the same tick payload builder for immediate, refresh, and interval emissions.
• Add a regression test for u64::MAX tick values.

Fixes #39

Validation

• cargo fmt --manifest-path crates/nemo-data/Cargo.toml -- --check
• git diff --check

Blocked:

• cargo test -p nemo-data timer stalled while updating the workspace GPUI git dependency (https://github.com/zed-industries/zed); stopped after retrying to avoid leaving a hanging cargo process.

[geoffjay]

Code Review

Summary

Clean fix for timer tick overflow (#39). Saturates u64 tick values at i64::MAX instead of the silent wraparound from as i64, and deduplicates payload-building by extracting create_tick_payload_for.

Issues (blocking)

None.

Suggestions (non-blocking)

None — this is well-scoped and correct.

Approved

LGTM. The saturation behavior is correct, the deduplication eliminates a real maintenance hazard, and the test covers the overflow case.

[codecov]

Codecov Report

❌ Patch coverage is 87.50000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 52.45%. Comparing base (46d8ab7) to head (01e0870).

Files with missing lines	Patch %	Lines
crates/nemo-data/src/sources/timer.rs	87.50%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #68      +/-   ##
==========================================
+ Coverage   52.35%   52.45%   +0.09%     
==========================================
  Files          71       71              
  Lines        6101     6097       -4     
==========================================
+ Hits         3194     3198       +4     
+ Misses       2907     2899       -8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.