Module doctor 

drep doctor - report what drep can actually do in this repository.

Adoption question, not a debugging one. Before trusting drep as a gate, a user wants to know the real coverage here: which languages are present, which of their own tools will actually run, and whether the LLM half is configured.

Diagnostic findings never fail doctor. A broken provider or missing tool still returns Ok(Exit::Clean); it is diagnosis, and drep check is the gate. Ordinary I/O failures can still be returned when the report itself cannot be written or the platform cannot resolve its user paths.

All output goes through a &mut dyn std::io::Write so the command is testable without spawning a subprocess. The tests call run_to directly against a captured buffer.

Structs

DoctorArgs

Functions

run

Run the command, writing to stdout. Diagnostic findings return Ok(Exit::Clean); failures to produce the report remain ordinary errors.

run_at

run_to, against a named auth store and a named site policy file.

run_to

run, writing to an arbitrary sink so tests can capture the report.