Repository navigation
Exposition: raise the minimal-file baseline to 214 - #284
Conversation
CI measured 214/245 passing on the merge of #283 — the branch was gated at 207, the count from a local run over a smaller target set. At 207 a six-target regression would have gone unnoticed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Greptile SummaryRaises the
Confidence Score: 5/5Safe to merge — the only change is tightening the ratchet threshold to match what CI already measured. The change is a single integer bump that makes the gate stricter, not looser. The new value (214) is directly sourced from the CI run on #283, so it reflects a real measurement rather than a guess. Nothing in the workflow logic, scripts, or job structure is modified. Files Needing Attention: No files require special attention.
|
| Filename | Overview |
|---|---|
| .github/workflows/exposition-verify.yml | Single-line baseline bump from 207 to 214 in the exposition verify job, tightening the ratchet to match CI-measured results from #283. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[PR or weekly schedule trigger] --> B[Checkout + Restore caches]
B --> C[Install Lean + Mathlib cache]
C --> D[Build pool]
D --> E[Extract declarations]
E --> F[Generate site data]
F --> G[Verify minimal files\n--baseline 214]
G -->|pass: compiled >= 214/245| H[Upload report artifact]
G -->|fail: compiled < 214| I[CI fails]
Reviews (1): Last reviewed commit: "Exposition: raise the minimal-file basel..." | Re-trigger Greptile
CI measured 214/245 minimal files compiling on the merge of #283. That branch was gated at 207, which came from a local run over a smaller target set (238), so the ratchet had ~7 targets of slack — a real regression could have landed unnoticed.
Raises
--baselineto the number CI actually measured. The gate's own run on this PR validates it.🤖 Generated with Claude Code