Implement incremental and forced project index updates #9
Labels
No labels
area/cli
area/core
area/database
area/indexing
area/query
type/epic
type/feature
type/foundation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
JayKobe6k/ClariTree#9
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Update an existing index efficiently while preserving atomic queryable revisions.
Command contract
Resolve the existing index from the cached catalog using the canonical project path. If no catalog entry exists, require
--index-pathto identify the existing index database.--reindexforces all translation units to be rebuilt.Incremental behavior
Acceptance criteria
--reindex.--reindexshares the same publication path as incremental updates and does not mutate the active graph in place.Dependencies
Depends on #8 and the provenance/fingerprint behavior from #4, #6, and #7.
JayKobe6k referenced this issue2026-09-11 12:55:49 +00:00