v0.8.6

What's Changed

• Status-line update marker, robust self-update, and shared connection pools by @fuseraft in #14
  • Once a new release has downloaded, the status line shows ↑ <version> on restart for the rest of the session, so the one-time notice isn't the only sign that an update is waiting.
  • A downloaded release must start and report its version before it's kept, and again before it replaces the running one, so a release that can't run on this machine, or a download damaged on disk, never takes over a start. A damaged download used to crash the next start.
  • Several anchor starts at the same moment no longer lose an update: one start's cleanup could delete the folder another had just claimed the update into, which crashed that start.
  • Each session downloads into its own folder, so two sessions downloading at once never write the same file.
  • On Windows, an update works while a session from the previous update is still running, and an install reached through a symbolic link has its file replaced instead of the link.
  • Every HTTP client shares one connection pool for the process. MCP servers over HTTP made a new pool on every connect and reconnect, and setup, /setup and the update check each had their own.
• test: the session-log retry test no longer races a timer, so it doesn't fail at random on Windows CI, and headless tests wait up to 10 seconds for events

Full Changelog: v0.8.5...v0.8.6