Under the hood
Useful2 Signal3
Failed cleanup of a checked-out source now names the case, including a case-only path collision.
What's wrong with this entry?
Anonymous. No account, no email.
What
Two failure modes for tidying up a checked-out context source now have descriptions and telemetry keys: removal failed and the partial checkout may still be visible to the session, or the path collided with an already-prepared copy differing only in letter case and was left alone.
Evidence
kept_prepared_twin
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.229
Session context is built lazily and cached per project root
Both mention context
-
v2.1.232
/context returns a structured breakdown of token usage
Both mention context
-
v2.1.232
/context returns machine-readable usage alongside the table
Both mention context