Release endpoint-libs 3.0.1 with secret-safe WebSocket logs

.gitignore

@@ -1,5 +1,10 @@
 /target
 Cargo.lock
+package-lock.json
+bun.lock
+bun.lockb
+pnpm-lock.yaml
+yarn.lock
 .vscode/settings.json
 node_modules/
 examples/ws-echo/target/

AGENTS.md

@@ -5,7 +5,7 @@ the single source of truth for the rules: Codex, Cursor and Gemini CLI read `AGE
 natively, and Claude Code loads it through the `@AGENTS.md` import in
 [`CLAUDE.md`](CLAUDE.md). **Never fork these rules into a per-vendor file.**
 
-**Mixed Rust + JavaScript repository.** The JS side (`endpoint-libs-examples`, built with `npm`) is the primary surface; the Cargo workspace holds supporting Rust (e.g. integration tests).
+**Rust workspace.** The library, examples, and integration tests are built with Cargo.
 
 ## Invariants (don't break these)
 
@@ -17,16 +17,10 @@ natively, and Claude Code loads it through the `@AGENTS.md` import in
   `WsRequest`/`WsResponse` traits and must be published after it; the six backends
   bump both together. Getting it wrong puts two incompatible copies of endpoint-libs
   in a consumer's graph. See [`docs/release-order.md`](docs/release-order.md).
-- **`npm` is the package manager** — its lockfile is authoritative. Don't introduce a second one by running npm/yarn/pnpm here.
-- **Two toolchains live here.** A change to one side does not imply the other still builds — check both before calling it done.
 - **Docs describe what is true now.** If you change behaviour, update the README and any affected doc in the same change.
 
 ## Build & run
 
-```bash
-npm install
-```
-
 ```bash
 cargo build
 cargo test

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "endpoint-libs"
-version = "3.0.0"
+version = "3.0.1"
 edition = "2024"
 authors = ["Veon <dveonloch@protonmail.com>"]
 description = "Launch MCP services fast: describe endpoints once in RON, and endpoint-gen generates the Rust models, docs and MCP tool schemas that this crate serves over WebSocket RPC, with roles and typed errors built in."

README.md

@@ -346,10 +346,6 @@ alone, which consumers depend on. A test asserts that stays true.
 Narrowing options on `ws`. `ws-http1` adds HTTP/1.1 upgrade support alongside HTTP/2;
 `ws-tls12` accepts TLS 1.2 in addition to 1.3. Default is HTTP/2 and TLS 1.3 only.
 
-### `s3-sync`
-
-Forwards to `cert-provider/s3-sync`, for certificate material synced from S3.
-
 ### `full`
 
 `types` + `ws` + `signal` + `scheduler` + `log_reader` +

examples/ws-echo/README.md

@@ -74,42 +74,3 @@ Expected response (error confirming the test passed):
 ```
 {"type":"Error","method":211,"code":100400,"seq":2,"log_id":"...","params":{"kind":"Rejected","message":"ReceiveUserInfo is not processed by this test server"}}
 ```
-
-## Run with Cloudflare Containers (wrangler dev)
-
-The Docker build context must be the repo root (so it can access the local `endpoint-libs` source via the path dependency). Run from the **repo root**:
-
-```sh
-npm install
-npx wrangler dev --config examples/ws-echo/wrangler.toml
-```
-
-Test:
-
-```sh
-websocat ws://localhost:8787
-```
-
-Then send a JSON message:
-
-```
-{"method":1,"seq":1,"params":{"message":"hello"}}
-```
-
-Expected response:
-
-```
-{"type":"Immediate","method":1,"seq":1,"params":{"message":"echo: hello"}}
-```
-
-Or call `ReceiveUserInfo`:
-
-```
-{"method":211,"seq":2,"params":{"userPubId":"a1b2c3d4-e5f6-7890-abcd-ef1234567890","username":"alice"}}
-```
-
-Expected response:
-
-```
-{"type":"Error","method":211,"code":100400,"seq":2,"log_id":"...","params":{"kind":"Rejected","message":"ReceiveUserInfo is not processed by this test server"}}
-```