You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
Project MemoryArea: what it touches
ImprovementsKind: in v2.1.265,
ImprovementsSection of the release
What
When a tool result is too large and gets spilled into separate tool-results storage, and that save fails, the error message now says specifically which method triggered it: "project_read: spill to tool-results failed" or "project_memory_read: spill to tool-results failed", instead of one generic message.
Why
This makes it clearer, when something goes wrong saving a large result, exactly which operation caused it, which helps with diagnosing failures.
