feat(cache): Add persistent documentation cache - #14
Merged
Conversation
Use a dedicated disk-backed URL cache for Apple documentation responses and expose a cache clean command for deterministic cleanup.
philprime
marked this pull request as ready for review
September 10, 2026 12:04
philprime
enabled auto-merge (squash)
September 10, 2026 12:04
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Apple documentation responses now use a dedicated 1 GB disk-backed URL cache instead of the small shared default. This lets repeated searches reuse downloaded DocC pages across CLI invocations while preserving standard HTTP cache revalidation.
Adds
apple-docs cache cleanfor deterministic cleanup with human-readable reclaimed size reporting. Cache directory lookup safely handles unavailable user cache locations without forced unwrapping or unbounded array access.Validated with the full test suite, static analysis, a release build, and an isolated release smoke test that populated and cleared cached response payloads.