A useful report distinguishes a completed check from an area it could not inspect.
A result is only as useful as its scope. “Nothing found” after a completed check means something different from “nothing found” because the check never ran. A report should make that distinction easy to see.
Ask what was actually checked
Consider a checkout that cannot be reached without a test account. A Review can inspect the public pages, but it cannot use that work to claim the checkout behaves correctly. The missing account is a coverage limitation.
Keep the evidence attached
The VibeCheck workflow is designed to separate reproduced Issues, source-established Issues, Concerns, informational observations, and untested coverage. Each label should help you understand what the evidence supports.
Before acting on a result, ask which version was tested, which actions completed, and what the tester could not reach. A short, specific limitation is more useful than an unexplained green tick.