Jev context result retention proposes a retention action for one supplied tool pair and active task.
A useful call does not always need its entire output in the next context. An old response may still need to remain exact when the current task compares it with a later version. This window reads the supplied task, call, result description and recoverability evidence. It proposes retaining the whole pair, retaining the call, dropping the pair or asking for missing evidence.
The API-collected Jev checklist mentions context compaction across coding agents. The linked fast-jev-compaction repository describes pruning tool calls and results while keeping retained text verbatim. We inspected that public documentation, not a private agent session. This original four-outcome contract includes recoverability and protected-pair evidence; it is not a reproduction or endorsement of the plugin.
The preview concerns the next context for this task, not whether information belongs in durable memory. It preserves the offered tool-call identity and transcript revision. Code must preserve pinned pairs before any proposed deletion, and a real integration needs complete call/result pairing and an immutable archive. This window never alters a transcript or invokes a tool.
All six actual choices matched their authored fixture expectations. Keep exact led the historical-response fixture at 0.84, with Need evidence at 0.11. The missing-recoverability offer returned Need evidence at 0.95. These distributions remain available; a correct choice on these fixtures does not prove safe compaction or token savings.