reviewing-problems

What problem does it solve? Before a competitive programming problem ships to Polygon, someone must verify the statement is unambiguous, the checker and validator match the promised I/O format, and the declared constraints are actually reached by the tests. Doing this audit by hand is error-prone and easy to skip under deadline pressure. ## Core Features & Use Cases - Mechanical checks: Runs tools.review_checks against the problem directory, the .tex statement, and testlib to catch structural inconsistencies automatically. - Judgement review: Reads the statement as a first-time contestant to find ambiguous sentences, assumed definitions, unproven algorithmic claims, and mismatches between the checker/validator and the stated format. - Hard-stop safety: Halts the pipeline when an unresolvable HIGH ambiguity is found, preventing tests from being built on a guessed interpretation. - Use Case: After preparing tests and solutions for a problem, run this audit to confirm the .tex scores and constraints match problem.json, samples match the main solution, and no sentence admits two legitimate readings. ## Quick Start Ask the assistant to review the finished problem package in the current directory and report any statement ambiguity or mechanical findings before shipping.