History leakage: a product explaining its own edit history

I got so annoyed by edit history leaking into everything from models desperately trying to prove themselves or oversharing what has been deleted, I had an agent come up with a name for it so I could create a skill to prevent it: /dehistorize. It's interesting because humans can do a similar thing when they anchor to a number or let a change/delta influence decision making instead of looking at it with a fresh perspective. In any case all those ScoringV2 and legacy_phase artifacts are now gone with a single word. And your UI can support the next decision instead of reporting the agents work.