Skip to main content

Module probes

Module probes 

Source
Expand description

The environment probe catalog.

One catalog, read by every caller that needs to know whether this host is ready: rk doctor runs it whole, and a mutating command guards the subset it depends on at entry, so the per-command guards and the doctor cannot drift apart. Each probe answers with a status, a message, and — on failure — the remediation printed verbatim wherever the probe is consulted.

Structs§

ProbeResult
One probe’s answer.

Enums§

ProbeClass
How a failure weighs at the doctor level.
ProbeStatus
What a probe found.

Constants§

HARD_RUNTIME_TOOLS
Every executable a Hard probe requires, paired with the nixpkgs package whose bin/ supplies it in the installed package’s wrapper.
SKILL_PROBES
The probes judging the skill installation itself, in catalog order.

Functions§

direnv
direnv answers; it loads the devshell on directory entry.
direnv_bin
One owner for the direnv binary, which nothing here spawns but the doctor probes: it is what loads a consumer’s devshell on entry. RK_DIRENV_BIN substitutes it.
git_bin
One owner for the git binary every production launcher spawns.
nix
Nix answers; rk devshell sync updates and builds the pinned devshell with it. Soft, and deliberately outside the wrapper: wrapping nix would put it inside the package’s own closure on every host.
nix_bin
One owner for the nix binary every devshell launch spawns: the lock refresh, the system probe, and the build. RK_NIX_BIN substitutes it.
run_all
Run the whole catalog, in its stable order.
sh_bin
One owner for the POSIX shell every setup step spawns through.