research-git currently has no dedicated store health diagnostic command. When .rgit/graph.db or .rgit/objects/ becomes inconsistent, the failure only appears later through unrelated commands.
Examples observed:
rgit doctor is not registered today.- Missing proposal diff objects can surface as
FileNotFoundError from rgit pending --json.
- Malformed proposal candidate JSON can surface as
JSONDecodeError.
- Missing feature payload objects can crash
rgit features.
- Missing run artifacts are only reported from
rgit provenance.
- Dangling edges can be inserted with
rgit edges --add.
- One-sided symmetric edges can make graph output misleading.
This makes support and bug reporting harder, because users cannot run a single command to inspect whether the durable .rgit memory store is healthy.
I have already submitted a companion PR to add a read-only rgit doctor command that checks schema metadata, object references, proposal JSON, dangling edges, and symmetric edge invariants: #12. Please help review the fix.
research-gitcurrently has no dedicated store health diagnostic command. When.rgit/graph.dbor.rgit/objects/becomes inconsistent, the failure only appears later through unrelated commands.Examples observed:
rgit doctoris not registered today.FileNotFoundErrorfromrgit pending --json.JSONDecodeError.rgit features.rgit provenance.rgit edges --add.This makes support and bug reporting harder, because users cannot run a single command to inspect whether the durable
.rgitmemory store is healthy.I have already submitted a companion PR to add a read-only
rgit doctorcommand that checks schema metadata, object references, proposal JSON, dangling edges, and symmetric edge invariants: #12. Please help review the fix.