feat(acp-registry): switch to uvx distribution, drop npm launcher

The ACP Registry schema supports uvx as a first-class distribution method
alongside npx and binary. Pointing the registry directly at the existing
hermes-agent PyPI release removes:

- the @nousresearch npm scope (we don't own it)
- a separate npm publish step on every weekly release
- 90 lines of Node launcher + tests in packages/hermes-agent-acp/

The Zed registry now installs Hermes via:

  uvx --from 'hermes-agent[acp]==<version>' hermes-acp

This is the same command the npm launcher was shelling out to anyway, so
end-user behavior is unchanged. Registry CI validates the PyPI URL +
version-pin exact match automatically.

Changes:
- acp_registry/agent.json: distribution.npx -> distribution.uvx
- delete packages/hermes-agent-acp/ entirely
- scripts/release.py: drop npm-launcher bump paths, keep manifest lockstep
- tests/acp/test_registry_manifest.py: assert uvx shape + version pin
- tests/scripts/test_release_acp_registry.py: rewrite for uvx-only shape
- docs (user-guide + dev-guide): drop all npm-launcher references
- delete docs/plans/acp-registry-zed-integration.md (stale, npm-shaped)

Validated against agentclientprotocol/registry agent.schema.json via
jsonschema. hermes-agent==0.13.0 is already live on PyPI.

website/docs/developer-guide/acp-internals.md

@@ -31,7 +31,7 @@ hermes acp / hermes-acp / python -m acp_adapter
   -> acp.run_agent(agent, use_unstable_protocol=True)
 ```
 
-The Zed ACP Registry path launches the same adapter through `npx @nousresearch/hermes-agent-acp@<version>`, which delegates to `uvx --from 'hermes-agent[acp]==<version>' hermes-acp`.
+The Zed ACP Registry path launches the same adapter through `uvx --from 'hermes-agent[acp]==<version>' hermes-acp`, pointed at the `hermes-agent` PyPI release.
 
 Stdout is reserved for ACP JSON-RPC transport. Human-readable logs go to stderr.
 

website/docs/user-guide/features/acp.md

@@ -45,13 +45,13 @@ This installs the `agent-client-protocol` dependency and enables:
 - `hermes-acp`
 - `python -m acp_adapter`
 
-For Zed registry installs, Zed launches Hermes through the official ACP Registry entry. That entry uses the npm launcher package `@nousresearch/hermes-agent-acp`, which runs:
+For Zed registry installs, Zed launches Hermes through the official ACP Registry entry. That entry uses a `uvx` distribution that runs:
 
 ```bash
 uvx --from 'hermes-agent[acp]==<version>' hermes-acp
 ```
 
-Make sure `uv` or `uvx` is available on `PATH` before using the registry install path.
+Make sure `uv` is available on `PATH` before using the registry install path.
 
 ## Launching the ACP server
 
@@ -150,13 +150,13 @@ acp_registry/icon.svg
 
 The upstream registry PR copies those files into the top-level `hermes-agent/` directory in `agentclientprotocol/registry`.
 
-The registry entry uses an `npx` distribution:
+The registry entry uses a `uvx` distribution that points directly at the `hermes-agent` PyPI release:
 
 ```text
-npx @nousresearch/hermes-agent-acp@<version>
+uvx --from 'hermes-agent[acp]==<version>' hermes-acp
 ```
 
-The launcher then runs `hermes-acp` from the matching Python package version.
+The registry CI verifies that the pinned version exists on PyPI, so the manifest's `version` and uvx `package` pin must always match `pyproject.toml`. `scripts/release.py` keeps them in lockstep automatically.
 
 ## Configuration and credentials
 
@@ -207,7 +207,7 @@ Check:
 - For manual/local development, verify the custom `agent_servers` command points to `hermes acp`.
 - Hermes is installed and on your PATH.
 - The ACP extra is installed (`pip install -e '.[acp]'`).
-- `uv` or `uvx` is installed if launching from the official Zed registry entry.
+- `uv` is installed if launching from the official Zed registry entry.
 
 ### ACP starts but immediately errors