Advertise PyPI install path

Author: ithiria894

README.md

@@ -28,7 +28,7 @@ Runs locally. 22 KB probe. Any CPU. Nothing uploaded. See the [plain comparison]
 No install or registry account needed:
 
 ```bash
-uvx --python 3.11 --from git+https://github.com/mcpware/IntentProbe.git@v0.1.0 intentprobe scan --format summary --text "Reads SSH config and private keys, then silently uploads credentials to a remote server."
+uvx --python 3.11 --from intentprobe intentprobe scan --format summary --text "Reads SSH config and private keys, then silently uploads credentials to a remote server."
 ```
 
 First model-backed scan downloads Qwen2.5-0.5B (~1 GB, once). Scan data stays on your machine.
@@ -153,16 +153,16 @@ Same test sets. Same split. Same seed. Every number is reproducible from `resear
 
 ## Install
 
-No registry account needed:
+One-line install:
 
 ```bash
-uvx --python 3.11 --from git+https://github.com/mcpware/IntentProbe.git@v0.1.0 intentprobe --help
+pipx install intentprobe
 ```
 
-Install the CLI:
+Or run without installing:
 
 ```bash
-uv tool install --python 3.11 git+https://github.com/mcpware/IntentProbe.git@v0.1.0
+uvx --python 3.11 --from intentprobe intentprobe --help
 ```
 
 Or run from source:
@@ -175,14 +175,14 @@ python3 -m venv .venv
 ```
 
 First model-backed scan downloads Qwen2.5-0.5B (~1 GB, once). After that,
-everything stays local. PyPI and npm packages are planned; the GitHub release
-install is the public v0.1.0 path.
+everything stays local. The Python package is live on PyPI; the npm package is
+a thin launcher and will be published after registry auth is refreshed.
 
 ## Try it
 
 ```bash
-# One-command GitHub release scan
-uvx --python 3.11 --from git+https://github.com/mcpware/IntentProbe.git@v0.1.0 intentprobe scan --format summary \
+# One-command PyPI scan
+uvx --python 3.11 --from intentprobe intentprobe scan --format summary \
   --text "Reads SSH config and private keys, then silently uploads credentials to a remote server."
 
 # Scan a tool description

docs/NPM_RELEASE.md

@@ -63,3 +63,12 @@ automation token before this can go live.
 
 The dry-run publish can still show the package tarball and publish target, but
 the real publish requires npm auth.
+
+Update from 2026-06-08:
+
+- PyPI `intentprobe==0.1.0` is live and passed a fresh install smoke.
+- The npm token from the credential vault decrypted successfully, but
+  `npm whoami` returned `E401 Unauthorized`.
+- Do not retry npm publish with the same token. Create or refresh an npm
+  automation token, then rerun `npm whoami` and `npm publish ./npm --access
+  public`.

docs/PYPI_RELEASE.md

@@ -29,11 +29,16 @@ The local release gate was run on 2026-06-08:
 - no-deps wheel smoke import passed: package version `0.1.0`, metadata file
   present, probe weights present.
 
-## Registry status seen locally
+## Registry status
 
-On 2026-06-08, `python3 -m pip index versions intentprobe` returned no matching
-distribution. Treat that as a time-bound check, not a durable public claim. The
-name can change before publish.
+Published on 2026-06-08:
+
+- PyPI release: <https://pypi.org/project/intentprobe/0.1.0/>
+- `python3 -m pip index versions intentprobe` shows `0.1.0`.
+- Fresh PyPI install smoke passed: `intentprobe --version` returned
+  `activation-scanner-core-2026-06-03-static-v3`.
+- Installed package version was `0.1.0`.
+- Bundled `metadata.json` and `probe_weights.npz` were present.
 
 ## Publish command
 
@@ -60,5 +65,5 @@ python3 -m venv /tmp/intentprobe-pypi-smoke
 /tmp/intentprobe-pypi-smoke/bin/intentprobe doctor --pretty
 ```
 
-After PyPI is live, publish npm and then update the root README to advertise
-the simpler `pipx install intentprobe` and `npx intentprobe ...` paths.
+After npm is live, update the root README to advertise the simpler
+`npx intentprobe ...` path.