hash▌

Cache expensive file processing results using SHA-256 content hashes instead of file paths. \n \n Content-hash keys survive file moves and auto-invalidate when content changes, eliminating path-based cache brittleness \n Store cache entries as individual {hash}.json files for O(1) lookup without requiring a separate index \n Implement caching as a service layer wrapper around pure processing functions, keeping extraction logic separate from cache concerns \n Handle cache corruption gracefully by