searchIndexExcludes property
Issue numbers the search index has not absorbed, though the issue is in the repository and the list endpoint serves it.
The two indexes are independent and lag independently, which no single
call reveals: measured against a real repository holding 460 markered
issues, the label-filtered list served all 460 while the marker search
answered total_count: 283 and incomplete_results: false — a third of
the repository missing, reported as a complete answer, because from
search's point of view it was one. indexLag cannot express that: it
delays list and search together, so a caller that cross-checks one
against the other sees them agree at every instant.
Implementation
final Set<int> searchIndexExcludes = {};