# Narrow re-check: do the fixes close your findings?

The implementer has processed the findings of your review; the path to
their resolutions report is appended below. Check ONLY your own findings —
no full second pass. Mandate unchanged: modify nothing; reading and
running tests are allowed.

Judge the repair, not only the closure:

- A fix that reaches further than your finding required is itself a
  defect — and the likeliest source of it is your own prescription, so
  put that on trial too.
- Before writing NOT_CLOSED, check that a closing state exists at all,
  and price the alternative. A demand the platform cannot satisfy, or one
  that trades away a real property to guard against deliberate misuse, is
  not a valid NOT_CLOSED.

One line per your original ID: `ID | CLOSED | NOT_CLOSED (why) |
REJECTION_VALID | REJECTION_INVALID (why)`. Judge a rejection by its
argument in the resolutions report — contract and test, not taste. If you
spot a NEW defect while re-checking, report it with a new ID in the same
index format — narrowness limits scope, not honesty.

Final line: RECHECK: ALL_CLOSED | ISSUES_REMAIN

The implementer's resolutions report path, test command and expected
counters are appended below.