+ ]gj.Rt^RIHtRRltRRltR#)uShared pace math for usage-window tracking. `server.py::_compute_pace` and `simulate_display.py::draw_gauge` both need to turn "how far into the window are we, and how much has been used" into a pace ratio, but they apply *different* guard/clamp policy on top of that ratio: - `server.py` returns the raw, unclamped ratio (or `None` on a few edge conditions) because it feeds the `/status` API's `"pace"` field, a real consumer surface. - `simulate_display.py` clamps the ratio to `[0.0, 2.0]` for the gauge's visual arc and has its own branch behavior at the edges. Only the genuinely-shared arithmetic lives here. Each caller keeps its own guards, clamps, and edge-case handling exactly as before — this module does not decide policy. ) annotationsc$V^8dQhRRRRRR/#) resets_in_secint duration_secreturnfloat)formats";/Users/jameslopez/projects/CodexBar-ESP32/companion/pace.py __annotate__r s!99C9s9u9c W, V, #)uFraction of the window elapsed so far: (duration - remaining) / duration. Caller is responsible for guarding `duration_sec` (e.g. against zero or negative values) and for clamping/interpreting the result — this is pure arithmetic, no policy. r )rrs&&r elapsed_fractionrs  (L 88rc$V^8dQhRRRRRR/#)rpctr elapsed_fracrr )r s"r r r s! ( (E ( (5 (rc WR,, #)a|Usage pace ratio: pct used vs. pct expected at this point in the window. `elapsed_frac * 100.0` is the expected usage percent if usage were perfectly linear; `pct / expected_pct` is 1.0 exactly on pace, >1.0 ahead of pace (overpace), <1.0 behind pace (underpace). Caller is responsible for guarding `elapsed_frac` (e.g. against zero/negative) and for any clamping of the result. gY@r )rrs&&r pace_ratiors & ''rN)__doc__ __future__rrrr rr rs"#9 (r