Mock replay pins a capped number of recordings and warns you to prune unused ones.
What's wrong with this entry?
The internal eval mock-replay loader now pins only up to a fixed number of recorded interactions per file and warns to prune recordings no case still reaches once that cap is passed. The cap is an internal constant whose value is not visible in the build.
only the first ${oo} are pinned for replay — prune ones no case reaches any more
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
plugin evalno longer swallows piped inputBoth mention eval
-
v2.1.234
Plugin eval reference documents image grading and new exit codes
Both mention eval
-
v2.1.234
claude plugin evalhandles termination signals and cleans up its outputBoth mention eval