Rabadon doctor reported the native core green by looking only at the binaries on disk, never at whether they were built from the source beside them — so a tree that does not compile could report all binaries present and healthy

what was wrong

measured in this repository: a half-finished multi-agent change left gate.cpp calling into a header it did not include, so make all failed with use of undeclared identifier 'rbhook'. rabadon doctor in the same tree answered with the full green banner, because every rabadon-* file was on disk and executable from a build made the previous day. The whole thesis of this project is that a green nobody re-ran is not a green, and the tool that reports rabadon's own health was making exactly that claim about itself. The fix is a staleness check rather than a compile: doctor compares the newest mtime under native/.cpp and native/.h against the oldest binary mtime and says STALE, naming the source that is newer, because running a build inside a diagnostic would make the diagnostic the slowest command in the product.

the command that shows it

A finding without a command that demonstrates it is an opinion, and site/build.py drops it. This one is also listed on the catches page.

related

commands

rabadon doctor