check-stale-exits-nonzero

IN premise

`cmd_check_stale` calls `sys.exit(1)` when any stale nodes are found, making it usable as a CI or pre-commit gate.

Summary

The staleness checker is designed to fail hard when it finds problems, returning a non-zero exit code that CI pipelines and pre-commit hooks can catch. This means you can wire it into automated workflows and block merges or deployments whenever beliefs in the system have gone stale.

Dependents

These beliefs depend on this one:

staleness-checking-is-comprehensive — Staleness checking detects all nodes whose source material has changed on disk
staleness-is-conservative-ci-gate — Staleness checking is designed as a safe CI gate: it never mutates state, only checks IN nodes, requires both source fields, and exits nonzero to fail the pipeline

Details

Source

entries/2026/04/23/reasons_lib-cli.md