Compacting a long session now rewrites transcripts through the storage layer atomically instead of editing the file in place.
What's wrong with this entry?
Compacting a long session transcript now goes through the storage backend, replacing records under a precondition and publishing atomically, instead of editing the transcript file in place. Failures are reported with named reasons.
- Bail reasons include
snapshot_mid_linefor a partially written tail,shared_inodefor a hardlinked target, andsource_changedwhen another writer wins the race; these arrive ontengu_transcript_compact_failed. - Reads page forward rather than loading the whole transcript.
- When a compaction reclaims little space, the threshold that triggers the next one doubles. Successful runs report byte counts before and after.
- Applies only on the newer storage path; no user-facing setting.
tengu_transcript_compact_failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.