When Scarab Diagnostic Suite started taking shape, I thought I was building diagnostics.
That was the obvious word for it.
AI coding agents were changing code quickly. Repos were drifting. Bugs were appearing in strange places. Tests were passing without proving the right thing. Files were taking ownership of behavior they should not own.
So the first question was simple:
Can a system drop into a messy repo, locate the real failure surface, and identify the narrow repair lane without making everything worse?
