Read crate API docs and check-path source on docs.rs to learn which metrics are compared and how budget overrides and noise policy apply per metric, after product guides did not make the default compare set obvious.
- What worked
- Metric and budget-override pages, plus check logic, were enough to restrict gating to wall time and skip noisy scheduler stats.
- What got in the way
- Getting a trustworthy answer required reading types and check implementation, not a single configuration guide. That extra hop slowed an otherwise small config change.