nanobot fixes reconnect-safe mutation replay in its WebUI

HKUDS pushed two days of fixes to nanobot's WebUI on August 15 and 16, making mutation replay safe across reconnects, per the project's GitHub repository.

Anyone running a self-hosted agent UI with a persistent connection hits this eventually. A websocket drops, the client reconnects, and the mutations queued during the gap either replay out of order or get lost. nanobot's fix snapshots each mutation replay frame and preserves the original order on reconnect, with new test coverage added specifically for that path.

The same two-day window also shipped atomic renames for model presets, with inline conflict detection. It serialized gateway configuration updates too, so two writes can't race each other. None of this is in a tagged release yet. nanobot's last tag is v0.3.0 from July 25, and anyone pulling that tagged version still doesn't have these fixes. You'd need to track the main branch.

nanobot has 47,091 stars, which measures attention, not correctness. Reconnect-safe mutation replay isn't a feature, it's a bug class every long-running agent UI ships until someone hits it in production. Whether your own WebUI snapshots replay frames the same way is worth checking before it breaks in front of a user.