Open the files under screenshots/ with your normal image viewer. Use their filenames, timestamps, and the surrounding artifacts to establish where each image belongs in the investigation.

Establish what the image shows

Read the corresponding entry in session.md or notes.md when one exists. Record the filename, visible subject, expected state, observed state, and any context outside the crop.

The full filename suffix means a visible viewport capture, not a stitched full-page image. An area capture can omit a lane heading, account identity, error message, or other relationship needed for the conclusion. Use the action sequence or returned data to supply only context that those artifacts actually establish.

An externally added image can describe a useful state without proving when that state occurred. Treat timing or provenance written by the tester as an authored observation unless another artifact supports it.

Compare with the same subject

Use stable text, a record ID, filename note, or surrounding action to connect the image to network.har and session.md. Do not join evidence only because it appears near the same time.

In the sample bundle, 003-area.png shows the Blocked badge but omits the lane heading. The recorded In progress action and final board response establish the lane; the pixels establish the remaining badge.

Review and share safely

Inspect names, messages, account details, tokens, QR codes, browser chrome, and background content. Screenshot pixels are not automatically masked. If an image is unsafe, request a retaken or separately edited copy using safe data; preserve the original only in an approved location.

Share only the images needed for the conclusion and state what each one cannot show. An omitted file is different from a sanitized connected report, and excluding a file from your handoff does not alter copies already shared.