The TapeFile cache will keep growing as the tape expands. #105
Description
Summary
As the title suggests: in a long-running conversation session where entries are continuously written to the same tape, even though TapeContext only uses after_last to limit the context size, from the perspective of the TapeFile cache layer, it permanently caches the entire history in the tape. Furthermore, _read_entries are not evicted during handoff. Could this cause a memory leak for the agent during long-term operation?