Inspect Sparse State
VCS-INSPECT-SPARSE-STATE
Summary
Check sparse checkout state before treating a missing path as absent from history. Sparse patterns can hide files, so inspection prevents recreating or editing the wrong path.
Rule
Inspect sparse state before treating a missing path as missing history.
Why
In sparse checkouts, a missing file may be outside the sparse patterns rather than deleted from history. Treating it as absent can lead agents to recreate files, misread ownership, or make edits in the wrong location.
Helps
- Prevents false conclusions about repository contents in sparse workspaces.
Limits
If the repo is not sparse, normal path and history inspection is enough. Check sparse state when paths expected from docs, tests, or history are missing.
Agent Instruction
Inspect sparse state before treating a missing path as missing history; sparse patterns can hide
files that still exist.Mechanisms
Supported by jj sparse list, workspace inspection, path search, adjusting sparse patterns
deliberately, and handoffs that note sparse limitations.