You'll notice
Useful2 Signal1
Purging history now fails loudly if the history file can't be safely rewritten.
What's wrong with this entry?
Anonymous. No account, no email.
What
Counting and rewriting history.jsonl now raise an error saying the file was not rewritten when the history file is a symlink or not a regular file, or when the read or rewrite is declined, instead of failing quietly.
Details
- The code prefers an optional storage backend for the paged scan and rewrite; that backend is never constructed in this build, so the existing line-by-line path is what actually runs.
- Failure telemetry is now reported per failure code, with
multiple_failureswhen more than one code occurs, rather than a blanketconfig_write_failed.
Evidence
purge history rewrite refused
Strings lifted out of the shipped bundle, so the claim above can be checked against them.