Comment filenames were stamped to the second, so two comments added in
the same second produced the same name and fs::write truncated the first.
Agents post in bursts, so this was routine data loss: five comments added
back to back left one file.
Stamp microseconds instead, and create the file with create_new rather
than fs::write, so a name that already exists is taken as a collision and
the next zero-padded suffix is used instead of overwriting. The suffix
sorts after the bare stem, so read_comments still orders comments the way
they were written.
The collision branch cannot be reached from the CLI, since two processes
will not share a microsecond, so it has a unit test of its own.
Patch bump: existing second-resolution comment files still read and still
sort ahead of new ones written in the same second, so no migration.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>