The code index now tells you how each index was built and when a full re-read last confirmed it. A daily check compares the index with a fresh read of the same commit, and repairs the index when the two differ.
What's new in v1.18.0
See how fresh an index is. The
freshnessblock on/context,/summaryand/treenow carriesindex_mode,files_reparsedandfiles_reresolved, plus fourlast_full_verify_*fields that say when a full check last read the same commit and what it found.A daily check you can read. Once every 24 hours we re-read the whole commit the ready index describes and compare the two. The check runs as an ordinary job in
GET /jobswithsourceset topoll, and queries keep answering from the index throughout.A drift repairs itself. When the check and the index disagree, the job ends as
incremental_drift, posts one "Repo index failed" notification for that commit and queues a full rebuild. A check that proves nothing ends asverify_inconclusiveand posts nothing.Incremental builds, per workspace. Where they are switched on, a merge re-parses only the files it changed and re-resolves the files that depend on them. Where they are off, every job still reads the whole repository and
index_modesaysfull.
Between 20 and 22 November the check matched five times and caught one drift; the rebuild finished three minutes later and the next check matched.
Read every field and outcome in the docs at https://opvs.ai/docs/guides/code-index.