DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.
Transcript compaction planner split out of the writer
Under the hood
Useful1Signal1
Elsewhere
The logic deciding which old transcript messages to drop was split into scan, plan and filter steps.
What's wrong with this entry?
Anonymous. No account, no email.
What
The code that decides which on-disk transcript messages to drop was extracted into separate scan, plan and filter functions, with the same abort telemetry as before when a preserved message id is missing or the preserved-segment walk breaks.
Evidence
preserved_walk_broken
Strings lifted out of the shipped bundle, so the claim above can be checked against them.