Module check 

2026-09-26: --pull-request-gate-check: does this commit have a passing record for every required gate? Reads .benchmarks/, the kernel tree and git diff; no endpoint, no GPU.

Owner: bench gate. Invariants:

• exit_code depends only on the verdicts it is given.
• A gate is GateStatus::Pass only when a readable record (for a group, a complete shard partition) stands at the commit and passes every check; otherwise it is GateStatus::Missing or GateStatus::Fail.

Re-exports

pub use super::scoring::Comparison;

pub use super::scoring::check_record;

pub use super::scoring::compare;

Enums

GateStatus

2026-09-26: One required gate’s standing in the committed tree.

Standing

2026-09-26: A record’s standing at a head, from its own commit.

Functions

check_gates

2026-09-26: The verdict for sha of every gate in REQUIRED_GATES, keyed by gate id.

exit_code

2026-09-26: The exit code: 0 when every verdict is Pass, else 1.

record_covers

2026-09-26: Whether a record measured at record_sha still stands for head on the path boundary alone: true when git diff between the two commits touches no path that invalidates gate, false when it does or git cannot diff them. Ancestry is not required, and the closure hash is not consulted (see record_standing).

record_standing

2026-09-26: Where a record measured at its own commit stands relative to sha. The gate verdict (record_still_stands) and record agreement (agreement::standing_at) both read this, so they cannot disagree about a record.

records_newest_first

2026-09-26: The .json record files in one benchmark’s directory, newest first by each record’s own recorded_at; BASELINE.json is not a record.