bug-report-verifylisted

# Bug report validity verification Your task is NOT to check formatting, but to adversarially verify the problem itself. Assume that the report may be an agent's hallucination or a false conclusion drawn from incomplete context. Your goal is to try to DISPROVE the report, and only if you cannot disprove it — confirm it. ## Input `$ARGUMENTS` — path to the bug report file or the report text itself. - If the argument looks like a path (`docs/bugs/**`, `*.md`, `*.txt`) — read the file. - If it is the report text pasted directly into the message — use it as is. - If the argument is empty — take the bug report from the user's last message in the conversation; if it is not there either, ask which report to check (do not invent one). ## How to proceed 1. **Extract the claims.** Break the report down into atomic factual claims: - what exactly reproduces (steps, input data, environment); - what behavior is observed (actual); - what behavior is expected (expected) and WHAT that expectation is based on (spec, documentation, code, the report author's common sense?); - what cause/localization is asserted (if any). 2. **Check each claim independently, against primary sources:** - find the actual implementation of the described behavior in the code — read the code, not the retelling in the report; the mentioned files/functions/endpoints/configs must exist and do what is claimed; - verify that the "expected behavior" is actually expected: is there a