# Human review checklist

- [ ] Confirm the contract: zero is valid; undefined means no filter; invalid inputs are handled upstream.
- [ ] Run the regression against the buggy starting point; confirm it fails for the reported reason.
- [ ] Read the patch: check for undefined explicitly rather than testing truthiness.
- [ ] Check that nonzero priorities, no filter, no matches and empty inputs still behave as specified.
- [ ] Confirm the function preserves input and order, and adds no dependency or unrelated change.
- [ ] Run the corrected suite yourself and inspect the actual output.
- [ ] For a real repository, run its integration, lint and security checks as well.
- [ ] Record time spent on reproduction, context setup, generation, testing, review and rework separately.
- [ ] Compare total effort with comparable work done the current way, including review and tool cost.
- [ ] Decide whether to merge, ask for changes or reject the patch. Passing tests alone are not approval.

For this example, review the diff between `broken.mjs` and `fixed.mjs`. No merge, client result, productivity gain or production validation is claimed.