Verified now@deepseek-ai/dsh-agent-loop@0.1.0-rc.8 exists on registry.npmjs.org. A resolver can still hold older metadata.

Route registry identity first.

Configured

Record npm config get registry.

Authoritative

Query the exact version on official npm.

Integrity

Compare full tarball digests, not filenames.

Cache

Use a new probe cache before deleting shared state.

Four outcomes, four owners.

Both see rc.8local install state

Probe with a new job-scoped cache.

Only npm sees rc.8mirror or proxy

Wait for replication or invalidate one metadata entry.

Neither sees rc.8release graph

Stop and report the unavailable publication.

Do not begin with npm cache clean --force.

Capture the configured registry and version lists, then isolate one fresh cache. Broad deletion destroys the evidence that distinguishes stale metadata from publication failure.

Prove one clean resolution.

probe_cache="$(mktemp -d)"
npx -y --cache "$probe_cache" \
  --registry=https://registry.npmjs.org/ \
  @deepseek-ai/dsh@0.1.0-rc.8 --version

Require the exact output 0.1.0-rc.8. A successful official-registry probe does not authorize bypassing an enterprise registry for production; it identifies which metadata boundary needs repair.

Primary evidence.

Keep the complete registry runbook.

The canonical guide includes official-versus-mirror routing, PowerShell and POSIX probes, dist-tag semantics, CI cache keys, release-publisher gates, and an incident bundle.

Read the complete guide