@kitelev/exocortex-cli 16.240.17 → 16.240.18

package/README.md

@@ -217,6 +217,19 @@ npx @kitelev/exocortex-cli query "CONSTRUCT { ?s ?p ?o } WHERE { ?s ?p ?o }" \
 
 Build or refresh the persistent triple cache used by `--use-cache` consumers. The cache lives at `<vault>/.exocortex/cache/triples.json`.
 
+**Validity and refresh (#4263).** The cache is keyed per file: it stores the mtime, the
+size and the triples of every indexed `.md`. A `--use-cache` command compares that manifest
+with a stat-walk of the vault, so an add / edit / delete anywhere under `assetspaces/**` is
+detected (the vault root directory's mtime is no longer consulted). A small change is
+refreshed incrementally — only the changed files and the files that refer to an added,
+removed or alias-changed target are re-parsed, and the inferred layer `index` materialized
+is recomputed when a touched file feeds an inference engine (class / superclass / type /
+prototype), otherwise kept — while a legacy or corrupt cache, a change to a TBox-form asset
+(`prefix__Name` label or alias), a FileSpace declaration change or a diff above half the
+vault falls back to a full rebuild. The cache file is written atomically, so concurrent
+commands never read a torn file. `index --force` always rebuilds; `query` reports
+"♻️ Cache refreshed incrementally" on a delta and "🚀 Cache hit!" on a hit.
+
 ```bash
 npx @kitelev/exocortex-cli index --vault ~/vault --stats
 ```