Operating steps
- Run a budget scan on the proposed tools/list or server-card output.
- Compare total eager tokens, schema tokens, and trace replay accuracy against policy.
- Fail the build with a clear fix prompt when thresholds are exceeded.
- Attach the budget diff to the pull request.
Common risks
- CI needs stable sample traces to avoid noisy failures.
- Temporary budget exceptions should expire automatically.
- Gate results should include enough detail for developers to fix the schema.