Pipeline annotations that developers actually open

Annotations should answer: which shard failed, which browser version ran, and where artefacts live. Anything else belongs in linked logs.

We recommend a single-line summary per failed stage, then a collapsible details block for deep links. Teams in Seoul and Berlin both responded well to that shape in office hours.

If your vendor lacks rich annotations, emit a tiny markdown file as an artefact and link it. Humans follow links; they rarely scroll raw console dumps.

This article stays vendor-neutral on purpose—bring your YAML flavour and map fields to the three facts above.