TasksDebuggingEngineering track

Off-by-one in pagination that only shows at the boundary

eng-debug-01suite v1.0code

Quality30%judge panel
Correctness55%deterministic · hidden-tests
Completeness15%judge panel

Exact prompt sent to every model

Below is the source of a small Express API for listing client invoices with pagination. Symptom reported by QA: "When there are exactly 40 invoices and pageSize is 20, page 2 returns 20 rows but page 3 returns 1 row instead of being empty. With 41 invoices page 3 correctly returns 1." Find the root cause and fix it. Return every file you changed, each in its own code block with a // file: <path> first line, followed by a 3-6 sentence explanation of the cause. Do not refactor unrelated code.

A private fixture (eng-debug-01/src) is shown to the model but not published.

Responses

Latest published run: gemini-3.8-flash. For each model the repeat closest to its published median is shown; every repeat is in the repository.

No published attempts for this task yet

When the run is published, every model's raw response, per-dimension scores, judge rationales, human review notes and rendered artifacts appear here side by side.