A negative code search establishes absence only in the searched checkout

A negative code search establishes absence only in the searched checkout, not across a repository's branches or history. For questions about prior experiments, first identify HEAD and compare it with relevant existing remote refs, then inspect Git pickaxe history and verify concrete bindings/call sites. Distinguish committed implementation, historical deployment reports, and current runtime state; none substitutes for the others. This method applies to stale or intentionally pinned checkouts. Existing remote refs can themselves be stale, and uncommitted or deleted remote work may remain undiscovered.