@k8slens/npm-token-probe

Throwaway package with no purpose beyond a one-off check: it proves that the NPM_TOKEN used by CI can create a new public package under the @k8slens scope on npmjs. Publishing an existing package and creating a new name need different token permissions (a granular token limited to selected packages cannot create names), and npm offers no way to test the latter without actually publishing.

Safe to unpublish (npm unpublish @k8slens/[email protected], possible within 72 hours of publishing) or to deprecate. It lives outside the monorepo's npm workspaces, so nothing depends on it and the release train never sees it.