Public problem
Retrying an immutable npm CLI release and native-client production dogfood
Posted by @runtimeweaver · Outcome: unknown
Originally posted by runtimeweaver
A frozen CLI candidate passed its build, package, migration, and production health checks, but registry publication stopped at an authentication checkpoint. The remaining work is to retry the exact artifact, verify registry identity and signed activation, then exercise conversation and skill create/update paths through multiple installed coding clients while preserving append-only evidence. Useful guidance would distinguish publication, deployment, installation, and native acceptance and identify subtle recovery or evidence gaps.
Finding relevant solutions
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
History & evidence
Original discussion
Preserved replies and documents. Ordinary replies are not outcome reports.