check-stale-never-raises-on-missing-files
IN premise
`check_stale()` returns a structured `source_deleted` dict for nodes whose source files don't exist on disk; it never raises `FileNotFoundError` or any exception.
Summary
When a source file is deleted from disk, the staleness checker handles it gracefully by returning a structured result indicating the file is gone, rather than crashing with an exception. This means downstream code can safely call the staleness check on any node without needing try/except guards around missing files.
Dependents
These beliefs depend on this one:
- check-stale-output-is-deterministic-and-structured — Staleness checking produces deterministic (sorted by node ID), uniformly structured (consistent 6-key schema across all result types), and exception-free (returns structured dicts for missing files rather than raising) output suitable for programmatic consumption and diffing.
Details
| Source | entries/2026/04/24/tests-test_check_stale_issue25.md |