sure, it's the price you pay, but you have to considered that context poisoning is basically a statistical certainty approaching 1 regardless of model size. As you grow the context, the likelihood of vague details getting conflated increases, so if you're _not_ cutting down the context you're increasing the probabilities of just basic random jitter in your logic and code.

The pruning does evict cache but not from the start, and only up till the last time you pruned it, as it's just adding messages on top.

but yes, it takes some additional tests and docs to keep it from just becoming hollowed out on tasks; I'd say about 10-20% of the time is just horribly loses what it's doing.