v0.58.0

Added

• Fleet sync shares each limit's history: a machine that was off or signed out
  for days takes in what the others saw meanwhile, so its pace, its projection
  and remuda's drain chart are measured from the whole week rather than across
  the gap. Finished weeks are shared too. Each machine shares only what it saw
  itself, and the fleet's view lands in tokengauge-window-fleet.json beside
  its own history, so a new fleet key forgets the old fleet's.

Fixed

• A limit's projection after a quiet start follows how fast it is filling
  now: a week left at 0% for days and then spent in an afternoon was measured
  as if that afternoon's use had been spread over the whole week.
• After a banked Claude reset, which refills the week without moving its
  reset, the pace is measured from the refill: a fresh 0% three days before
  the reset reads as on track rather than far behind, and its projection
  follows the use since the refill.

What's Changed

• [fix/burn-stretch-and-wild-resets] The burn measures its own stretch, and a refill in place opens the window by @Arzaroth in #88
• [feature/fleet-window-trails] Fleet sync shares each limit's history by @Arzaroth in #89

Full Changelog: v0.57.0...v0.58.0