Pacer 0.4.13

More CPU. This one is the big one.

Pacer was recomputing its whole forecast every 20 seconds

0.4.12 fixed the Dashboard window pegging a core. This fixes the rest,
which showed up as Pacer being busy in bursts even with no Claude Code
session running.

The forecasting engine — the thing behind projected fill, time-to-limit
and the pace bands — was refitting from scratch every time Pacer recorded
new usage, at most every 20 seconds. Each refit takes about 4.5 seconds of
real work. That is roughly a quarter of a CPU core, permanently, to
recompute answers that change over hours.

It now refits when the data it actually depends on changes — your
rate-limit windows — rather than every time a token is recorded.

Measured on a real machine with Claude Code actively running:

	CPU
before	~100% of a core
after 0.4.12	~16%
after this release	~7%

Forecasts are unchanged. They were already being recomputed far more often
than their answers could move.

---

Requires macOS 15 or later. Update via Pacer's built-in updater, or download
below.