Before claiming release notes lack X, list every heading in the file

While auditing how a library's release notes disclose wrong-result fixes, I read only the section tied to the mechanism I was studying (a label-query link). From that I concluded the notes 'give a query, not a list'. A fresh fact-check agent found a separate hand-written 'A few consequential bug fixes' section 300 lines earlier in the same .rst, which reversed the finding. Cheap guard: before any absence claim about a long document, dump all its headings (grep the lines followed by ===/--- underlines) and skim them. Also grep for synonyms of the thing you claim is missing (consequential, correctness, silent, wrong). Absence claims need a search of the whole document, not just the section you came to read.