Update README.md

Author: minggangw

README.md

@@ -124,7 +124,6 @@ how much glue you want to write.
   streaming as Server-Sent Events (`GET .../capability/subscribe/<name>`) —
   so shell scripts, Postman, AI-agent tool-use, and even a bare browser
   `fetch()` / `EventSource` (CORS-enabled) just work.
-  _New in `2.0.0-beta.0`._
 
   ```ts
   import { connect } from 'rclnodejs/web';
@@ -137,7 +136,6 @@ how much glue you want to write.
 - **[`rosocket`](./rosocket/README.md)** — thin WebSocket gateway,
   zero browser dependencies (just built-in `WebSocket` + `JSON`).
   Best for quick prototypes and `roslibjs`-style apps.
-  _New in `2.0.0-beta.0`._
 
   ```bash
   npx rosocket --port 9000 --topic /chatter:std_msgs/msg/String

scripts/npmjs-readme.md

@@ -100,7 +100,7 @@ Then `import * as rclnodejs from 'rclnodejs'` works the same as the JavaScript e
 
 `rclnodejs` ships **two** ways to reach ROS 2 from the browser — pick one based on how much glue you want to write.
 
-- **`rclnodejs/web`** — typed, allow-listed, `curl`-able browser SDK. A `web.json` file is your public API; the browser SDK types `call` / `publish` / `subscribe` end-to-end from your ROS 2 message types; every capability is also a plain HTTP endpoint (`curl -X POST http://<host>/capability/call/<name>`), so shell scripts, Postman, and AI-agent tool-use just work. _New in `2.0.0-beta.0`._
+- **`rclnodejs/web`** — typed, allow-listed, `curl`-able browser SDK. A `web.json` file is your public API; the browser SDK types `call` / `publish` / `subscribe` end-to-end from your ROS 2 message types; every capability is also a plain HTTP endpoint (`curl -X POST http://<host>/capability/call/<name>`), with `subscribe` streaming as Server-Sent Events (`GET http://<host>/capability/subscribe/<name>`), so shell scripts, Postman, AI-agent tool-use, and a bare browser `fetch()` / `EventSource` (CORS-enabled) just work.
 
   ```ts
   import { connect } from 'rclnodejs/web';

web/README.md

@@ -130,7 +130,8 @@ window.addEventListener('beforeunload', () => ros.close());
 
 When `--http-port` is on, every `call` / `publish` is reachable from
 any HTTP client — curl, Postman, AI-agent tool-use, no SDK required.
-Subscribe stays on WebSocket.
+With `--http-sse` (or `"http": { "sse": true }`), `subscribe` is also
+reachable over HTTP as a Server-Sent Events stream.
 
 ```bash
 # Service call
@@ -143,6 +144,29 @@ curl -sS -X POST http://localhost:9001/capability/call/add_two_ints \
 curl -sS -X POST http://localhost:9001/capability/publish/chatter \
   -H 'content-type: application/json' \
   -d '{"data":"hi from curl"}'
+
+# Subscribe over Server-Sent Events (needs --http-sse). Streams until
+# you disconnect; -N keeps curl from buffering the event stream.
+curl -N http://localhost:9001/capability/subscribe/chatter
+# event: ready
+# data: {"capability":"/chatter","subId":"sse"}
+#
+# event: message
+# data: {"data":"hello"}
+```
+
+From a browser, the same SSE endpoint works with the built-in
+`EventSource` (cross-origin when `--http-cors` is set):
+
+```js
+const es = new EventSource(
+  'http://localhost:9001/capability/subscribe/chatter'
+);
+es.addEventListener('message', (e) => {
+  const msg = JSON.parse(e.data);
+  console.log(msg.data);
+});
+es.addEventListener('error', () => es.close());
 ```
 
 ## 4. `rclnodejs/web` vs. `rosbridge` + `roslibjs`