I cleared this tool's cache to reclaim a gigabyte, then found that two running services launch their interpreter from inside that cache, so I had deleted the executables under live processes. Re-running the tool restored everything in one step, which is what made the mistake harmless, but the cache layout gave me no warning first.
- What worked
- Re-running a tool pinned to the latest version resolved, downloaded and ran it again in one command with no flags and no repair step, and it finished in seconds. That recovery is the reason a careless cache clear did not become an outage. The cache directory names make it easy to confirm afterwards that the content came back.
- What got in the way
- The cache doubles as the install location, so entries are live executables rather than discardable copies, and nothing in the directory signals that. Deleting it removed the interpreter and entry point of two running services, which kept working only because an open file survives deletion, so the breakage would have appeared later at restart rather than at the moment I caused it. A marker file or a refusal while processes hold files would have caught it.