feat: keep what was loaded between runs, and start where you left off

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

docs/config.md

@@ -16,6 +16,7 @@ sourcesView: grouped   # or flat; ` toggles it
 collapseGroups: true   # start with the Sources pane's groups folded; enter or space unfolds one
 updateCheck: true      # look for a newer release once a day (U and lazysecrets update work either way)
 history: true          # count uses of items for Recent (R)
+cache: true            # keep what was loaded (never values) for the next start
 providers:
   azure:                                 # applies to every az account
     enabled: true                        # default
@@ -102,6 +103,25 @@ count as using it: its record keeps when it was last used and how often,
 for Recent (`R`). Records kept only for usage are dropped after 90 days
 unused, and beyond the 100 most recent. `history: false` stops counting.
 
+It also keeps where you left lazysecrets in each folder (the selected
+source, vault or secret), and goes back there the next time it starts in
+that folder, unless it was started on a link.
+
+## Cache
+
+What lazysecrets has loaded is kept in
+`~/.cache/lazysecrets/cache.json` (`$XDG_CACHE_HOME`), readable only by
+you: the Sources lists, vaults and scopes, and secrets' names and metadata
+(tags, dates, references), never values. On the next start they show at
+once, and anything older than two minutes reloads in the background when
+you go to it, or when Go to searches it. Revealing and copying always
+fetch the value live.
+
+Lists not loaded for 30 days are dropped, and so is everything from an
+account you're no longer signed in to. Repos aren't cached: their files
+are read from disk anyway. Deleting the file is always safe, and
+`cache: false` stops using it.
+
 ## Updates
 
 Once a day (`updateCheck`), in the background, lazysecrets asks the