Publish as orvix-cli

[lightningpixel]

npm refuses the name orvix:

403 Forbidden - PUT https://registry.npmjs.org/orvix
Package name too similar to existing package urix

urix@0.1.0 is a deprecated package from years ago. The block applies to everyone, so nobody else can take orvix either.

Only the package name changes

The command is still orvix. bin names it independently of the package, and I verified that rather than assuming it — packed the tarball, installed it globally, and ran it:

$ npm install -g orvix-cli-0.2.0.tgz
$ which orvix
/c/Users/MaXx_/AppData/Roaming/npm/orvix
$ orvix --version
0.2.0
$ orvix index .
10 files, 21 symbols, 10 call edges

Untouched: the repository name, the CLI name, HOOK_MARKER, and the .orvix/ cache directory.

Why orvix-cli and not @lightningpixel/orvix

Shorter to install, better placed in npm search, and it reads as a tool rather than a personal namespace — the @vue/cli → vue pattern in reverse. The scoped name stays available if npm refuses this one as well; a refusal costs nothing, since the similarity check runs before anything is recorded.

Checked

• npm run build, npx tsc --noEmit, npm test — 395 tests pass
• package-lock.json regenerated, so the lock and the manifest agree
• ci.yml installs /tmp/orvix-*.tgz, which still matches orvix-cli-0.2.0.tgz — confirmed against the real filename

After merging

The v0.2.0 release carries an orvix-0.2.0.tgz whose manifest says orvix. Move the tag so the release reattaches the right artefact:

git checkout main && git pull
git tag -d v0.2.0 && git push origin :refs/tags/v0.2.0
git tag v0.2.0 && git push origin v0.2.0

Then npm publish --access public.