Repository navigation
Pacer 0.7.7
Two fixes to pacer, so paused work stops before a limit and doesn't stampede back afterwards.
A go-ahead now expires before the limit
Subagents check pacer status between steps. That check accepted a "go" for up to 15 minutes, so near a limit, work in flight kept running until the account was full. A "go" now lasts only as long as the current burn rate leaves room: status shows go (until 22:41Z), and once that time passes the next check asks Pacer again. With plenty of room nothing changes. Near a limit, sessions get a fresh answer every minute or two and stop in time.
Resuming waits for real room
After a pause, pacer wait resumed as soon as you switched to another login, even one with only a few points left. Every waiting session then started at once and filled it within minutes. wait now resumes on a login switch only when the new login has room for 20 minutes at the rate your sessions were using (--resume-headroom to change it). A reset still resumes as before.
Your data is untouched. No reset, no re-import.