Search the code the builder actually emitted, across every generation. Token mode is anchored — the identifier must sit where an API is used (dragToMove:, [dragToMove]=, :drag-to-move=), not merely appear in a comment or a string. Regex mode is raw, for everything the catalog has no name for.

Coverage, inverted. Every other view asks whether one demo is right; this asks which catalog entries the pipeline has never once emitted. An API option that appears in no generated demo, or a recipe the planner never cites, is either undiscoverable or broken — and no amount of per-run scoring will ever surface it.

What no static check can see. Every check in the pipeline reads code; none of them can tell that the resource filter select does not open. A note is the record of a person looking at the demo — and the area tag is what makes six notes into one finding: “the select is broken” said about six different cases is a systemic defect, the same count on one case is one bad demo.

A note that keeps recurring is a check waiting to be written. When you write it, set the note's checkId — that closes the loop, and ?format=agent turns the open set into a work order an agent can consume.