Similar to what we have today for test coverage, a separate job that measures fuzz coverage and prevents check-in when we drop below a certain level will incentivize more fuzzing work done across the developer community. We could narrow this to just extensions and data plane, or make it proxy wide. It won't start as 98%, but even if only 30%, it would provide a useful measure for how we are fairing and prevent regression.