How it works
Configuration decides which reviewers run, where output is posted, and how cost is reported. Keep secrets in environment storage and validate changes with a dry run.
For configure a juror review, use the published configuration and source repository as the product record. Keep the workflow small enough to inspect, and record any exception in the pull request rather than assuming a model result is final.
Limits to keep in view
Models, providers, and benchmark conditions change. Juror does not replace code ownership, test suites, static analysis, or a human decision to merge. Treat unknown cost and unevaluated compatibility as explicit unknowns.