Problem:

When jobs fail in CircleCI, there's no way to leave contextual notes explaining why it happened or linking to relevant resources. This leads to repeated investigations, lost knowledge, and wasted time searching for context.

Proposed Solution:

Add manual annotations on graphs and job timelines (similar to Datadog's annotations) that allow users to:

* Pin notes to specific job failures

* Add explanations and links (e.g., to Datadog graphs, PRs, tickets)

* Make context visible to all team members

Use Case:

Team has a non-blocking job integration-tests still in development. When it fails, they want to annotate: "Failed due to API rate limiting. See [DD graph]. Will be fixed in Q1. Safe to ignore."

This prevents others from re-investigating the same issue and creates a historical record of patterns.

Benefits:

* Reduced investigation time

* Better knowledge sharing across the team

* Historical visibility of recurring issues

* Improved incident response