Every path it matched, the listed ones and those beneath them.
The topmost paths it matched, objects and marks alike, in the order the scene lists them; empty when it matched nothing.
The pattern as the request writes it.
Which part of the request the pattern belongs to: parts, hide, label, color, or the view's focus.
What one pattern of a drawn cell resolved to: the role it plays in the request, the pattern as written, and the paths it matched, so the record shows whether each selection, label, colour and focus matched what was meant.
.agents/skills/visual-debugging/capture.mdasks a reader to confirm from the record that each selection matched what was meant, because an empty selection draws a still with no defect in it. A pattern takes the subtree under every path it matches, so only the topmost matched paths are listed, with the count of every path matched beneath them; the record lists names, never geometry, and grows with the number of distinct subtrees a pattern reaches.