README npx command (@dioptx/mcp-atom-of-thoughts) is unpublished (404); unscoped name is a different author's package

[wan-huiyan]

Thanks for the v3 rewrite — it builds and runs fine from source (the MCP server connects). Flagging two related packaging/docs issues:

1. The scoped package the README documents isn't published.

$ npm view @dioptx/mcp-atom-of-thoughts version
npm error code E404
npm error 404 Not Found - GET https://registry.npmjs.org/@dioptx%2fmcp-atom-of-thoughts - Not found

So the README's MCP-config snippet and TUI command — both using npx -y @dioptx/mcp-atom-of-thoughts — fail with a 404.

2. Namespace-collision hazard on the unscoped name.

The unscoped mcp-atom-of-thoughts IS on npm, but it's a different author's older package:

$ npm view mcp-atom-of-thoughts version maintainers
1.0.0
jeongsk <jeongseok@wantedlab.com>

It's v1.0.0, maintainer jeongsk, with no repository field linking back to this repo (this repo is v3.0.0). A user who drops the scope to work around issue (1) would silently install that different package instead of this code.

(Verified 2026-05-29 against registry.npmjs.org.)

Workaround today: git clone + npm install + npm run build, then register the local build, e.g. claude mcp add atom-of-thoughts -- node /path/to/build/index.js.

Suggested fix: publish @dioptx/mcp-atom-of-thoughts to npm, or update the README to document the build-from-source path and note the unscoped-name collision.