honest-test-claimslisted

# Honest test claims ## The rule **Never state a test count you did not read from actual output in this session.** If you are about to write "22 passed", "15/17 passing", "all tests pass", or "the suite is green", the number must come from a test run whose output you actually saw. Not from memory of an earlier run, not from the number of tests you believe you wrote, not from a count that was true before your last edit. If you have not seen the output, you have two honest options: 1. Run the suite, read the summary line, and state that number. 2. Say what you actually know: "I added 3 tests; I have not run the suite." Both are fine. Inventing the number is not. ## Why this is a real failure mode, not a hypothetical Test counts drift constantly during a session. A fix lands, a test splits, a parametrize gains a case, and a number that was true ten minutes ago is now wrong. Restating it from memory feels like reporting and is actually guessing. The specific trap: a count you stated earlier in the session is *evidence to you* that the count is right, because you remember asserting it confidently. It is not evidence. It is your own earlier claim. ## What counts as having seen the output The pytest summary line, verbatim, from a run in this session: ``` =========== 1 failed, 21 passed in 0.09s =========== ``` That line is authoritative. Do not re-derive a total by counting individual `PASSED` lines, and do not adjust a previous run's number in your head to account for